# EVM Transaction Calldata Risk Decoder (GET)

> EVM Transaction Calldata Risk Decoder (GET) is a paid API for AI agents from gpt55.558686.xyz, paid per call via x402, $0.01/call, status down (last checked 2026-09-07).

Decodes and risk-scores raw EVM calldata for common token operations (ERC20/ERC721/ERC1155) without requiring a private key, sending a transaction, or calling external APIs.

## Facts

- Endpoint: POST https://gpt55.558686.xyz/v1/tools/evm-transaction-risk-decoder
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-07
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-transaction-calldata-risk-decoder-get-271cf03e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TcZllw9gdV0BZ32ZGcMcf

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 evm-transaction-calldata-risk-decoder-get-271cf03e -d '<json body>'
```

Example prompt: Before I sign this transaction, can you decode the calldata and tell me what it's doing and whether there are any red flags? The calldata is 0x095ea7b3000000000000000000000000abcdef1234567890abcdef1234567890abcdef12ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff and it's going to contract 0x6B175474E89094C44Da98b954EedeAC495271d0F on Ethereum mainnet.

## When to prefer this

Use this endpoint when a wallet, agent, or dApp needs to explain raw EVM calldata to a user before signing — especially for ERC20 approve, transferFrom, permit, setApprovalForAll, and multicall patterns. Prefer this over generic LLM decoding when you need structured risk flags and a confirmation checklist. Choose the GET variant when your client cannot easily construct a JSON body (e.g. browser redirects, crawlers, wallet deep-links).

## Known failure modes

- Unrecognized or custom calldata selector returns partial or no decode
- Malformed hex calldata returns a 400 error
- Unsupported chain identifier may limit risk context
- Payment not included or insufficient USDC causes 402 response
- Very long or nested multicall data may hit the 20000-character input limit

## Output

Returns a structured response with: decoded function name and ABI parameters, human-readable token amounts and addresses, risk flags (e.g. unlimited approval, suspicious recipient, unknown contract), and a checklist of items the user should confirm before signing. No transaction is sent.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-transaction-calldata-risk-decoder-get-271cf03e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gpt55.558686.xyz](https://www.zero.xyz/host/gpt55.558686.xyz/llms.txt)