Alchemy — Contracts By Owner

getContractsForOwner - Retrieves all NFT contracts held by a specified owner address with the Alchemy API. Supply a repository owner. Sample fields include addresses and symbols. Use it in blockchain research or an on-chain monitoring dashboard. The GET request schema also lists pageKey, pageSize.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
String - Address for NFT owner (can be in ENS format for Eth Mainnet).
Optional parameters (4)
String - key for pagination. If more results are available, a pageKey will be returned in the response. Pass back the pageKey as a param to fetch the next page of results.
Number of NFTs to be returned per page. Defaults to 100. Max is 100.
Boolean - 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`.
Enum - ordering scheme to use for ordering NFTs in the response. If unspecified, NFTs will be ordered by contract address and token ID. - transferTime: NFTs will be ordered by the time they were transferred into the wallet, with newest NFTs first. Note: This ordering is supported on Ethereum Mainnet, Optimism Mainnet, Polygon Mainnet, Base Mainnet, Arbitrum One, Polygon Amoy, Base Sepolia, Arbitrum Sepolia, Ethereum Sepolia, and Optimism Sepolia.

Sample response

{
  "contracts": [
    {
      "address": "0xe785E82358879F061BC3dcAC6f0444462D4b5330",
      "contractDeployer": "<contractDeployer>",
      "deployedBlockNumber": 0,
      "displayNft": {
        "name": "<name>",
        "tokenId": "<tokenId>"
      },
      "image": {
        "cachedUrl": "<cachedUrl>",
        "contentType": "<contentType>",
        "originalUrl": "<originalUrl>",
        "pngUrl": "<pngUrl>",
        "size": 0,
        "thumbnailUrl": "<thumbnailUrl>"
      },
      "isSpam": false,
      "name": "<name>",
      "numDistinctTokensOwned": 0,
      "openseaMetadata": {
        "bannerImageUrl": "<bannerImageUrl>",
        "collectionName": "<collectionName>",
        "description": "<description>",
        "discordUrl": "<discordUrl>",
        "externalUrl": "<externalUrl>",
        "floorPrice": 0,
        "imageUrl": "<imageUrl>",
        "lastIngestedAt": "<lastIngestedAt>",
        "safelistRequestStatus": "<safelistRequestStatus>",
        "twitterUsername": "<twitterUsername>"
      },
      "symbol": "<symbol>",
      "tokenType": "<tokenType>",
      "totalBalance": 0,
      "totalSupply": "<totalSupply>"
    }
  ],
  "pageKey": "<pageKey>",
  "totalCount": "<totalCount>"
}

Response result

Response structure

Inferred from examples
  • contractsobject[]
    • addressstring
    • contractDeployerstring
    • deployedBlockNumberinteger
    • displayNftobject
      • namestring
      • tokenIdstring
    • imageobject
      • cachedUrlstring
      • contentTypestring
      • originalUrlstring
      • pngUrlstring
      • sizeinteger
      • thumbnailUrlstring
    • isSpamboolean
    • namestring
    • numDistinctTokensOwnedinteger
    • openseaMetadataobject
      • bannerImageUrlstring
      • collectionNamestring
      • descriptionstring
      • discordUrlstring
      • externalUrlstring
      • floorPriceinteger
      • imageUrlstring
      • lastIngestedAtstring
      • safelistRequestStatusstring
      • twitterUsernamestring
    • symbolstring
    • tokenTypestring
    • totalBalanceinteger
    • totalSupplystring
  • pageKeystring
  • totalCountstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Alchemy — Contracts By Owner with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.