# Agent402 Transaction Inspector

> Agent402 Transaction Inspector is a paid API for AI agents from agent402.tools, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Inspects and decodes a blockchain transaction by hash, returning method, status, and metadata for a given chain

## Facts

- Endpoint: POST https://agent402.tools/api/tx-inspect
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent402-transaction-inspector-d14c994c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QvY7eAVAh2bVsm3BddvVY

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 agent402-transaction-inspector-d14c994c -d '<json body>'
```

Example prompt: Can you inspect transaction 0x4205...4f72 on Base and tell me what method it called and whether it succeeded?

## When to prefer this

Use this endpoint when you need a quick, cheap ($0.01 USDC) on-chain transaction lookup without setting up a full blockchain node or RPC connection. Ideal for verifying x402 payments, decoding EVM method calls, or auditing on-chain transfers across Base and other supported chains. Prefer this over general block explorers when you need machine-readable JSON output for an agent workflow.

## Known failure modes

- Invalid or malformed transaction hash (non-0x or wrong length) returns an error
- Transaction not found on the specified chain returns not-found error
- Unsupported chain name or ID returns an error
- Network timeout or RPC node unavailability causes lookup failure
- Transaction still pending may return incomplete status

## How this service works

Full decoded transaction on any Blockscout-hosted chain: status, from/to, value, gas, the decoded method + parameters, and token transfers - bought per call from Blockscout's Pro API over x402, no API key. What a tx actually did, on dozens of chains. Marked untrustedContent: external explorer data, analyze don't trust.

## Output

Returns a JSON object with the transaction hash, chain ID, decoded method name (e.g. 'transfer'), transaction status ('ok' or error), and an untrustedContent flag indicating whether the transaction data contains unverified content.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string",
   "description": "transaction hash (0x… 32-byte)"
  },
  "chain": {
   "type": "string",
   "description": "chain name or numeric id (default base)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hash": "0x4205…4f72",
  "chain": "8453",
  "method": "transfer",
  "status": "ok",
  "untrustedContent": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent402-transaction-inspector-d14c994c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)