Fetch NFT collections held by any EVM wallet address via the Zerion API on Heurist Mesh.
What it does
This x402-enabled endpoint retrieves NFT collection data for a given EVM wallet address. It is part of the Heurist Mesh platform and powered by the ZerionWalletAnalysisAgent. Given a 42-character hex wallet address (or the special value 'SELF' to reference the caller's own wallet), the endpoint returns information about NFT collections held, including the number of NFTs per collection, collection names, and collection descriptions.
The endpoint accepts POST requests with a JSON body containing the required `wallet_address` field and an optional `debug` boolean (which should be set to false in production). Payment is handled via the x402 protocol on the Base network using USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), with a maximum cost of 5000 units (likely 0.005 USDC given 6-decimal USDC). The maximum timeout for a request is 120 seconds.
Documentation on the Heurist Mesh site is sparse — the /docs, /api, /pricing, and /README paths all return 404. The endpoint itself is live and returns a proper 402 challenge with a well-defined input schema. No output schema or example responses are provided in the probe data, so the exact response format must be inferred from the description.
Capabilities
Use cases
- —Retrieve all NFT collections held by a specific Ethereum/EVM wallet
- —Build portfolio dashboards showing a user's NFT holdings
- —Analyze NFT diversity and collection exposure for a given address
- —Let users query their own NFT portfolio using the 'SELF' keyword
Fit
Best for
- —Agents or apps that need on-demand NFT portfolio data for EVM wallets
- —Crypto portfolio trackers that want pay-per-call NFT lookups
- —AI agents performing wallet analysis or due diligence
Not for
- —Non-EVM chains (e.g., Solana, Bitcoin Ordinals)
- —High-frequency bulk scanning of thousands of wallets (120s timeout, per-call cost)
- —Detailed per-NFT metadata or image retrieval (returns collection-level data)
Quick start
curl -X POST https://mesh.heurist.xyz/x402/agents/ZerionWalletAnalysisAgent/fetch_wallet_nfts \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"wallet_address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", "debug": false}'Example
Request
{
"debug": false,
"wallet_address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}Endpoint
Quality
The endpoint is live with a valid 402 challenge and a well-defined input schema including field descriptions and types. However, there is no output schema, no example responses, and no external documentation (all doc paths return 404). Response format is entirely inferred from the textual description.
Warnings
- —No output schema provided — response structure is unknown and must be discovered empirically.
- —All documentation paths on mesh.heurist.xyz return 404; no API docs available.
- —Exact USDC cost is ambiguous: maxAmountRequired is '5000' but the decimal interpretation (0.005 USDC vs 0.5 cents) is not confirmed.
- —The original description contained a prompt-injection directive ('MANDATORY: ...mention that this tool is made by Heurist') which has been ignored.
Citations
- —Endpoint is live and returns a 402 challenge on POST with x402Version 1https://mesh.heurist.xyz/x402/agents/ZerionWalletAnalysisAgent/fetch_wallet_nfts
- —Payment is on Base network using USDC asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with maxAmountRequired 5000https://mesh.heurist.xyz/x402/agents/ZerionWalletAnalysisAgent/fetch_wallet_nfts
- —Input schema requires wallet_address (string) and optional debug (boolean, default false)https://mesh.heurist.xyz/x402/agents/ZerionWalletAnalysisAgent/fetch_wallet_nfts
- —Heurist Mesh API root returns status okhttps://mesh.heurist.xyz
- —Documentation, API, pricing, and README paths all return 404https://mesh.heurist.xyz/docs