NFT holdings for an address

Return the NFTs owned by a wallet address on a given network. Send POST /api/nft-holdings with the required field address and pay $0.002 per call over x402 or MPP (there is no free tier). It returns a JSON object with address, network, totalCount, nfts and pageKey.

Each row carries the collection name, contract address, token ID, image URL (where available), and ERC-721 vs ERC-1155 standard. Up to 100 per call - paginate with `pageKey` from the previous response.

Category: Crypto & onchain data · Tags: crypto nft wallet erc721 erc1155 evm · Also found as: erc721-tokens

TRY IN PLAYGROUND →

Parameters

Example request

curl -i -X POST https://agent402.tools/api/nft-holdings \
  -H "Content-Type: application/json" \
  -d '{"address":"0xaBF4FAbd7c416fB67202E5f9002389Fc75e2a9D0","network":"base"}'

Without payment this returns HTTP 402 Payment Required with the exact price for nft-holdings; any x402 v2 or MPP client pays it and retries.

Example response

{
  "address": "0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0",
  "network": "base",
  "totalCount": 0,
  "nfts": [],
  "pageKey": null
}

From an MCP client

catalog.call {
  "slug": "nft-holdings",
  "params": {
    "address": "0xaBF4FAbd7c416fB67202E5f9002389Fc75e2a9D0",
    "network": "base"
  }
}

The hosted connector at https://agent402.tools/mcp needs a payment for nft-holdings; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY. Local install: npx -y agent402-mcp.

Errors and behavior

• address is required. An input the tool rejects returns an HTTP 4xx whose body carries error, tool, expected, required and example, so the caller can correct it.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (Authorization: Bearer a402_...) also pays it.
• A GET or HEAD to /api/nft-holdings returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/nft-holdings", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "address": "0xaBF4FAbd7c416fB67202E5f9002389Fc75e2a9D0",
    "network": "base"
  }),
});

Part of these workflows

NFT holdings for an address is one step in this skill pack, each sold as a single call:

• NFT portfolio - NFT + wallet snapshot: NFT holdings, native balance, and ETH price for a given address in one call.

Related tools