NFT Data is a pay-per-request multichain API for AI agents and developer tools, providing structured market data for OpenSea collections across 30 networks. Send a collection slug and get floor price, 24h/7d/30d/lifetime sales and volume, total supply, unique owners, contract addresses and creation date. Data is sourced from OpenSea API v2, with currencies reported as provided by the source (ETH, USDC, etc.).
Each successful non-cached request costs $0.002, payable in USDC using x402 v2 (Base Mainnet or Solana Mainnet) or MPP evm/charge (Base Mainnet). No API keys or subscriptions required. NFT Data is also available through a free website and an MCP server for AI agents.
Website
Explore NFT collections and market data for free at nftdata.app.
Paid API
Access the same data programmatically:
POST https://www.nftdata.app/api/get-collection-data
Each successful request costs $0.002 in USDC.
- x402 v2 on Base and Solana mainnet
- MPP (
evm/charge) on Base mainnet
MCP Server
The NFT Data MCP server provides an MCP interface to NFT Data through the get_collection_data tool. It supports x402 and MPP payments on Base mainnet at $0.002 per successful call.
- PayAI Ecosystem: https://payai.network/ecosystem/nft-data
- OpenSea Tool #778 (ERC-8257): https://opensea.io/tools/erc8257/base/778
- Poncho: https://tryponcho.com/m/nftdata.app
- x402scan: https://www.x402scan.com/server/0ee65334-846e-433a-bc38-55a37ffe841a
- Agent402 Marketplace: https://agent402.tools/marketplace/tools?q=www.nftdata.app
- Circle Agent Readiness (100/100): https://agents.circle.com/sell/score?url=www.nftdata.app
| Field | Value |
|---|---|
| Tool ID | 778 |
| Network | Base (chain ID 8453) |
| Registry contract | 0x265bb2dbfc0a8165c9a1941eb1372f349bad2cf1 |
| Registry page | https://opensea.io/tools/erc8257/base/778 |
| Action | get_collection_data |
| Payment | OpenSea Tool #778: x402 v2 on Base mainnet (USDC). The public API additionally supports x402 v2 on Solana mainnet and MPP evm/charge on Base mainnet. Price: $0.002 per successful request. |
| Manifest | https://www.nftdata.app/.well-known/ai-tool/nft-data.json |
NFT Data is available as a Farcaster Mini App. Open it inside Warpcast or any Farcaster client to look up NFT collection statistics without leaving the app.
Mini App URL: https://farcaster.xyz/miniapps/xGfhsTicjUjY/nft-data
NFT Data is also available through Poncho, providing another discovery point for AI agents to find and try the service.
Try NFT Data on Poncho: https://tryponcho.com/m/nftdata.app
NFT Data is available as a published MCP server (nftdata-mcp) for developers and AI agents using local MCP clients over stdio.
npx -y nftdata-mcp
The MCP server exposes the get_collection_data tool, which calls the NFT Data API and pays for each request on Base mainnet using either x402 or MPP. Each successful request costs $0.002 in USDC. The MCP server pays on Base mainnet only; Solana payments are supported by the main NFT Data API, not by the MCP server.
Requirements:
- Node.js 20 or newer.
- A dedicated EVM wallet funded with USDC on Base mainnet. Do not use a primary wallet.
- Set the
EVM_PRIVATE_KEYenvironment variable to the private key of that dedicated wallet.
Installing the MCP server is optional. The NFT Data API remains directly accessible without it.
- GitHub: https://github.com/Nomad07/nftdata-mcp
- npm: https://www.npmjs.com/package/nftdata-mcp
- MCP Registry: https://registry.modelcontextprotocol.io/?q=nftdata
Endpoint: https://www.nftdata.app/api/get-collection-data
POST https://www.nftdata.app/api/get-collection-data
Content-Type: application/json
The endpoint accepts valid payment credentials through either x402 v2 or MPP evm/charge. Requests without a valid payment credential receive HTTP 402. See x402 Payment and MPP Payment below.
The endpoint accepts 0.002 USDC per successful call via x402 v2 (exact scheme) on Base mainnet or Solana mainnet. Use whichever network your client supports.
Base mainnet (EVM)
| Field | Value |
|---|---|
| Network | Base (eip155:8453) |
| Token | USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) |
| Amount | 2000 atomic units (0.002 USDC) |
| Scheme | exact |
| Recipient | 0x344143199642E87320785823C20c2dF107D17534 |
Solana mainnet (SVM)
| Field | Value |
|---|---|
| Network | Solana mainnet (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp) |
| Token | USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v) |
| Amount | 2000 atomic units (0.002 USDC) |
| Scheme | exact |
| Recipient | 8MdycJfWSD8KxL8n2kSzEU9Ryuo1EuJALkq8ezrK9i3m |
The 402 response uses the x402 v2 format -- payment requirements for both networks are encoded in the PAYMENT-REQUIRED response header. The endpoint also exposes the official Bazaar discovery extension under extensions.bazaar, which describes the POST JSON input schema and an example response. Bazaar-compatible x402 clients can discover this endpoint through that extension.
To call this tool from an OpenSea-compatible agent, reference it by its on-chain coordinates:
8453,0x265bb2dbfc0a8165c9a1941eb1372f349bad2cf1,778
The endpoint also accepts payment via MPP (Machine Payments Protocol) using the evm/charge method.
| Field | Value |
|---|---|
| Protocol | MPP evm/charge |
| Network | Base mainnet (eip155:8453) |
| Token | USDC on Base mainnet |
| Amount | 2000 atomic units (0.002 USDC, 6-decimal token) |
Payment flow:
- An initial request without a valid MPP credential receives
HTTP 402 Payment Required. The response includes an MPP challenge in theWWW-Authenticateheader. - A compatible client resolves the challenge and retries with
Authorization: Payment <mpp evm credential>. - A successful
200response includes theMPP-Receiptheader confirming settlement.
The endpoint also accepts Payment-Authorization: Payment <credential> as a fallback for proxy configurations that preserve the application Authorization header separately.
The payment credential is bound to the challenge. MPP and x402 payment credentials are mutually exclusive for a single request -- a request may carry one or the other, not both.
Settlement is attempted only after collection data has been retrieved successfully. Requests that fail input validation (HTTP 400) or encounter an upstream data error do not proceed to settlement.
{
"collection": "milady"
}collection is the OpenSea collection slug — the unique identifier visible in the collection's URL, for example milady from opensea.io/collection/milady or basedpunks from opensea.io/collection/basedpunks.
Validation: the slug must be lowercase alphanumeric and may contain hyphens or underscores. Uppercase letters, spaces, and special characters are rejected with HTTP 400.
A successful HTTP 200 response contains the following 20 fields:
| Field | Type | Description |
|---|---|---|
name |
string |
Collection display name |
slug |
string |
Collection slug |
contracts |
array |
NFT contract addresses and their chains |
floor_price |
number |
Current floor price |
floor_price_currency |
string |
Currency symbol for the floor price |
one_day_sales |
number |
Sales count in the last 24 hours |
one_day_volume |
number |
Trading volume in the last 24 hours |
one_day_volume_currency |
string | null |
Currency symbol for 24-hour volume; null if not reported |
seven_day_sales |
number | null |
Sales count in the last 7 days; null if not reported |
seven_day_volume |
number | null |
Trading volume in the last 7 days; null if not reported |
seven_day_volume_currency |
string | null |
Currency symbol for 7-day volume; null if not reported |
thirty_day_sales |
number | null |
Sales count in the last 30 days; null if not reported |
thirty_day_volume |
number | null |
Trading volume in the last 30 days; null if not reported |
thirty_day_volume_currency |
string | null |
Currency symbol for 30-day volume; null if not reported |
total_sales |
number |
Lifetime sales count |
total_volume |
number |
Lifetime trading volume |
total_volume_currency |
string | null |
Currency symbol for lifetime volume; null if not reported |
num_owners |
number |
Current unique owner count |
total_supply |
number | null |
Total NFTs in the collection; null if not reported |
created_date |
string | null |
ISO 8601 creation date; null if not reported |
Currency values (floor_price_currency, *_volume_currency) are returned directly from OpenSea and vary by collection and network. Examples include ETH, WETH, USDC, APE, RON, HYPE, and others. Do not assume all volume is ETH.
The OpenSea API supports 30 networks. The table below lists production-tested examples across a subset of those networks.
| Network | Slug | Contract |
|---|---|---|
| Base | basedpunks |
0xcb28749c24af4797808364d71d71539bc01e76d4 |
| Base | gribbits |
0x38b7446dd746a98a101ec0bf1a0717784c4dc69f |
| Ink | rekt-ink |
0x25aa78ab6785a4b0aeff5c170998992fd958d43d |
| Ink | prtscn-ink |
0x3ea71c6abde8a1b3cf6e5683761a7378b4e9e448 |
| Robinhood Chain | quotrons404 |
0x027aca2794e44f24950d81227dcd516ffbb49d6e |
| Robinhood Chain | rare-friends-genesis |
0x116eaa62241751e0c98da43d458600c6c17cd361 |
| HyperEVM | hypurr-hyperevm |
0x9125e2d6827a00b0f8330d6ef7bef07730bac685 |
| HyperEVM | hypio |
0x63eb9d77d083ca10c304e28d5191321977fd0bfb |
| HyperEVM | rekt-wolves-hype |
0x822c4f30414299e003ef39e9aba49d8f8d4445ba |
| Arc | akarii |
0xbea22653119f73716905919708a612332bf98e3f |
| Ronin | axie-land |
0x8c811e3c958e190f5ec15fb376533a3398620500 |
| Ronin | moki-collection |
0x47b5a7c2e4f07772696bbf8c8c32fe2b9eabd550 |
| ApeChain | gimboznft |
0x81c9ce55e8214fd0f5181fd3d38f52fd8c33ec38 |
| ApeChain | gobs-on-ape |
0xbebaa24108d6a03c7331464270b95278bbbe6ff7 |
| Ethereum | azuki |
0xed5af388653567af2f388e6224dc7c4b3241c544 |
| Ethereum | pudgypenguins |
0xbd3531da5cf5857e7cfaa92426877b022e612cf8 |
| Solana | claynosaurz |
6mszaj17KSfVqADrQj3o4W3zoLMTykgmV37W4QadCczK |
| Solana | mad-lads |
J1S9H3QjnRtBbbuD4HjPV6RpRhwuk4zKbxsnCHuTgh9w |
These examples have been tested in production and are not representative of all 30 supported networks.
NFT Data supports collection lookups across 30 networks. The following examples demonstrate collection discovery across five different networks.
| Network | Collection | Explore |
|---|---|---|
| Arc | AKARII | www.nftdata.app/?collection=akarii |
| Solana | Mad Lads | www.nftdata.app/?collection=mad-lads |
| Ethereum | Azuki | www.nftdata.app/?collection=azuki |
| Base | OK Computers | www.nftdata.app/?collection=okcomputers |
| Ink | Templars of the Storm | www.nftdata.app/?collection=templars-of-the-storm |
NFT Data is strictly read-only. It does not:
- require a user wallet or private key
- sign transactions
- purchase, sell, list, offer on, or transfer NFTs
- perform any on-chain write operations
The OpenSea API key is held server-side and is never exposed to callers or included in any response.
API versus MCP Server: the main NFT Data API does not require API users to provide a wallet or private key. The MCP Server is a separate local client that pays for each request, so it uses a dedicated funded wallet configured through EVM_PRIVATE_KEY.
Responses are cached in-memory for 60 seconds per worker instance. The API runs on Vercel's Node.js runtime — multiple isolated instances may be active simultaneously, so cache hits are best-effort within a single warm instance, not globally shared. Cold instances always fetch from the OpenSea API.
| Status | Meaning |
|---|---|
200 |
Success — response body contains collection data |
400 |
Invalid request — malformed slug, missing field, or OpenSea rejected the input |
402 |
Payment required — no valid x402 or MPP payment credential supplied |
404 |
Collection not found — slug does not match any OpenSea collection |
429 |
Rate limited — OpenSea upstream rate limit hit; Retry-After header forwarded if present |
500 |
Unexpected server error |
502 |
Upstream error — OpenSea API returned a 5xx or unexpected response |
| Variable | Required | Description |
|---|---|---|
OPENSEA_API_KEY |
Yes | OpenSea API v2 key. Used server-side only; never exposed to callers. |
MPP_SECRET_KEY |
Yes (paid endpoint) | Secret key (at least 32 bytes) used by the MPP payment flow of /api/get-collection-data to bind payment challenges to their contents. The MPP library throws "Missing secret key" if it is not set. |
TOOL_ENDPOINT |
No | Override the manifest endpoint URL. Defaults to https://www.nftdata.app/api/get-collection-data. |
The ERC-8257 AI tool manifest is served at:
https://www.nftdata.app/.well-known/ai-tool/nft-data.json
It describes the tool action, input/output schema, pricing, and creator address for agent and registry discovery. The manifest is generated from src/manifest.ts using @opensea/tool-sdk.
api/
get-collection-data.ts # Paid Vercel Node.js function (x402 and MPP payment-gated)
collect.ts # Free Edge function for the website UI (origin-checked)
analyze.ts # Edge function for the website UI's AI analysis (origin-checked)
well-known/
[slug].ts # Serves the ERC-8257 manifest
src/
handler.ts # Tool handler, input/output schemas, error mapping
manifest.ts # ERC-8257 manifest definition
opensea.ts # OpenSea API v2 client and in-memory cache
test/
payment-routing.test.ts # Payment routing tests (run with npm test)
public/
index.html # Static website frontend
docs/ # API documentation pages (index.html, mcp/index.html)
openapi.json # OpenAPI 3.1 discovery document for API clients, agents and registries
.well-known/ # x402, farcaster.json and x402gle-challenge.json discovery files
nftdata-banner.png # README banner
nft-data-icon.svg # Tool icon (256×256)
nft-data-banner.svg # Featured banner (1200×400)
favicon.svg # Favicon (32×32)
nft-data-*.png # Site logo, icon and preview images
env.example # Example environment variables
vercel.json # Build config and /.well-known/ai-tool/* rewrite
tsconfig.json # TypeScript config (NodeNext, strict)
tsconfig.test.json # TypeScript config for tests
package.json # Dependencies and scripts
Requirements: Node.js ≥ 18, Vercel CLI
# Install dependencies
npm install
# Set environment variables
cp env.example .env
# Edit .env and add your OPENSEA_API_KEY
# Run locally
npm run dev # vercel dev — serves API routes and static files
# Type-check
npm run build
# Run the tests
npm test
# Validate the ERC-8257 manifest
npm run validate-manifestMIT
