Multi-chain address intelligence check via x402 micropayment on Base (USDC) or Tron (USDT).
What it does
This endpoint from Erudite Intelligence LLC accepts a wallet or contract address and returns cross-chain intelligence data about it. The service is accessed via the x402 payment protocol: callers pay $0.01 per request (10,000 base units of USDC on Base or USDT on Tron, both 6-decimal tokens). The endpoint accepts a POST with a JSON body containing an `address` field and returns a JSON object with a `success` boolean and a `data` object.
The endpoint is live and returns a standard x402 v2 payment challenge. Two payment rails are supported: USDC on Base (eip155:8453) settled through the Coinbase CDP facilitator, and Tether USDT on Tron (tron:728126428). The maximum payment timeout is 300 seconds for both options. The provider, Erudite Intelligence LLC, also operates the EruditePay x402 Bridge facilitator that supports 20 blockchains.
Documentation is sparse — the crawled /docs path returns a 404, and the bazaar schema embedded in the x402 challenge provides only a minimal example (an empty `data` object). The exact fields returned in the `data` object for a real address are not documented in the available material, so consumers should expect to discover the response shape experimentally. The endpoint description in the challenge is simply "Crypto data intelligence."
Capabilities
Use cases
- —Check whether a wallet or contract address has activity across multiple blockchains
- —Screen addresses for compliance or risk assessment workflows
- —Enrich blockchain address data in agent-driven crypto analytics pipelines
- —Integrate address intelligence into x402-compatible payment-gated applications
Fit
Best for
- —Agents or services that need quick per-address blockchain intelligence
- —x402-native workflows that can pay per call in USDC or USDT
- —Cross-chain address lookups without managing multiple chain RPCs
Not for
- —Bulk batch processing of millions of addresses (pay-per-call at $0.01 each adds up)
- —Use cases requiring detailed documented response schemas before integration
- —Non-crypto address validation (email, postal, etc.)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/cross/address/multi-chain-check \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0x1234567890abcdef1234567890abcdef12345678"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live and returns a well-formed x402 v2 challenge with clear pricing and two payment options. However, documentation is effectively absent (docs path 404s), the response example shows only an empty data object, and the actual fields returned for a real address are unknown. The description 'Crypto data intelligence' is vague.
Warnings
- —No external documentation available — /docs returns 404
- —Response schema is unknown; the only example shows an empty data object
- —The endpoint description 'Crypto data intelligence' is vague and does not specify what data is returned
- —No OpenAPI spec available
Citations
- —The endpoint returns an x402 v2 challenge with USDC on Base (amount 10000) and USDT on Tron (amount 10000), both with 300s timeouthttps://bridge.eruditepay.com/v1/cross/address/multi-chain-check
- —USDC on Base uses asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (6 decimals), making 10000 base units = $0.01https://bridge.eruditepay.com
- —Provider is Erudite Intelligence LLC, FinCEN MSB registered with BSA ID 31000324258137https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains and implements x402 facilitator specification v2.0.0https://bridge.eruditepay.com