← All endpoints
agent402.tools api block-receipts
https://agent402.tools/api/block-receipts
answers 402
Every transaction receipt in one block, fetched as a single upstream read and summarised: tx count, succeeded vs failed, total gas used, total fees, log count, contract creations, tx-type mix - plus compact per-transaction rows (hash, from, to, status, gas used, effective gas price, fee, log count) capped at 300. Block analytics, failed-tx hunting, or 'who paid what in block N' without N separate
We sent a real
POST request to this endpoint and it
answered 402 with payment requirements we could parse.
- Price
- $0.005
- Network
- base
- Pay to
- 0xaBF4FAbd7c416fB67202E5f9002389Fc75e2a9D0
- Spec dialect
- v2 (declares x402Version 2)
- Transport
- PAYMENT-REQUIRED header
- HTTP method
- POST
- Response latency
- 112 ms
- Payment options
- 13 usable of 13
- Last checked
- 2026-09-06T01:16:42.018Z (2h ago)
- Category
- finance-crypto
Re-check it yourself:
curl "https://api.the402.dev/validate?url=https%3A%2F%2Fagent402.tools%2Fapi%2Fblock-receipts"