Cloud function result object

When following the BSC NFT tutorial (https://www.youtube.com/watch?v=02VnfTIomn8) to implement some quick testnet NFTs, I found that cloud functions always wrap the response in a “result” object that cannot be stripped. This causes metadata to not work with platforms such as Opensea.

As a workaround I was able to create a separate endpoint that removes this result object, but it would be preferred if cloud functions could not wrap the result in another object.

Moralis Cloud Response:

{
    "result": {
        "nft_id": 0,
        "name": "Death Knight Helm",
        "description": "A horned helm of the cult of death knights.",
        "image": "https://fqwpsdk76ndn.moralis.io:2053/server/files/a8w1Tc3Ac1PopSRcTAtrLDRB2kAMvPKImQWKQjX5/d1bbc24878efcec442302ec827318431_DK-Helm-Blue-Male.png"
    }
}

Required Response for metadata:

{
    "nft_id": 0,
    "name": "Death Knight Helm",
    "description": "A horned helm of the cult of death knights.",
    "image": "https://fqwpsdk76ndn.moralis.io:2053/server/files/a8w1Tc3Ac1PopSRcTAtrLDRB2kAMvPKImQWKQjX5/d1bbc24878efcec442302ec827318431_DK-Helm-Blue-Male.png"
}

Hi,
This looks similar to this post: Using HTTP Cloud Functions as URI endpoint for NFT metadata

Ah I must have missed that one in my search, I guess my workaround will do. Thanks!