Query token holder data on Base via x402-paid crypto intelligence endpoint
What it does
This endpoint, operated by Erudite Intelligence LLC, returns token holder information for a given wallet/contract address and token on the Base network. It accepts a POST request with a JSON body containing an `address` (wallet or contract address) and a `token` (token address or symbol), and returns holder data in JSON format.
Payment is handled via the x402 protocol (version 2). The endpoint accepts two payment options: USDC on Base (eip155:8453) at 10,000 base units ($0.01 per call) or USDT on Tron (tron:728126428) at 10,000 base units ($0.01 per call). Settlement is facilitated through the EruditePay Bridge, which supports 20 blockchains and charges 0.5% per settlement. The Coinbase CDP facilitator is listed for the Base payment path.
The provider's landing page describes EruditePay as a FinCEN MSB-registered (BSA ID 31000324258137), non-custodial x402 payment facilitator. Documentation at docs.eruditepay.com is referenced but the /docs path on the bridge itself returns a 404. The output schema is minimal — the example response is `{"success": true, "data": {}}` — so the exact shape of the holder data returned is not documented in the probe material.
Capabilities
Use cases
- —Retrieve the list of holders for a specific token on Base
- —Analyze token distribution across wallets for due diligence
- —Power dashboards showing top holders of an ERC-20 token
- —Agent-driven portfolio or whale-tracking workflows
Fit
Best for
- —Agents needing on-chain token holder data on Base
- —Crypto analytics pipelines requiring per-call micropayments
- —Developers who want x402-native blockchain data endpoints
Not for
- —Querying holder data on chains other than Base (endpoint is Base-specific)
- —Use cases requiring detailed documentation or guaranteed response schemas
- —Free or high-volume bulk data extraction (each call costs $0.01)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/token/holders \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0xYourWalletOrContract", "token": "0xTokenAddress"}'Example
Request
{
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear schema for input, but the output example is a stub (`data: {}`) with no documentation of the actual response shape. No OpenAPI spec or detailed docs are available. Pricing is clear at $0.01/call.
Warnings
- —Output response schema is effectively undocumented — the example shows an empty `data` object
- —docs.eruditepay.com is referenced but /docs on the bridge returns 404
- —The exact fields returned in the holder data are unknown from available material
- —No rate limits or usage quotas are documented
Citations
- —Endpoint accepts USDC on Base at 10,000 base units ($0.01) and USDT on Tron at 10,000 base units ($0.01)https://bridge.eruditepay.com/v1/base/token/holders
- —Provider is Erudite Intelligence LLC, FinCEN MSB registered with BSA ID 31000324258137https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains and charges 0.5% per settlementhttps://bridge.eruditepay.com
- —Input schema requires address (wallet or contract address) and token (token address or symbol)https://bridge.eruditepay.com/v1/base/token/holders
- —Coinbase CDP facilitator is used for the Base payment pathhttps://bridge.eruditepay.com/v1/base/token/holders