Query token supply data on Base via x402-paid crypto intelligence endpoint.
What it does
This endpoint, hosted by Erudite Intelligence LLC on their EruditePay Bridge infrastructure, returns token supply data for tokens on the Base network. It accepts a POST request with a JSON body containing a token address (or symbol) and returns supply information. The endpoint is gated by the x402 payment protocol (v2), requiring per-call payment of 0.01 USDC on Base (eip155:8453) or 0.01 USDT on Tron before the response is served.
The x402 challenge confirms the endpoint is live and describes itself as "Crypto data intelligence." The Bazaar schema extension specifies the input format: a JSON body with a `token` field (string, representing a token address or symbol). The output is a JSON object with `success` (boolean) and `data` (object), though the example output's `data` field is empty, so the exact shape of the returned supply data is not documented.
The provider (EruditePay) is primarily an x402 payment facilitator supporting 20 blockchains, registered as a FinCEN MSB. This particular endpoint appears to be a data intelligence service built on top of that infrastructure rather than the facilitator itself. Documentation at docs.eruditepay.com was referenced on the landing page but the /docs path on the bridge returns a 404, and no OpenAPI spec is available, leaving the response schema largely undocumented.
Capabilities
Use cases
- —Querying total or circulating supply of a token on Base for portfolio dashboards
- —Automated agents checking token supply before executing trades
- —DeFi protocols verifying token supply as part of risk assessment
- —Data aggregators collecting supply metrics across tokens
Fit
Best for
- —Agents needing on-demand token supply data with crypto-native payment
- —Programmatic access to Base network token supply without API keys
- —x402-compatible clients that can pay per-call in USDC or USDT
Not for
- —Bulk historical supply data retrieval (no batch or time-series documented)
- —Free or subscription-based access — every call requires a micropayment
- —Non-Base-network token supply queries (endpoint path specifies Base)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/token/supply \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'Example
Request
{
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear payment scheme and basic input schema from the Bazaar extension. However, the output schema is essentially empty (example data is {}), there is no OpenAPI spec, and the dedicated docs page returns 404. The actual response structure for supply data must be inferred.
Warnings
- —Output schema is undocumented — the example response contains an empty data object
- —docs.eruditepay.com referenced on landing page but /docs on bridge returns 404
- —No OpenAPI or detailed API documentation available for this specific endpoint
- —Response shape for token supply data is unknown — callers must discover it empirically
Citations
- —Endpoint returns x402 v2 challenge with 0.01 USDC on Base or 0.01 USDT on Tron pricinghttps://bridge.eruditepay.com/v1/base/token/supply
- —Provider is Erudite Intelligence LLC, FinCEN MSB registered (BSA ID 31000324258137)https://bridge.eruditepay.com
- —Endpoint self-describes as 'Crypto data intelligence'https://bridge.eruditepay.com/v1/base/token/supply
- —Input schema requires a JSON body with a 'token' field (token address or symbol)https://bridge.eruditepay.com/v1/base/token/supply
- —EruditePay Bridge supports 20 blockchains as an x402 facilitatorhttps://bridge.eruditepay.com