Query token holder changes for any wallet/contract on Base via x402 micropayment.
What it does
This x402-gated endpoint from Erudite Intelligence LLC returns token holder change data for a given wallet or contract address on the Base blockchain. You POST a JSON body containing an `address` (wallet or contract) and a `token` (token address or symbol), and receive structured JSON describing holder changes for that token.
Payment is handled via the x402 protocol. The endpoint accepts two payment options: USDC on Base (EIP-155:8453) or USDT on Tron, both at 10,000 base units per call — which equals $0.01 USD per request (6-decimal stablecoins). The x402 facilitator is Coinbase CDP for the Base payment rail. The provider, Erudite Intelligence LLC, also operates the EruditePay Bridge facilitator that supports 20 blockchains and is registered as a FinCEN MSB (BSA ID 31000324258137).
Documentation is sparse: the endpoint description in the x402 challenge is simply "Crypto data intelligence," and the output example is a generic `{"success": true, "data": {}}` stub. There is no OpenAPI spec, no dedicated docs page, and no detailed field-level documentation for the response payload. The endpoint is live and returns a valid x402 v2 challenge on POST.
Capabilities
Use cases
- —Track changes in token holder counts for a specific ERC-20 token on Base
- —Monitor wallet-level token holder movements for portfolio analytics
- —Feed holder-change signals into trading or alerting bots
- —Enrich on-chain data pipelines with holder dynamics
Fit
Best for
- —Agents needing per-call token holder change data on Base without subscriptions
- —Automated crypto analytics pipelines that can pay per request via x402
- —Developers building wallet monitoring dashboards
Not for
- —Historical multi-chain holder analytics across many blockchains (only Base is indicated)
- —Free or high-volume bulk data extraction (each call costs $0.01)
- —Users who need detailed documentation or guaranteed response schemas before integrating
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/token/holder-changes \
-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
Quality
The endpoint is live with a valid x402 v2 challenge, schema for input is provided, and pricing is clear ($0.01/call). However, there is no OpenAPI spec, no real documentation, and the output example is an empty stub — making it impossible to know the actual response structure without paying for a call.
Warnings
- —No dedicated documentation page exists (docs, api, pricing, README all return 404-equivalent errors)
- —Output schema is a generic stub: {"success": true, "data": {}} — actual response fields are unknown
- —Endpoint description is vague: 'Crypto data intelligence' — unclear exactly what holder-change data is returned
- —Only Base chain is indicated for this specific endpoint despite the provider supporting 20 chains
Citations
- —The endpoint accepts USDC on Base (amount 10000, 6 decimals = $0.01) and USDT on Tron at the same pricehttps://bridge.eruditepay.com/v1/base/token/holder-changes
- —The x402 facilitator for the Base payment rail is Coinbase CDPhttps://bridge.eruditepay.com/v1/base/token/holder-changes
- —Provider is Erudite Intelligence LLC, a FinCEN MSB registered entity (BSA ID 31000324258137)https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains for x402 facilitationhttps://bridge.eruditepay.com
- —Input schema requires address (wallet or contract) and token (token address or symbol) fieldshttps://bridge.eruditepay.com/v1/base/token/holder-changes