x402basequality 0.45

Retrieve hot trading pairs from Tron token launches via x402-paid API

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint, hosted by Erudite Intelligence LLC on the EruditePay Bridge, returns hot trading pairs from Tron-based token launches. It accepts a POST request with a Tron address (T-prefix base58 format) and returns structured JSON data about active or trending pairs associated with that address. The endpoint is gated behind the x402 payment protocol (version 2) and accepts payment in USDC on Base (eip155:8453) or USDT on Tron (tron:728126428), both priced at $0.01 per call (10,000 base units with 6 decimals).

The x402 challenge is live and returns a valid 402 response with two accepted payment options. The facilitator for the Base/USDC option is Coinbase CDP. The Tron/USDT option does not specify a third-party facilitator. The provider is registered as a FinCEN MSB (BSA ID 31000324258137) and operates a non-custodial settlement model.

Documentation is sparse — the /docs path returns a 404, and the only schema information available comes from the x402 challenge's bazaar extension. The example output is a generic `{"success": true, "data": {}}` stub, so the actual shape of the returned hot-pairs data is unknown. Users should expect JSON but will need to experiment to understand the full response structure.

Capabilities

tron-hot-pairstoken-launch-datax402-paymentusdc-baseusdt-troncrypto-data-intelligencepost-json-api

Use cases

  • Discover trending or newly launched token pairs on the Tron network
  • Monitor hot trading activity around a specific Tron address
  • Feed Tron launch data into a trading bot or analytics dashboard

Fit

Best for

  • Tron ecosystem traders looking for early token launch signals
  • Crypto analytics platforms needing programmatic access to Tron pair data
  • Automated agents that need pay-per-call access to Tron market intelligence

Not for

  • Users needing data on non-Tron blockchains (this endpoint is Tron-specific)
  • Anyone requiring detailed historical data — the endpoint appears to return current/hot pairs only
  • Users who cannot make x402 micropayments in USDC or USDT

Quick start

curl -X POST https://bridge.eruditepay.com/v1/tron/launch/hot-pairs \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"address": "T9yD14Nj9j7xAB4dbGeiX9h8unkKHxuWwb"}'

Example

Request

{
  "address": "T9yD14Nj9j7xAB4dbGeiX9h8unkKHxuWwb"
}

Response

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

Endpoint

Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.45/ 1.00

The x402 challenge is live and well-formed with two payment options and a bazaar schema extension, but documentation is effectively absent (all doc paths return 404). The example response is a stub with an empty data object, so the actual output structure is unknown. Pricing is clear at $0.01/call.

Warnings

  • No dedicated documentation available — /docs returns 404
  • Example output in bazaar extension is a stub ({"data": {}}) with no real field definitions
  • Actual response schema for hot-pairs data is undocumented and must be discovered empirically
  • The Tron network identifier 'tron:728126428' is non-standard (mainnet is typically 'tron:mainnet'); verify compatibility with your x402 client

Citations

Provenance

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

Agent access