x402basequality 0.45

Query NFT ownership data on Base via x402 micropayment (USDC or USDT).

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint returns NFT ownership information for a given collection on the Base blockchain. It is an x402-gated POST endpoint operated by Erudite Intelligence LLC. Callers send a JSON body containing a `collection` field (an NFT collection address or slug) and receive a JSON response indicating which NFTs are owned.

Payment is required per-call via the x402 protocol (version 2). The endpoint accepts two payment options: USDC on Base (EIP-155:8453) or USDT on Tron, both at an amount of 10,000 base units — which equals $0.01 per request (both USDC and USDT use 6 decimals). The facilitator for Base payments is Coinbase CDP. The provider is registered as a FinCEN MSB (BSA ID 31000324258137) and operates a non-custodial settlement model.

Documentation is sparse. The crawled landing page describes the EruditePay Bridge facilitator infrastructure but does not document the `/v1/base/nft/owned` data endpoint specifically. The Bazaar schema embedded in the 402 challenge provides the input/output contract: POST a JSON body with a `collection` string property, and receive `{"success": true, "data": {}}`. The exact structure of the `data` object is not documented, so consumers should expect an object whose shape may vary by collection.

Capabilities

nft-ownership-querybase-chain-nftx402-paymentusdc-paymentusdt-tron-paymentjson-apiper-call-micropayment

Use cases

  • Check which NFTs a collection has distributed and to whom on Base
  • Token-gate access by verifying NFT ownership for a specific collection
  • Build dashboards showing NFT holder distributions for Base collections
  • Integrate NFT ownership checks into trading bots or portfolio trackers

Fit

Best for

  • Developers needing per-call NFT ownership data without API key subscriptions
  • Agents that can pay with USDC on Base or USDT on Tron via x402
  • Applications requiring on-demand Base-chain NFT intelligence

Not for

  • Bulk historical NFT analytics requiring thousands of free queries
  • Multi-chain NFT queries beyond Base (endpoint is Base-specific)
  • Users who cannot make x402 crypto micropayments

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/nft/owned \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"collection": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"}'

Example

Request

{
  "collection": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"
}

Response

{
  "data": {},
  "success": true
}

Endpoint

Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (402 challenge captured) with a clear Bazaar schema for input, but the output data structure is only shown as an empty placeholder. No dedicated documentation exists for this specific endpoint — the crawled docs path returns 404. Pricing is clear ($0.01/call) but the actual response payload is undocumented.

Warnings

  • No dedicated documentation for /v1/base/nft/owned — the docs URL returns endpoint_not_found
  • The example output in the Bazaar schema shows an empty data object; actual response structure is unknown
  • The endpoint description in the 402 challenge is generic ('Crypto data intelligence') and does not specifically describe NFT ownership

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:51:21Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access