Query TRON token holder changes via x402-paid POST endpoint
What it does
This endpoint, hosted by Erudite Intelligence LLC on their EruditePay x402 Bridge infrastructure, returns data about token holder changes on the TRON blockchain. Callers send a POST request with a JSON body containing an `address` (wallet or contract address) and a `token` (token address or symbol), and receive a JSON response with holder-change data. The endpoint is gated by the x402 protocol (version 2) and returns HTTP 402 with payment requirements to unauthenticated callers.
Payment is accepted in two ways: USDC on Base (eip155:8453) at 10,000 base units ($0.01) per call, or USDT on TRON (tron:728126428) at 10,000 base units ($0.01) per call. The facilitator for the Base/USDC option is Coinbase CDP. The endpoint responds with `application/json` containing a `success` boolean and a `data` object, though the exact shape of the `data` payload is not documented beyond the example stub `{}`.
The provider describes the service as "Crypto data intelligence." Documentation at docs.eruditepay.com was referenced on the landing page but the /docs path on the bridge itself returns a 404, and no OpenAPI spec was found. The input/output schema is available via the x402 challenge's bazaar extension, but the output structure is underspecified. The endpoint is live and responding with a valid x402 v2 challenge.
Capabilities
Use cases
- —Track changes in token holder counts for a specific TRON token
- —Monitor wallet-level token holder activity for compliance or analytics
- —Feed TRON holder-change data into trading or research pipelines
Fit
Best for
- —Agents needing programmatic access to TRON token holder change data
- —Crypto analytics platforms tracking holder dynamics
- —Automated monitoring of TRON token distribution shifts
Not for
- —Querying non-TRON blockchains (this endpoint is TRON-specific)
- —Getting real-time price or trading data
- —Free or unauthenticated bulk data access
Quick start
curl -X POST https://bridge.eruditepay.com/v1/tron/token/holder-changes \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7", "token": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"}'Example
Request
{
"token": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t",
"address": "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live with a valid x402 v2 challenge and has input schema via the bazaar extension, but the output data structure is essentially a stub (empty object). No OpenAPI spec, no dedicated docs, and the docs.eruditepay.com link leads nowhere on the bridge. Pricing is clear ($0.01/call) but the actual data returned is unspecified.
Warnings
- —Output schema is underspecified — the example response data is an empty object {}
- —No OpenAPI or dedicated API documentation found for this endpoint
- —docs.eruditepay.com referenced on landing page but /docs returns 404 on the bridge
- —Exact fields and semantics of 'holder changes' are not documented
Citations
- —Endpoint returns x402 v2 challenge with USDC on Base and USDT on TRON payment options at 10,000 base units eachhttps://bridge.eruditepay.com/v1/tron/token/holder-changes
- —Provider is Erudite Intelligence LLC, FinCEN MSB registeredhttps://bridge.eruditepay.com
- —Input schema requires address and token fields as stringshttps://bridge.eruditepay.com/v1/tron/token/holder-changes
- —USDC on Base uses 6 decimals, so 10000 base units = $0.01https://bridge.eruditepay.com