x402basequality 0.45

Look up labels/tags for wallet or contract addresses on Base via x402 micropayment.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint from Erudite Intelligence LLC provides crypto address labeling ("Crypto data intelligence") on the Base network. You POST a wallet or contract address and receive label/tag data associated with that address. The endpoint is gated behind the x402 payment protocol (v2), returning a 402 challenge until payment is provided.

Payment is accepted in two ways: USDC on Base (eip155:8453) at 0.01 USDC per call, or USDT on Tron (tron:728126428) at 0.01 USDT per call. The x402 facilitator is Coinbase CDP for the Base option. The provider is Erudite Intelligence LLC, a FinCEN MSB-registered entity. The Bridge facilitator at bridge.eruditepay.com supports 20 blockchains and handles verify/settle steps.

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 schema for what fields appear inside `data`, no enumeration of supported label types, and the docs link (docs.eruditepay.com) was not reachable in the crawl. The input schema requires a JSON body with an `address` string field described as "Wallet or contract address." The endpoint path includes `/base/` suggesting it is scoped to the Base L2 chain, though this is inferred from the URL structure rather than explicit documentation.

Capabilities

address-labelingblockchain-intelligencebase-chainx402-paymentusdc-paymenttron-usdt-paymentwallet-lookupcontract-lookup

Use cases

  • Identify known entities (exchanges, protocols, scammers) behind a Base address before transacting
  • Enrich on-chain transaction data with human-readable labels for compliance dashboards
  • Agent-driven wallet screening: automatically label counterparty addresses during trade execution
  • Build address books that auto-tag new addresses encountered in DeFi interactions
  • Power AML/KYC workflows by resolving addresses to known entity labels

Fit

Best for

  • AI agents that need per-call address intelligence without API key management
  • Compliance and risk teams screening Base wallet addresses
  • On-chain analytics pipelines that need entity resolution for addresses

Not for

  • Bulk labeling of millions of addresses (per-call micropayment model would be expensive at scale)
  • Chains other than Base (this specific endpoint is scoped to /base/)
  • Detailed transaction history or balance queries — this is label/tag data only

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/address/label \
  -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.45/ 1.00

The endpoint is live (402 challenge captured) with a clear input schema and pricing, but the output schema is a stub with no detail on what label data is actually returned. No external documentation was reachable. The description 'Crypto data intelligence' is vague.

Warnings

  • Output schema is a generic stub — no documentation on what fields appear inside 'data'
  • docs.eruditepay.com was not crawled/reachable; /docs on bridge returns 404
  • Endpoint description is vague ('Crypto data intelligence') — actual label taxonomy unknown
  • Scope appears limited to Base chain based on URL path; no confirmation of multi-chain label coverage at this endpoint

Citations

Provenance

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

Agent access