Back to Browse
Multichain RPC – ERC-721 NFT Metadata Lookup
x402
Multichain RPC – ERC-721 NFT Metadata Lookup is a paid API for AI agents from multichain-rpc.clankerceo.workers.dev, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).
Fetches on-chain ERC-721 NFT metadata (name, token URI, standard) for a given contract address and token ID on EVM chains including Base, Polygon, Arbitrum, Optimism, and Ethereum.
Price / call$0.004
Success—
StatusUnknown
How this service works
Cheap, factual EVM chain lookups priced per call in USDC. Base, Polygon, Arbitrum, Optimism and Ethereum.
Output
A JSON object containing the chain name, contract address, token ID, NFT standard (erc721), the raw token URI (e.g. ipfs://…), and the resolved metadata object (including the NFT name and any other on-chain fields).
Example use cases
NFT display card in a marketplace
“Pull the metadata for token ID 42 of the contract 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D on Ethereum so I can show the NFT's name and image in my app.”
Verify NFT ownership details
“I need to confirm the token URI and metadata standard for token ID 7 of contract 0x8a90CAb2b38dba80c64b7734e58Ee1dB38B8992e on Base — is it ERC-721?”
Resolve IPFS link for NFT attributes
“Fetch the on-chain metadata for token #100 of contract 0x34d85c9CDeB23FA97cb08333b511ac86E1C4E258 on Polygon so I can resolve the IPFS URI and display the traits.”
Technical details
Endpoint
GEThttps://multichain-rpc.clankerceo.workers.dev/erc721-metadataWhen to prefer
Choose this endpoint when you need cheap, pay-per-call ERC-721 metadata lookups across multiple EVM chains (Base, Polygon, Arbitrum, Optimism, Ethereum) without managing your own RPC infrastructure. It is ideal for AI agents that need factual, on-chain NFT data priced in USDC via x402 micropayments, avoiding subscription overhead for low-volume or bursty queries.
Side effects
- Invalid or non-existent contract address returns an error or empty metadata
- Token ID not minted yet may return a revert or null metadata
- Unsupported chain name returns a bad request error
- IPFS or HTTP token URI that is unreachable may result in partial metadata
- Malformed contract address format causes a query failure
- Rate limits or RPC node downtime may cause transient errors
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"chain": "base",
"contract": "0x…",
"metadata": {
"name": "Item #1"
},
"standard": "erc721",
"token_id": "1",
"token_uri": "ipfs://…"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"