x402basequality 0.45

Token holder distribution data for Base chain addresses, paid per-call via x402 in USDC or USDT.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint returns token holder distribution data for a given wallet or contract address on the Base blockchain. It accepts a POST request with a JSON body containing an `address` (wallet or contract address) and a `token` (token address or symbol), and returns a JSON object with distribution data.

The endpoint is operated by Erudite Intelligence LLC and is gated via the x402 payment protocol (v2). Each call costs 10,000 base units — equivalent to $0.01 USD — payable in USDC on Base (eip155:8453) or USDT on Tron (tron:728126428). Payment is facilitated through the EruditePay Bridge, which supports 20 blockchains and settles via the Coinbase CDP facilitator or directly. The provider is a FinCEN-registered MSB (BSA ID 31000324258137) and operates non-custodially.

Documentation beyond the x402 challenge and the provider's landing page is sparse. The endpoint description in the challenge is simply "Crypto data intelligence," and the output example is a generic `{"success": true, "data": {}}` stub. No detailed field-level documentation for the response was found. The docs.eruditepay.com link referenced on the landing page was not crawled, and /docs on the bridge itself returns a 404. Consumers should test with a real token address to understand the shape of the returned distribution data.

Capabilities

token-holder-distributionbase-chain-analyticsx402-paymentusdc-paymentusdt-tron-paymentcrypto-data-intelligencepost-json-api

Use cases

  • Analyze the distribution of token holders for a specific ERC-20 token on Base
  • Assess token concentration risk before investing or listing a token
  • Build dashboards showing whale vs. retail holder breakdowns
  • Automate due-diligence checks on token decentralization

Fit

Best for

  • Agents or bots that need on-demand token holder analytics on Base
  • DeFi researchers analyzing token distribution patterns
  • Compliance teams checking token concentration metrics

Not for

  • Querying holder distributions on chains other than Base (only Base addresses accepted)
  • Free or high-volume bulk data pulls (each call costs $0.01 via x402)
  • Detailed transaction-level or historical holder data (response schema unclear)

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/token/holder-distribution \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"address": "0xYourWalletAddress", "token": "0xTokenContractAddress"}'

Example

Request

{
  "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "address": "0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1"
}

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 schema for the request body and pricing. However, the response schema is a stub with an empty data object, no detailed docs were found, and the endpoint description is generic. Significant inference is required about what 'holder distribution' data actually contains.

Warnings

  • Response data shape is unknown — the example output is just {"success": true, "data": {}}
  • No detailed API documentation found; /docs returns 404 on the bridge domain
  • The endpoint description is only 'Crypto data intelligence' with no specifics on holder distribution fields
  • docs.eruditepay.com was referenced but not crawled; may contain additional documentation

Citations

Provenance

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

Agent access