Query token transfer history for any wallet on Base via x402 micropayment.
What it does
This x402-gated endpoint from Erudite Intelligence LLC returns token transfer data for a specified wallet address and token on the Base network. You POST a JSON body containing an `address` (wallet or contract address) and a `token` (token address or symbol), and receive structured JSON with transfer intelligence.
Payment is handled via the x402 protocol (version 2). The endpoint accepts two payment options: USDC on Base (EIP-155:8453) or USDT on Tron, both at 10,000 base units per call — which equals $0.01 per request (6-decimal stablecoins). The facilitator is Coinbase CDP's x402 service for the Base option. The provider, Erudite Intelligence LLC, operates the EruditePay Bridge, a FinCEN MSB-registered x402 facilitator supporting 20 blockchains.
The response schema is minimal in the probe: `{"success": true, "data": {}}`. The exact shape of the `data` object for token transfers is not documented in the crawled material — the docs endpoint at `/docs` returns a 404. This limits confidence in the precise fields returned, though the endpoint description labels it "Crypto data intelligence" and the URL path (`/v1/base/wallet/token-transfers`) strongly implies it returns historical transfer records for the given wallet and token on Base.
Capabilities
Use cases
- —Retrieve token transfer history for a specific wallet on Base
- —Monitor wallet activity for compliance or analytics dashboards
- —Feed on-chain transfer data into trading or portfolio tracking agents
- —Audit token movements for a specific ERC-20 contract on Base
Fit
Best for
- —Agents needing per-call crypto wallet transfer data without API key subscriptions
- —Developers building Base-chain analytics with micropayment-gated access
- —Automated compliance checks on wallet token flows
Not for
- —Querying chains other than Base (endpoint is Base-specific)
- —High-volume bulk data extraction where per-call pricing adds up
- —Use cases requiring fully documented response schemas before integration
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/wallet/token-transfers \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0xYourWalletAddress", "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'Example
Request
{
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with clear pricing and a basic input schema, but the output schema is essentially a stub (`data: {}`), docs return 404, and there are no examples of actual response payloads. The exact fields returned for token transfers must be discovered empirically.
Warnings
- —Documentation endpoint (/docs) returns 404 — no detailed API reference available.
- —Response data schema is a stub; the actual structure of the `data` field is unknown.
- —Output example in the probe is just `{"success": true, "data": {}}` — real response shape is undocumented.
Citations
- —Endpoint accepts USDC on Base (10,000 base units = $0.01) and USDT on Tron (10,000 base units = $0.01) per call.https://bridge.eruditepay.com/v1/base/wallet/token-transfers
- —Provider is Erudite Intelligence LLC, a FinCEN MSB-registered entity (BSA ID 31000324258137).https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains and uses x402 v2.0 protocol.https://bridge.eruditepay.com
- —The facilitator for the Base payment option is Coinbase CDP (https://api.cdp.coinbase.com/platform/v2/x402).https://bridge.eruditepay.com/v1/base/wallet/token-transfers
- —Docs endpoint returns 404.https://bridge.eruditepay.com/docs