x402basequality 0.40

Look up counterparties for any wallet or contract address on Base, paid per-call via x402.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint, operated by Erudite Intelligence LLC, returns counterparty data for a given blockchain wallet or contract address. You POST a JSON body containing an `address` field (a wallet or contract address) and receive a JSON response with counterparty information. The endpoint is described as "Crypto data intelligence" in its x402 challenge.

Payment is handled via the x402 protocol (version 2). The endpoint accepts two payment options: USDC on Base (eip155:8453) at 0.01 USDC per call, or USDT on Tron (tron:728126428) at 0.01 USDT per call. The Base payment is facilitated through Coinbase CDP's x402 facilitator. The Tron payment route is provided directly by Erudite Intelligence LLC.

Documentation is sparse — the endpoint's behavior is inferred primarily from the x402 challenge's Bazaar schema extension and the example input/output. The example output is simply `{"success": true, "data": {}}`, so the exact structure of the counterparty data returned is unknown. The provider's landing page focuses on the EruditePay Bridge (a payment facilitator), not on this data intelligence endpoint specifically, so there is limited detail on what "counterparties" means in this context (e.g., addresses that have transacted with the queried address, labeled entities, etc.).

Capabilities

blockchain-address-lookupcounterparty-analysiscrypto-data-intelligencex402-paymentbase-usdctron-usdtpost-json

Use cases

  • Identify which addresses have transacted with a given wallet for compliance or due diligence
  • Feed counterparty data into an agent pipeline for on-chain risk scoring
  • Enrich wallet profiles with interaction graphs in a crypto analytics dashboard

Fit

Best for

  • Agents or apps needing per-call blockchain address intelligence without API key management
  • Compliance workflows that need counterparty identification for a specific address
  • Developers already using x402-compatible payment flows

Not for

  • Bulk historical transaction export across thousands of addresses (per-call pricing adds up)
  • Non-blockchain address lookups (e.g., email, IP, DNS)

Quick start

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

Example

Request

{
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}

Response

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

Endpoint

Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.40/ 1.00

The endpoint is live (402 challenge captured) with a clear Bazaar schema for input, but documentation is essentially absent — no dedicated docs page, no detailed output schema, and the example response is an empty data object. The exact meaning of 'counterparties' and the response structure must be inferred.

Warnings

  • No dedicated documentation found — /docs, /api, /pricing, and /README all return endpoint_not_found errors.
  • The example output contains an empty data object, so the actual response structure for counterparty data is unknown.
  • The endpoint description is only 'Crypto data intelligence' — the specific meaning of 'counterparties' is not documented.

Citations

Provenance

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

Agent access