Query NFT transfer data on Base via x402-paid POST endpoint
What it does
This endpoint at bridge.eruditepay.com provides NFT transfer intelligence on the Base blockchain. It accepts a POST request with a transaction hash and/or NFT collection address and returns structured transfer data. Payment is handled via the x402 protocol: callers must pay $0.01 per request in USDC on Base (eip155:8453) or USDT on Tron (tron:728126428).
The endpoint is operated by Erudite Intelligence LLC, which also runs the EruditePay x402 Bridge — a payment facilitator supporting 20 blockchains. The Bridge itself handles verify/settle steps for x402 payments. This particular endpoint is a data endpoint (not the facilitator itself) described as "Crypto data intelligence" in the x402 challenge. The input schema requires a JSON body with `hash` (transaction hash) and `collection` (NFT collection address or slug). The output returns a JSON object with a `success` boolean and a `data` object, though the exact shape of the data payload is not documented beyond the example stub.
Documentation is sparse — the provider's /docs path returns a 404, and no OpenAPI spec is available. The endpoint is live and returns a well-formed x402 v2 challenge on unauthenticated POST requests. The facilitator for payment settlement is Coinbase CDP (api.cdp.coinbase.com).
Capabilities
Use cases
- —Retrieve NFT transfer records for a specific transaction hash on Base
- —Look up transfer activity for an NFT collection by contract address
- —Enrich blockchain analytics pipelines with NFT movement data
- —Verify NFT provenance by tracing transfer history
Fit
Best for
- —Agents needing on-demand NFT transfer data on Base
- —Blockchain analytics tools requiring per-call paid data access
- —Applications tracking NFT collection activity programmatically
Not for
- —Querying NFT data on chains other than Base (endpoint is Base-specific)
- —Free or high-volume bulk data extraction (each call costs $0.01)
- —Getting full NFT metadata or images (this is transfer data only)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/nft/transfers \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{"hash": "0xabc...123", "collection": "0xdef...456"}'Example
Request
{
"hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
"collection": "0x0000000000000000000000000000000000000000"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live with a valid x402 v2 challenge and includes a basic input/output schema via the Bazaar extension. However, documentation is effectively absent (no OpenAPI spec, /docs returns 404), the output data shape is a stub with an empty object, and there are no real response examples showing what NFT transfer data actually looks like.
Warnings
- —No OpenAPI or detailed API documentation available — /docs returns 404
- —Output schema example is a stub ({"success": true, "data": {}}) with no detail on actual transfer data fields
- —The endpoint description is generic ('Crypto data intelligence') and does not specifically confirm NFT transfer functionality beyond the URL path
- —Tron payment option uses asset address TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t (USDT) — callers should verify chain compatibility
Citations
- —Endpoint returns x402 v2 challenge with $0.01 USDC on Base and $0.01 USDT on Tronhttps://bridge.eruditepay.com/v1/base/nft/transfers
- —Operated by Erudite Intelligence LLC, FinCEN MSB registeredhttps://bridge.eruditepay.com
- —Payment facilitator is Coinbase CDP at api.cdp.coinbase.com/platform/v2/x402https://bridge.eruditepay.com/v1/base/nft/transfers
- —Input schema accepts hash (transaction hash) and collection (NFT collection address or slug)https://bridge.eruditepay.com/v1/base/nft/transfers
- —EruditePay Bridge supports 20 blockchains with 0.5% per settlement feehttps://bridge.eruditepay.com