x402basequality 0.45

Fetch Tron block data by number via x402 micropayment (USDC on Base or USDT on Tron)

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint, operated by Erudite Intelligence LLC, returns Tron blockchain block data when given a block number. It is an x402-gated POST endpoint at https://bridge.eruditepay.com/v1/tron/block/by-number. Callers must include a valid x402 payment header to access the data. The endpoint accepts payment in two ways: USDC on Base (EIP-155:8453) or USDT on Tron (tron:728126428), both priced at 10,000 base units per call — which equals $0.01 USD given 6-decimal stablecoins.

The request body is JSON and, based on the Bazaar schema embedded in the x402 challenge, expects properties such as a blockchain identifier and a Tron address. However, the endpoint path says "block/by-number," suggesting the body should contain a block number — the example body in the schema shows a `chain` and `address` field, which may be a generic template rather than the actual input for this specific route. The response format is JSON with a `success` boolean and a `data` object.

The provider, EruditePay, operates an x402 payment facilitator bridge supporting 20 blockchains. The facilitator is registered as a FinCEN MSB (BSA ID 31000324258137) and is non-custodial. The endpoint returned a proper 402 challenge on probe, confirming it is live. Documentation at docs.eruditepay.com is referenced on the landing page but the /docs path on the bridge itself returns a 404, so detailed API documentation for this specific data endpoint is not available from the crawl.

Capabilities

tron-block-datax402-paymentusdc-baseusdt-tronblockchain-querycrypto-data-intelligence

Use cases

  • Retrieve Tron block details by block number for chain analytics
  • Build block explorers or indexers that need on-demand Tron block data
  • Integrate Tron block queries into agent workflows with micropayment access
  • Verify on-chain Tron activity by fetching specific blocks

Fit

Best for

  • Developers needing pay-per-call Tron block data without running a full node
  • AI agents that need programmatic access to Tron blockchain blocks
  • Applications requiring low-cost ($0.01/call) Tron block lookups

Not for

  • High-volume bulk block ingestion (per-call cost adds up quickly)
  • Querying non-Tron blockchains (this endpoint is Tron-specific)
  • Users who need free or subscription-based blockchain data access

Quick start

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

Example

Request

{
  "block_number": 12345678
}

Response

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

Endpoint

Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (402 challenge confirmed) with clear pricing ($0.01 per call in USDC or USDT). However, the Bazaar schema example body (chain + address) does not match the endpoint path (block/by-number), suggesting a generic or mismatched template. No dedicated API docs were reachable from the crawl, and the output example is an empty data object, providing no insight into actual response structure.

Warnings

  • The Bazaar schema example body shows 'chain' and 'address' fields, which may not match the actual expected input for a block-by-number endpoint — the real request body format is uncertain.
  • docs.eruditepay.com is referenced but not crawled; the /docs path on the bridge returns 404.
  • The output example contains an empty 'data' object, so the actual response structure is unknown.

Citations

Provenance

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

Agent access