x402basequality 0.45

Sanctions-check a wallet or contract address via x402 micropayment on Base or Tron.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint, operated by Erudite Intelligence LLC, accepts a blockchain wallet or contract address and returns a sanctions-check result. It is part of the EruditePay Bridge infrastructure, which describes itself as a "Crypto data intelligence" provider. The endpoint is live and responds with an x402 v2 payment challenge, accepting payment in USDC on Base (EIP-155:8453) or USDT on Tron before returning results.

The cost per call is $0.01 (10,000 base units of a 6-decimal stablecoin). Payment can be made via USDC on Base to address 0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1, or via USDT on Tron to TTikV9JD3xTfk5TDv8HMEvpWmNQS8Fm6Pw. The facilitator for Base payments is Coinbase CDP's x402 endpoint. The request body is a JSON object with a single field, `address`, representing the wallet or contract address to check. The response is a JSON object with a `success` boolean and a `data` object (contents of `data` are not documented beyond the empty example).

Documentation is sparse — the provider's /docs path returns a 404, and no OpenAPI spec is available. The exact sanctions lists checked, the structure of a positive match in the response `data` field, and rate limits are all undocumented. The provider is a FinCEN-registered MSB (BSA ID 31000324258137) and operates non-custodially.

Capabilities

sanctions-screeningwallet-address-lookupx402-paymentusdc-baseusdt-troncompliance-checkcrypto-intelligence

Use cases

  • Screen a wallet address against sanctions lists before processing a crypto transaction
  • Automate compliance checks in a DeFi or CeFi onboarding flow
  • Agent-driven KYC/AML pipeline that needs per-call sanctions lookups without monthly subscriptions
  • Integrate sanctions screening into an x402-enabled payment gateway

Fit

Best for

  • Developers needing pay-per-call sanctions screening without API key management
  • Agents or bots that must verify wallet compliance before interacting
  • Low-volume or bursty compliance checks where a subscription model is wasteful

Not for

  • High-volume batch screening (no documented bulk endpoint; $0.01/call adds up)
  • Users who need detailed match metadata — response data structure is undocumented
  • Screening non-crypto identifiers (names, IPs, etc.) — input is a blockchain address only

Quick start

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

Example

Request

{
  "address": "0x0000000000000000000000000000000000000000"
}

Response

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

Endpoint

Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live and returns a well-formed x402 v2 challenge with clear pricing and a basic schema. However, documentation is effectively absent: no OpenAPI spec, no description of what the `data` field contains on a positive match, no rate limits, and no information about which sanctions lists are checked. The response example is an empty object, making it hard to evaluate usefulness.

Warnings

  • No documentation available — /docs returns 404 and no OpenAPI spec exists
  • Response data structure is undocumented; the example shows an empty object
  • Sanctions/compliance is a regulated category — verify the provider's methodology and list coverage independently
  • Unknown which sanctions lists (OFAC SDN, EU, UN, etc.) are checked
  • No rate limit or usage policy documented

Citations

Provenance

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

Agent access