# BitBooth Tx Explain

> BitBooth Tx Explain is a paid API for AI agents from app.heinrichstech.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Decodes a Base-family EVM transaction hash into a human-readable narrative plus structured signals (4-byte selector, ERC-20 Transfer event logs), explicitly flagging reverted transactions

## Facts

- Endpoint: POST https://app.heinrichstech.com/v1/cdp/tx-explain
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitbooth-tx-explain-f1c34bcf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vLwkn0wjhKq1kMn6d8VdC

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 bitbooth-tx-explain-f1c34bcf -d '<json body>'
```

Example prompt: Can you explain what happened in Base transaction 0x4a3b...c9f2 — specifically whether the ERC-20 transfer went through or if it reverted?

## When to prefer this

Choose this endpoint when you need to verify whether a specific Base-network EVM transaction succeeded or reverted, especially for payment verification workflows where a counterparty might present a reverted tx as a valid payment. Also ideal for agents that need to explain on-chain ERC-20 activity (transfers, approvals, transferFrom calls) to non-technical users. Prefer over raw RPC calls when you want both a narrative explanation and structured decoded signals without writing your own ABI decoding logic. Best suited for Base and Base Sepolia; not for Ethereum mainnet or other L1/L2 chains.

## Known failure modes

- Transaction hash not found on Base or Base Sepolia — returns error indicating unknown hash
- Transaction is on an unsupported EVM chain (non-Base family) — returns chain not supported error
- Malformed transaction hash input — returns validation error
- Transaction has no ERC-20 Transfer events (e.g. pure ETH transfer) — returns narrative with empty log fields
- Payment of 0.005 USDC not received — returns 402 payment required
- Network timeout fetching RPC data — returns retriable error

## How this service works

BitBooth Tx Explain: pay 0.005 USDC, hand in a Base-family EVM transaction hash, get back a human-readable narrative of what the tx did plus the structured signals it was derived from — 4-byte selector decode of tx.input (transfer / approve / transferFrom) and ERC-20 Transfer event log decode from the receipt. Reverted txs are surfaced explicitly so a counterparty can't pass off a reverted payment as a success.

## Output

A JSON response containing a human-readable narrative description of what the transaction did, a decoded 4-byte function selector identifying the called method (e.g. transfer, approve, transferFrom), decoded ERC-20 Transfer event logs from the transaction receipt, and an explicit revert flag indicating whether the transaction succeeded or failed on-chain.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bitbooth-tx-explain-f1c34bcf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from app.heinrichstech.com](https://www.zero.xyz/host/app.heinrichstech.com/llms.txt)