x402basequality 0.45

Retrieve Tron block transactions via x402 micropayment, settled in USDC (Base) or USDT (Tron).

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://bridge.eruditepay.com/v1/tron/block/transactions

What it does

This endpoint returns transaction data for a given Tron block, address, or transaction hash. It is operated by Erudite Intelligence LLC and gated behind the x402 payment protocol (version 2). Each call costs $0.01 — payable as 10,000 base units of USDC on Base (EIP-155:8453) or 10,000 base units of USDT on Tron (tron:728126428). The endpoint accepts a POST request with a JSON body containing fields such as `hash`, `chain`, and `address` (Tron T-prefix base58 format).

The provider describes the service as "Crypto data intelligence." The response schema indicates a JSON object with `success` (boolean) and `data` (object) fields, though the example output shows an empty `data` object, so the exact shape of returned transaction data is not documented in detail. No OpenAPI spec or dedicated documentation page was found — the docs URL returns a 404.

EruditePay Bridge is the x402 facilitator behind this endpoint, supporting 20 blockchains and registered as a FinCEN MSB (BSA ID 31000324258137). The facilitator operates non-custodially, routing settlements directly. The endpoint is live and returned a proper 402 challenge when probed.

Capabilities

tron-block-transactionscrypto-data-intelligencex402-payment-gatedusdc-base-settlementusdt-tron-settlementblockchain-querytransaction-lookup

Use cases

  • —Querying all transactions in a specific Tron block for analytics or indexing
  • —Looking up transactions associated with a Tron address for wallet tracking
  • —Retrieving transaction details by hash for payment verification or auditing

Fit

Best for

  • —Agents needing on-demand Tron transaction data without API key management
  • —Micropayment-gated blockchain data access for pay-per-query workflows
  • —Automated crypto analytics pipelines that can settle via x402

Not for

  • —High-volume bulk data ingestion where per-call costs would accumulate quickly
  • —Querying non-Tron blockchains (this endpoint is Tron-specific)

Quick start

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

Example

Request

{
  "address": "T9yD14Nj9j7xAB4dbGeiX9h8unkKHxuWwb"
}

Response

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

Endpoint

URLhttps://bridge.eruditepay.com/v1/tron/block/transactions
Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live and returns a well-formed x402 v2 challenge with clear pricing and schema hints. However, documentation is effectively absent (docs URL 404), the output example is an empty object, and the exact semantics of the request fields (hash vs. address vs. chain) and the structure of returned transaction data are not documented.

Warnings

  • —No dedicated documentation found — /docs returns 404
  • —Output example contains empty data object; actual response structure is unknown
  • —Request body schema is ambiguous: unclear whether hash, chain, and address are all required or optional
  • —The example body includes 'chain: base' for a Tron-specific endpoint, which is confusing

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/eDtTdy