x402basequality 0.40

Query smart contract data on Base via x402-paid crypto intelligence endpoint.

Price
per_call
Protocol
x402
Verified
no

What it does

This x402-protected endpoint from Erudite Intelligence LLC provides crypto data intelligence by accepting a smart contract address and returning data about it. The endpoint accepts POST requests with a JSON body containing an `address` field (a contract address) and returns a JSON response with a `success` boolean and a `data` object.

Payment is handled via the x402 protocol (version 2) with two accepted payment options: USDC on Base (eip155:8453) or USDT on Tron (tron:728126428), both priced at 10,000 base units per call — which equals $0.01 (one cent) given 6-decimal stablecoins. The facilitator is Coinbase CDP's x402 endpoint for the Base option. The provider, Erudite Intelligence LLC, also operates the EruditePay x402 Bridge, a multi-chain payment facilitator.

Documentation is sparse: the endpoint description is simply "Crypto data intelligence" and the example output is a generic `{"success": true, "data": {}}` stub. There is no detailed documentation available at the provider's /docs path, and the exact fields returned in the `data` object are unspecified. The schema confirms the input requires a contract address string, but the scope of intelligence returned (ABI, token metadata, transaction history, etc.) is not documented.

Capabilities

smart-contract-lookupcrypto-data-intelligencex402-paymentbase-chaintron-paymentcontract-address-query

Use cases

  • Querying metadata or intelligence about a smart contract by address
  • Automated agent workflows that need on-chain contract information before interacting
  • Building dashboards that aggregate contract-level data across protocols

Fit

Best for

  • Agents needing per-call contract intelligence without API key management
  • Workflows that already support x402 payment protocol
  • Developers who want to pay per query with USDC on Base or USDT on Tron

Not for

  • Bulk or high-volume contract scanning (at $0.01/call costs add up)
  • Use cases requiring well-documented, strongly-typed response schemas
  • Querying non-EVM contract addresses (input schema suggests EVM-style 0x addresses)

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/contract/call \
  -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.40/ 1.00

The endpoint is live (402 challenge captured) with a valid x402v2 payment structure and basic input/output schema. However, documentation is effectively absent — the /docs path returns 404, the output example is a stub with an empty data object, and the description is a vague three-word phrase. The actual intelligence returned is unknown.

Warnings

  • No documentation available — /docs returns endpoint_not_found
  • Output schema is a stub: example data object is empty with no field descriptions
  • Exact nature of 'crypto data intelligence' returned is unspecified
  • Input schema suggests EVM-style addresses but endpoint path says 'base' — unclear if other chains' contracts are supported

Citations

Provenance

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

Agent access