Look up token metadata on Base via x402-paid crypto data intelligence endpoint.
What it does
This endpoint, hosted by Erudite Intelligence LLC on the EruditePay Bridge, provides crypto token metadata for tokens on the Base network. You send a POST request with a token address (or symbol) in the JSON body, and receive structured metadata about that token. The endpoint is gated by the x402 protocol (v2), requiring per-call payment of 0.01 USDC (on Base, via Coinbase CDP facilitator) or 0.01 USDT (on Tron).
The x402 challenge confirms the endpoint is live and describes itself as "Crypto data intelligence." The input schema accepts a JSON body with a `token` field (a token address or symbol string). The output is a JSON object with a `success` boolean and a `data` object, though the exact shape of the returned metadata is not documented beyond the example stub `{"success": true, "data": {}}`. No OpenAPI spec or dedicated documentation page was found — the /docs path returns a 404.
The provider (EruditePay Bridge) is a FinCEN MSB-registered x402 facilitator supporting 20 blockchains. The Bridge itself primarily offers verify/settle services for x402 payments, but this particular endpoint appears to be a standalone paid data endpoint rather than part of the facilitator infrastructure. Pricing is 0.01 USDC or 0.01 USDT per call (10,000 base units with 6 decimals).
Capabilities
Use cases
- —Retrieve metadata for a token contract address on Base before executing a trade
- —Enrich a portfolio dashboard with token names, symbols, and other metadata
- —Validate token addresses by checking their on-chain metadata
- —Power an AI agent's crypto research workflow with structured token data
Fit
Best for
- —Agents or apps needing on-demand token metadata via a simple POST call
- —Developers who want x402-native pay-per-call crypto data without API keys
- —Workflows that already use x402 payment flows and need token intelligence
Not for
- —Bulk historical token data or analytics (single-call, single-token design)
- —Users who need free or API-key-based token metadata (this requires crypto micropayment per call)
- —Non-Base-chain token lookups (endpoint path specifies /base/)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/token/metadata \
-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 x402 challenge is live and provides a schema for input/output, but the output example is a stub with an empty data object. No OpenAPI spec, no dedicated docs, and no real example response showing what metadata fields are returned. Pricing and payment details are clear.
Warnings
- —No documentation found — /docs returns 404
- —Output example is a stub with empty data object; actual response fields are unknown
- —Endpoint description is generic ('Crypto data intelligence') with no detail on what metadata fields are returned
- —The endpoint path suggests Base-chain-specific data but this is inferred from the URL, not documented
Citations
- —Endpoint returns x402 v2 challenge with 10000 base-unit USDC on Base and 10000 base-unit USDT on Tronhttps://bridge.eruditepay.com/v1/base/token/metadata
- —Provider is Erudite Intelligence LLC, FinCEN MSB registered (BSA ID 31000324258137)https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains and charges 0.5% per settlementhttps://bridge.eruditepay.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base (eip155:8453) with Coinbase CDP facilitatorhttps://bridge.eruditepay.com/v1/base/token/metadata