Retrieve NFT collection metadata on Base via x402 micropayment
What it does
This x402-enabled endpoint returns NFT collection metadata when given a collection address or slug. It is operated by Erudite Intelligence LLC and accepts payment via the x402 protocol (version 2). The endpoint accepts a POST request with a JSON body containing a `collection` field (an NFT collection address or slug) and returns a JSON response with a `success` boolean and a `data` object.
Pricing is set at 10,000 base units of USDC on Base (eip155:8453) or USDT on Tron (tron:728126428). Since both USDC and USDT use 6 decimals, the per-call cost is $0.01 (one cent). Payment is facilitated through the EruditePay Bridge, which supports the Coinbase CDP facilitator for Base and direct settlement on Tron. The maximum payment timeout is 300 seconds.
Documentation beyond the x402 challenge and the Bazaar schema extension is sparse. The endpoint description in the challenge is simply "Crypto data intelligence," and no detailed field-level documentation for the response `data` object is available. The example output shows an empty `data` object, so the actual structure of returned metadata is unknown. The provider's landing page focuses on the EruditePay Bridge facilitator service rather than this specific NFT metadata endpoint.
Capabilities
Use cases
- —Retrieve metadata for an NFT collection by contract address
- —Enrich NFT portfolio dashboards with collection-level information
- —Automate NFT collection discovery and cataloging
- —Feed NFT metadata into trading or analytics agents
Fit
Best for
- —Agents needing on-demand NFT collection metadata with micropayment access
- —Developers building NFT analytics tools on Base
- —Automated workflows that need pay-per-call NFT data without API key management
Not for
- —Bulk retrieval of metadata for thousands of collections (per-call cost adds up)
- —Querying individual token-level metadata (endpoint is collection-scoped)
- —Users who need free or subscription-based NFT data APIs
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/nft/metadata \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"collection": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"}'Example
Request
{
"collection": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear Bazaar schema for input, but the response data structure is entirely unspecified (example shows empty object). No dedicated documentation exists for this endpoint, and the provider's docs URL returns a 404. The description 'Crypto data intelligence' is vague.
Warnings
- —Response data structure is unknown — the example output contains an empty data object
- —No dedicated API documentation available (docs endpoint returns 404)
- —Endpoint description is vague ('Crypto data intelligence') with no field-level output documentation
- —Actual metadata fields returned for a real collection are unverified
Citations
- —Endpoint accepts POST with a collection field (NFT collection address or slug) and returns JSON with success and data fieldshttps://bridge.eruditepay.com/v1/base/nft/metadata
- —Price is 10,000 base units of USDC on Base (eip155:8453) or USDT on Tron, equaling $0.01 per callhttps://bridge.eruditepay.com/v1/base/nft/metadata
- —Operated by Erudite Intelligence LLC, FinCEN MSB registeredhttps://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains and uses x402 v2.0 protocolhttps://bridge.eruditepay.com