# revert.wtf ABI-Aware EVM Revert Data Decoder

> revert.wtf ABI-Aware EVM Revert Data Decoder is a paid API for AI agents from revert.wtf, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Decodes raw EVM revert bytes into human-readable error messages using an optional ABI JSON for custom error types.

## Facts

- Endpoint: POST https://revert.wtf/api/x402/revert-decode?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/revert-wtf-abi-aware-evm-revert-data-decoder-29799c46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pc0W79O0eqGRs0MXY6zlu

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 revert-wtf-abi-aware-evm-revert-data-decoder-29799c46 -d '<json body>'
```

Example prompt: Can you decode this EVM revert data for me — the raw bytes are 0x08c379a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000134e6f7420656e6f75676820616c6c6f77616e6365000000000000000000000000 — and if it helps, here's the contract ABI: [{"type":"error","name":"InsufficientAllowance","inputs":[{"name":"needed","type":"uint256"},{"name":"available","type":"uint256"}]}]

## When to prefer this

Use this endpoint when you have raw EVM revert bytes from a failed transaction and need to understand the human-readable error. It is the right choice when dealing with custom Solidity errors that require ABI context to decode fully, or when you need a fast, deterministic programmatic decode rather than a natural-language explanation. Prefer this over the revert.wtf error explanation endpoint when you specifically have raw hex bytes and want structured decoded output rather than a prose explanation.

## Known failure modes

- Invalid or malformed hex data returns a decode error
- ABI JSON parse failure if abiText is malformed JSON
- Unknown 4-byte selector with no ABI provided results in partial decode (selector only)
- Empty data field returns an error indicating no revert data to decode
- Payment failure (x402) if USDC balance is insufficient

## How this service works

Paid hosted ABI-aware EVM revert data decoder. Send revert bytes and optionally an ABI JSON string.

## Output

Returns the decoded revert reason as a human-readable string, including the error name, decoded parameters, and their values when an ABI is provided. For standard errors (e.g. Error(string) or Panic(uint256)) decoding works without an ABI; for custom errors the ABI JSON enables full parameter decoding.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "string"
  },
  "abiText": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/revert-wtf-abi-aware-evm-revert-data-decoder-29799c46/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from revert.wtf](https://www.zero.xyz/host/revert.wtf/llms.txt)