Skip to main content
NFT ownership is public, but following it means decoding contract events across collections and token ids — a job for an indexer, not an RPC call — and the question an agent actually gets (“who owns this, and who held it before?”) spans a collection, one token and a wallet at once. Through AgentKey your agent reads collections, individual tokens, owners and transfers the same way it reads everything else — find_tools, describe_tool, execute_tool — with Chainbase behind the scenes.

​
What you can ask

  • “Who owns token #4821 in this collection, and who owned it before?”
  • “List every item in this collection with its metadata.”
  • “How many distinct owners does this collection have?”
  • “Show the most recent transfers in this collection.”
  • “Which NFTs does this wallet hold?”
  • “Has this token changed hands more than once this year?”
  • “Which wallets hold the most items in this collection?”
  • “这个 NFT 合约的名称、符号和基本信息是什么？“

​
What’s covered

Collections
  • Collection metadata for a contract address
  • The items in a collection, with their metadata
  • Every current owner of a collection — the basis for owner counts and concentration, since the full list is returned rather than a summary
  • Historical transfer transactions for a collection contract
Individual NFTs
  • Metadata of a specific token
  • Current owner of a token, and the full list of its historical owners
Wallets
  • The NFTs owned by an address — see also on-chain and wallets, where the cross-chain portfolio view can include a wallet’s NFTs
  • Entity labels for owner addresses, through the wallet tools, to tell an exchange or fund wallet from an individual collector

​
How to use it

Pass the request in plain language and let the router pick the tool:
Both English and Chinese phrasing work. Always describe_tool before executing — lookups take a contract address, a token id and a chain parameter, and the per-call cost is shown there. A typical flow is collection metadata first, then items or owners, then the owner history of one token. For a wallet-first question, start from the wallet tools instead — they return the NFTs an address holds alongside its balances.
Building with code? NFT data is available through the catalog today; there is no dedicated Scenario Method yet. See Scenario Methods for the fixed-contract API and the methods that exist.

​
FAQ

Not today. The coverage is on-chain: metadata, ownership and transfers. Marketplace pricing is not part of this group.
Lookups take a chain parameter alongside the contract address and token id, so the same tool serves any network the provider indexes. describe_tool lists the networks each tool accepts.
Yes for ownership and movement — the owner history of a token and the transfer history of a collection are lists of past events. Metadata and current owners reflect the chain at request time; nothing is served from a stale archive.