Look up labels/tags for Tron wallet and contract addresses via x402 micropayment.
What it does
This x402-enabled endpoint from Erudite Intelligence LLC provides crypto data intelligence for the Tron blockchain. By POSTing a Tron wallet or contract address, the endpoint returns label/tag information associated with that address (e.g., exchange names, known entities, contract types). Payment is required per-call via the x402 protocol.
The endpoint accepts payment in two ways: USDC on Base (eip155:8453) or USDT on Tron (tron:728126428), both at 0.01 USD per request (10,000 base units with 6 decimals). The request body is a simple JSON object containing an "address" field. The response returns a JSON object with a "success" boolean and a "data" object containing the label information.
The endpoint is live and returns a valid x402 v2 challenge. It is operated by Erudite Intelligence LLC, which also runs the EruditePay x402 Bridge facilitator service. Documentation beyond the x402 challenge metadata is sparse — the docs.eruditepay.com link referenced on the landing page was not crawled, and /docs on the bridge domain returns a 404. The exact structure of the returned label data is not documented; the example output only shows an empty data object.
Capabilities
Use cases
- —Identify whether a Tron address belongs to a known exchange, DeFi protocol, or scam entity
- —Enrich transaction monitoring pipelines with address labels for compliance workflows
- —Build address-book features in Tron wallets or block explorers
- —Automate KYT (Know Your Transaction) checks by labeling counterparty addresses
- —Power agent-driven crypto investigation tools that need on-chain entity resolution
Fit
Best for
- —Agents or bots that need programmatic Tron address attribution
- —Compliance and AML tools requiring entity labels for Tron addresses
- —Crypto analytics dashboards enriching Tron transaction data
Not for
- —Labeling addresses on non-Tron blockchains (endpoint is Tron-specific)
- —Free or high-volume bulk lookups where per-call micropayments are impractical
- —Use cases requiring detailed KYC-level identity information beyond labels
Quick start
curl -X POST https://bridge.eruditepay.com/v1/tron/address/label \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "TTikV9JD3xTfk5TDv8HMEvpWmNQS8Fm6Pw"}'Example
Request
{
"address": "TTikV9JD3xTfk5TDv8HMEvpWmNQS8Fm6Pw"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live and returns a well-formed x402 v2 challenge with clear pricing and a basic schema. However, documentation is very sparse: the output data structure is undocumented (example shows empty object), no OpenAPI spec exists, and the referenced docs site was not reachable. The actual label taxonomy and coverage are unknown.
Warnings
- —Output data structure is undocumented — the example only shows an empty data object, so the actual label fields are unknown.
- —No OpenAPI specification or detailed API documentation was found; docs.eruditepay.com was not crawled.
- —The example address in the schema uses an Ethereum-style 0x address, not a Tron-style T-address, which is inconsistent with a Tron-specific endpoint.
Citations
- —Endpoint returns x402 v2 challenge with USDC on Base and USDT on Tron payment options at 10000 base units eachhttps://bridge.eruditepay.com/v1/tron/address/label
- —Provider is Erudite Intelligence LLC, FinCEN MSB registered (BSA ID 31000324258137)https://bridge.eruditepay.com
- —USDC and USDT use 6 decimals, so 10000 base units = $0.01https://bridge.eruditepay.com
- —Request body accepts an 'address' field described as 'Wallet or contract address'https://bridge.eruditepay.com/v1/tron/address/label