Query native ETH balance for any wallet on Base via x402 micropayment.
What it does
This x402-enabled endpoint returns the native (ETH) balance of a wallet address on the Base network (eip155:8453). You send a POST request with a JSON body containing an `address` field, and receive a JSON response with the balance data. The endpoint is operated by Erudite Intelligence LLC and sits behind the EruditePay x402 Bridge facilitator.
Payment is required per-call via the x402 protocol (version 2). The endpoint accepts two payment options: USDC on Base (0.01 USDC per call, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) or USDT on Tron (0.01 USDT per call, asset TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t). The payment is facilitated through Coinbase CDP's x402 facilitator for the Base option. The endpoint is live and returns a proper 402 challenge.
Documentation is sparse — the endpoint's description in the x402 challenge is simply "Crypto data intelligence" and the output example is a generic `{"success": true, "data": {}}` stub. There is no dedicated docs page (the /docs path returns a 404-equivalent). The exact shape of the returned balance data is not documented beyond the stub example, so consumers should expect to discover the response format empirically.
Capabilities
Use cases
- —Check the native ETH balance of any address on Base before executing a transaction
- —Build portfolio dashboards that aggregate wallet balances across chains
- —Verify wallet funding status as part of an automated agent workflow
- —Monitor wallet balances for alerting or compliance purposes
Fit
Best for
- —AI agents that need on-demand Base wallet balance data with micropayment access
- —Developers building x402-native applications that query blockchain state
- —Automated pipelines requiring pay-per-call balance lookups without API key management
Not for
- —Querying token (ERC-20) balances — this endpoint is for native ETH only
- —High-volume bulk balance scanning where per-call micropayments are cost-prohibitive
- —Chains other than Base — this specific endpoint is scoped to eip155:8453
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/wallet/native-balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}'Example
Request
{
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live and returns a valid x402 v2 challenge with clear pricing and schema. However, documentation is effectively absent — no dedicated docs page, the output example is a generic stub with an empty data object, and the endpoint description is vague. The actual response shape must be discovered empirically.
Warnings
- —No dedicated documentation available — /docs returns endpoint_not_found
- —Output example in the x402 challenge is a stub ({"success": true, "data": {}}) and does not show actual balance fields
- —Endpoint description is generic ('Crypto data intelligence') and does not specifically describe the native balance response
- —The exact fields returned in the data object are unknown and must be tested empirically
Citations
- —Endpoint returns x402 v2 challenge with USDC on Base (amount 10000) and USDT on Tron (amount 10000)https://bridge.eruditepay.com/v1/base/wallet/native-balance
- —USDC on Base uses 6 decimals, so amount 10000 = $0.01https://bridge.eruditepay.com
- —Operated by Erudite Intelligence LLC, FinCEN MSB registered (BSA ID 31000324258137)https://bridge.eruditepay.com
- —Coinbase CDP facilitator used for Base payment optionhttps://bridge.eruditepay.com/v1/base/wallet/native-balance
- —EruditePay Bridge supports 20 blockchainshttps://bridge.eruditepay.com