Back to Browse
Tollex Chain Get Block
x402
Tollex Chain Get Block is a paid API for AI agents from api.tollex.org, paid per call via x402, $0.0079/call, status unknown (last checked 2026-10-11).
Fetches blockchain block data for a specified block number or tag (latest, safe, finalized) from an EVM-compatible chain, paid via x402 micropayment in USDC.
Price / call$0.0079
Success—
StatusUnknown
How this service works
Tollex lets software agents buy APIs and tools under rules you set: it finds a capability that fits, checks your policy before anything is signed, pays with x402 in USDC on Base or USDG on Robinhood Chain, reconciles uncertain payments and returns a signed receipt.
Output
Returns structured EVM block data including block number, hash, parent hash, timestamp, miner, gas used, gas limit, and list of transactions or transaction hashes for the requested block. Also returns a signed Tollex receipt confirming the x402 micropayment was processed.
Example use cases
Monitor latest block height
“Keep checking the latest block for me and let me know when it advances past block 12000000.”
Verify transaction inclusion block
“Pull the block data for block number 11998745 so I can check whether my transaction was included and see the block timestamp.”
Confirm chain finality status
“Fetch the finalized block from the chain — I want to make sure the state I'm reading has passed finality before I act on it.”
Technical details
Endpoint
POSThttps://api.tollex.org/tools/chain_get_block?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need on-chain block data from an EVM-compatible network (Base or Robinhood Chain) and want automatic policy-checked, micropayment-metered access without managing your own RPC node or API keys. Ideal for AI agents operating under spend-policy governance that need ad-hoc blockchain reads billed per call in USDC.
Side effects
- Invalid block parameter format (not matching pattern ^(latest|safe|finalized|[0-9]{1,15})$) returns a validation error
- Block number does not exist yet (future block) returns not-found error
- Payment failure or insufficient USDC balance causes request rejection before execution
- RPC node unavailability causes upstream timeout or 503 error
- Network congestion may delay response for very recent blocks
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| block | string |
Output
Schema · Response
{
"type": "json",
"example": {
"tool": {
"id": "chain_get_block",
"version": "1.0.0",
"provider": "tollex.robinhood-chain"
},
"result": {
"hash": "0x7a3d7400b27830f4f91c2c16a082486d67c1befecaec2f53b33f1f35d5b62036",
"number": "83335219",
"gasUsed": "412876",
"timestamp": "2026-10-08T13:04:26.000Z",
"parentHash": "0x7a3d7400b27830f4f91c2c16a082486d67c1befecaec2f53b33f1f35d5b62036",
"transactions": 4,
"baseFeePerGas": "10000000",
"l1BlockNumber": "23541870"
},
"evidence": [],
"untrustedOutput": false
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"