# Transaction Status & Revert Reason

> Transaction Status & Revert Reason is a paid API for AI agents from api.eucompliance.tools, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Returns full transaction status, block info, gas used, fee paid, and — for failed transactions — the plain-text revert reason recovered by replaying the call against its block.

## Facts

- Endpoint: GET https://api.eucompliance.tools/x402/tx
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transaction-status-revert-reason-1e5f2ead
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_41frXWFLlE_lDqsvBUYCG

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 transaction-status-revert-reason-1e5f2ead
```

Example prompt: Can you check what happened to my transaction 0x4a3b...f9c2 on Base — did it succeed, and if it failed, what was the revert reason?

## When to prefer this

Use this endpoint when you need to understand why a transaction failed and need the decoded revert reason — not just a pass/fail status. Unlike raw JSON-RPC eth_getTransactionReceipt calls, this endpoint replays the transaction against its block to recover the plain-text revert message. Prefer it over a generic Multi-Chain RPC Gateway when the goal is diagnosis rather than raw data, and over the Transaction Pre-flight Check when the transaction has already been submitted.

## Known failure modes

- Invalid or malformed tx_hash returns an error — hash must be a valid 0x-prefixed hex string
- Transaction not found on the specified chain (wrong chain selected)
- Revert reason unavailable if the node cannot replay the historical block (archive node limitation)
- Unsupported chain identifier returns a validation error
- Network or RPC timeout causing delayed or missing response

## How this service works

What happened to my transaction? Status, block, gas used, fee paid - and if it failed, the revert reason in plain text, recovered by replaying the call against its block. The receipt alone does not carry that reason.

## Output

Returns the transaction status (success/failure), block number, gas used, total fee paid, and — critically for failed transactions — the human-readable revert reason recovered by replaying the call against the original block. This goes beyond a raw receipt by decoding the actual failure message from the EVM.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "tx_hash"
     ],
     "properties": {
      "chain": {
       "enum": [
        "base",
        "ethereum",
        "arbitrum",
        "optimism",
        "polygon"
       ],
       "type": "string"
      },
      "tx_hash": {
       "type": "string",
       "description": "the 0x… transaction hash"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transaction-status-revert-reason-1e5f2ead/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.eucompliance.tools](https://www.zero.xyz/host/api.eucompliance.tools/llms.txt)