x402basequality 0.45

Retrieve smart contract events on Base by contract address, paid per call via x402 in USDC or USDT.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint, hosted by Erudite Intelligence LLC, returns contract event data for a given smart contract address on the Base blockchain (eip155:8453). It is described as "Crypto data intelligence" in the x402 challenge. You POST a JSON body containing an `address` field (the contract address) and receive a JSON response with event data.

Payment is handled via the x402 protocol (version 2). Each call costs 10,000 base units, which equates to $0.01 USD when paying in USDC on Base (6 decimals) or USDT on Tron (6 decimals). The facilitator is Coinbase CDP's x402 endpoint for the Base payment path. The Tron payment path uses USDT at the same price point. The endpoint is live and returns a proper 402 challenge when called without payment.

The provider, EruditePay, operates an x402 payment bridge supporting 20 blockchains and is registered as a FinCEN MSB (BSA ID 31000324258137). Documentation at docs.eruditepay.com is referenced on the landing page but the /docs path on the bridge itself returns a 404. The response schema is loosely defined — the example output is `{"success": true, "data": {}}` — so the exact structure and depth of the returned event data is not documented in the probe material.

Capabilities

contract-event-lookupbase-chain-datax402-paymentusdc-paymentusdt-paymentsmart-contract-analysiscrypto-data-intelligence

Use cases

  • Querying emitted events for a specific smart contract on Base to monitor activity
  • Building dashboards that track contract interactions and state changes
  • Automated agents that need on-chain event data for decision-making
  • Auditing or analyzing historical contract behavior on Base

Fit

Best for

  • Agents or services needing per-call contract event data without managing an RPC node
  • x402-native workflows that can pay per request in USDC or USDT
  • Lightweight integrations that only need event data for specific contracts on Base

Not for

  • High-volume event streaming where per-call pricing becomes expensive compared to running your own node
  • Multi-chain event queries beyond Base (this endpoint is Base-specific)
  • Use cases requiring detailed documentation or guaranteed response schemas

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/contract/events \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'

Example

Request

{
  "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}

Response

{
  "data": {},
  "success": true
}

Endpoint

Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live and returns a valid x402 challenge with schema and pricing. However, the response format is only shown as a stub ({"data": {}}), there is no detailed documentation available (docs.eruditepay.com is referenced but /docs returns 404), and the actual event data structure is unknown. Pricing and payment paths are clear.

Warnings

  • Response schema is effectively undefined — the example output is {"success": true, "data": {}} with no further detail.
  • docs.eruditepay.com is referenced on the landing page but the /docs path on the bridge returns 404; external docs site was not crawled.
  • Exact fields, pagination, and filtering capabilities for contract events are undocumented in available material.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:01:55Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access