Retrieve wallet transaction data on Base via x402 micropayment (USDC/USDT).
What it does
This x402-enabled endpoint from Erudite Intelligence LLC provides crypto data intelligence by returning transaction information for a given wallet address or transaction hash on the Base network. Callers POST a JSON body containing an `address` (wallet or contract address) and/or a `hash` (transaction hash), and receive structured transaction data in return.
Payment is handled via the x402 protocol (HTTP 402 challenge). The endpoint accepts two payment rails: USDC on Base (EIP-155:8453) at 0.01 USDC per call, or USDT on Tron at 0.01 USDT per call. The facilitator is Coinbase CDP's x402 service for the Base rail. The provider, Erudite Intelligence LLC, also operates the EruditePay Bridge — an x402 payment facilitator supporting 20 blockchains — but this specific endpoint is a data API, not the facilitator itself.
Documentation for this endpoint is sparse. The crawled landing page at bridge.eruditepay.com describes the EruditePay Bridge facilitator service, not this wallet transactions data endpoint specifically. The Bazaar schema embedded in the 402 challenge provides the input/output structure, but the output example is a generic `{"success": true, "data": {}}` stub with no detail on what fields are returned. No OpenAPI spec or dedicated docs page was found.
Capabilities
Use cases
- —Look up transaction history for a specific wallet address on Base
- —Retrieve details of a specific transaction by hash
- —Feed wallet transaction data into an AI agent's crypto analysis pipeline
- —Monitor wallet activity programmatically with per-call micropayments
- —Enrich blockchain addresses with transaction metadata
Fit
Best for
- —Agents needing on-demand wallet transaction data without API key subscriptions
- —Micropayment-based access to Base chain transaction intelligence
- —Developers integrating x402-native crypto data lookups
Not for
- —Bulk historical blockchain data exports (per-call pricing adds up)
- —Multi-chain transaction queries beyond Base (endpoint is Base-specific)
- —Users who need detailed documentation before integrating (docs are minimal)
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/wallet/transactions \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
"address": "0x0000000000000000000000000000000000000000"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear Bazaar schema for input, but the output example is a stub with no field details. No dedicated documentation exists for this data endpoint; the landing page describes the facilitator service, not the transactions API. Pricing is clear ($0.01 per call) but response structure is unknown.
Warnings
- —Output schema is a generic stub — actual response fields are undocumented
- —No OpenAPI spec or dedicated endpoint documentation found
- —The /docs path returns 404; docs.eruditepay.com was not crawled and may or may not exist
- —Response data structure must be discovered empirically
Citations
- —Endpoint accepts USDC on Base (amount 10000 = $0.01) and USDT on Tron (amount 10000 = $0.01)https://bridge.eruditepay.com/v1/base/wallet/transactions
- —Provider is Erudite Intelligence LLC, facilitator is Coinbase CDP x402https://bridge.eruditepay.com/v1/base/wallet/transactions
- —EruditePay Bridge is an x402 facilitator supporting 20 blockchains, FinCEN MSB registeredhttps://bridge.eruditepay.com
- —Input body accepts address (wallet or contract address) and hash (transaction hash)https://bridge.eruditepay.com/v1/base/wallet/transactions