# x402 Chain Tools – Transaction Receipt Status

> x402 Chain Tools – Transaction Receipt Status is a paid API for AI agents from blockchain-api.x402-chain-tools.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Checks the confirmation status and receipt of a Base Mainnet transaction by its hash

## Facts

- Endpoint: POST https://blockchain-api.x402-chain-tools.workers.dev/chain/transaction-receipt-status
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-chain-tools-transaction-receipt-status-5251282c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9qtsiViF4oVhUHC781UXT

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-chain-tools-transaction-receipt-status-5251282c -d '<json body>'
```

Example prompt: Can you check whether the Base Mainnet transaction 0x3a4f...c7d2 has been confirmed and whether it succeeded?

## When to prefer this

Use this endpoint when you need to verify the status of a specific Base Mainnet transaction by hash — e.g. after submitting an on-chain payment, transfer, or contract call and you need to confirm finality before proceeding. Prefer this over generic block explorers when operating in an agentic workflow that already uses the x402 payment protocol and needs a machine-readable receipt response.

## Known failure modes

- Transaction not yet mined — returns confirmed:false, receipt:null, receipt_found:false
- Invalid or malformed hash format — rejected by schema pattern validation
- Hash not found on Base Mainnet — returns receipt_found:false
- RPC node timeout or Base network congestion causing delayed response
- Payment failure (x402) if USDC balance is insufficient

## How this service works

Check Base transaction receipt status by transaction hash. Determine whether the transaction is pending, confirmed successful, or confirmed reverted, with receipt, block, and gas details.

## Output

Returns a JSON object with: ok (bool), the queried hash, network identifier (eip155:8453 for Base Mainnet), receipt (full receipt object or null), success (bool or null), confirmed (bool), and receipt_found (bool). If the transaction is not yet mined, receipt and success are null and confirmed/receipt_found are false.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Base Mainnet transaction hash."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "network": "eip155:8453",
  "receipt": null,
  "success": null,
  "confirmed": false,
  "receipt_found": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-chain-tools-transaction-receipt-status-5251282c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from blockchain-api.x402-chain-tools.workers.dev](https://www.zero.xyz/host/blockchain-api.x402-chain-tools.workers.dev/llms.txt)