x402basequality 0.45

Monitor smart contract calls on Base and other chains via a pay-per-request x402 endpoint.

Price
per_call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint from Erudite Intelligence LLC lets you monitor contract calls for a given smart contract address on a specified blockchain. You POST a JSON body containing a contract address and chain identifier, and receive structured data about contract call activity. The endpoint is described as "Crypto data intelligence" and accepts payment in USDC on Base (via Coinbase CDP facilitator) or USDT on Tron, at $0.01 per request.

The endpoint follows the x402 v2 protocol: unauthenticated requests receive an HTTP 402 challenge with payment requirements, and once payment is attached via the X-PAYMENT header, the endpoint returns results. The request schema requires an `address` field (the contract address to monitor) and a `chain` field (the blockchain network). The response returns a JSON object with a `success` boolean and a `data` object, though the exact structure of the data payload is not documented beyond the example stub.

The provider, Erudite Intelligence LLC, operates the EruditePay x402 Bridge facilitator supporting 20 blockchains. They are registered as a FinCEN MSB (BSA ID 31000324258137) and operate non-custodially. Documentation at docs.eruditepay.com is referenced but the /docs path on the bridge itself returns a 404, so detailed field-level documentation for this specific monitoring endpoint is unavailable.

Capabilities

contract-call-monitoringblockchain-analyticsmulti-chain-supportx402-paymentpay-per-requestbase-chaintron-chainusdc-paymentusdt-payment

Use cases

  • Monitoring smart contract interactions for a DeFi protocol on Base
  • Tracking contract call activity for security or compliance auditing
  • Building dashboards that display real-time contract usage across chains
  • Automated alerting when specific contracts receive calls
  • Agent-driven on-chain intelligence gathering for trading strategies

Fit

Best for

  • Developers needing per-call contract monitoring without subscription commitments
  • AI agents that need on-demand blockchain intelligence with micropayments
  • Teams monitoring smart contract activity across multiple chains

Not for

  • Historical bulk data export or full blockchain indexing
  • Free-tier or ad-supported analytics needs
  • Monitoring non-EVM chains not listed in the supported set

Quick start

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

Example

Request

{
  "chain": "base",
  "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}

Response

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

Endpoint

Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (402 challenge captured) with a clear input schema and pricing, but the response data structure is only shown as an empty stub. No detailed documentation is available (docs.eruditepay.com referenced but /docs returns 404), and the actual content of the `data` field is unknown.

Warnings

  • Response data structure is undocumented — the example only shows an empty object
  • docs.eruditepay.com is referenced but the /docs path on the bridge returns endpoint_not_found
  • The exact fields returned in the 'data' object for contract call monitoring are not specified anywhere in available materials
  • No OpenAPI spec available for this endpoint

Citations

Provenance

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

Agent access