x402basequality 0.50

Fetch the ABI of any smart contract on Base by address, paid per-call via x402.

Price
per_call
Protocol
x402
Verified
no

What it does

This x402-gated endpoint, operated by Erudite Intelligence LLC, accepts a contract address and returns the contract's ABI (Application Binary Interface) for contracts deployed on Base (EIP-155 chain 8453). The caller POSTs a JSON body containing an `address` field and receives a JSON response with the ABI data. Payment is required per call via the x402 protocol.

The endpoint accepts two payment options: USDC on Base (0.01 USDC per call) or USDT on Tron (0.01 USDT per call). The x402 challenge is facilitated through Coinbase CDP's x402 facilitator for the Base payment path. The provider describes the service as "Crypto data intelligence," and the endpoint is part of the EruditePay Bridge infrastructure, which supports 20 blockchains and is operated by a FinCEN MSB-registered entity (BSA ID 31000324258137).

Documentation is sparse — the `/docs` path returns a 404, and the Bazaar schema embedded in the x402 challenge is the primary source of input/output structure. The example output is a generic `{"success": true, "data": {}}` stub, so the exact shape of the returned ABI data is not documented. Callers should expect a standard Ethereum ABI JSON array inside the `data` field, but this is inferred rather than confirmed.

Capabilities

contract-abi-lookupbase-chainx402-paymentusdc-paymentusdt-tron-paymentsmart-contract-metadataevm-abi

Use cases

  • Retrieve the ABI of a verified smart contract on Base to enable programmatic interaction
  • Build tooling that auto-discovers contract methods and events from on-chain addresses
  • Power AI agents that need to understand smart contract interfaces before executing transactions
  • Integrate contract ABI resolution into wallet or dApp frontends

Fit

Best for

  • Developers needing on-demand ABI lookups for Base contracts
  • AI agents that interact with arbitrary smart contracts
  • dApp builders who want pay-per-call ABI resolution without API keys

Not for

  • Bulk ABI scraping across thousands of contracts (per-call pricing adds up)
  • Chains other than Base (this endpoint is Base-specific)
  • Retrieving source code or full contract verification details

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/contract/abi \
  -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 to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.50/ 1.00

The endpoint is live (402 challenge captured) with a clear input schema and two payment options, but documentation is missing (/docs returns 404), the example output is a stub with an empty data object, and the exact ABI response format is not documented. Pricing and payment paths are well-defined.

Warnings

  • No dedicated documentation available — /docs returns 404
  • Example output in the Bazaar schema is a stub ({"success": true, "data": {}}) and does not show actual ABI structure
  • Exact ABI response format is inferred, not confirmed
  • Only Base chain contracts are supported by this specific endpoint

Citations

Provenance

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

Agent access