Skip to main content
Glama

OpenAny

Alchemy — NFTs By Contract

alchemy_get_nft_v3_getnftsforcontract

getNFTsForContract - Retrieves all NFTs associated with a specific NFT contract. This endpoint is supported on Ethereum and many L2s, including Polygon, Arbitrum, Optimism, Base, World Chain and more. See the full list of supported networks here. Uses the shared Alchemy Free quota; not unlimited. Documentation prepared only, not runtime-verified. Uses the caller's OpenAny gateway credentials. Charges and authorization are determined by the gateway.

Input Schema

NameRequiredDescriptionDefault
limitNoInteger - Sets the total number of NFTs returned in the response. Defaults to 100.
startTokenNoString - A tokenID offset used for pagination. Can be a hex string, or a decimal. Users can specify the offset themselves to start from a custom offset, or to fetch multiple token ranges in parallel.
withMetadataNoBoolean - if set to `true`, returns NFT metadata. Setting this to false will reduce payload size and may result in a faster API call. Defaults to `true`.
contractAddressYesString - Contract address for the NFT contract (ERC721 and ERC1155 supported).
tokenUriTimeoutInMsNoNo set timeout by default - When metadata is requested, this parameter is the timeout (in milliseconds) for the website hosting the metadata to respond. If you want to _only_ access the cache and not live fetch any metadata for cache misses then set this value to 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.