# EIP-712 Signature Risk Decoder (GET)

> EIP-712 Signature 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-16).

Inspects eth_signTypedData / EIP-712 payloads for security risks — spender fields, deadlines, unlimited allowances, nonces, chainId, verifyingContract — and returns risk flags and a wallet confirmation checklist without signing or sending anything.

## Facts

- Endpoint: POST https://gpt55.558686.xyz/v1/tools/eip712-signature-risk-decoder
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/eip-712-signature-risk-decoder-get-0e556946
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gX5F08CTPR_MCXrobBR-s

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 eip-712-signature-risk-decoder-get-0e556946 -d '<json body>'
```

Example prompt: Before I sign this EIP-712 message in my wallet, can you decode it and flag any risks — like unlimited allowances, suspicious spender addresses, or expired deadlines? Here's the typed data: {"types":{"Permit":[{"name":"owner","type":"address"},{"name":"spender","type":"address"},{"name":"value","type":"uint256"},{"name":"nonce","type":"uint256"},{"name":"deadline","type":"uint256"}]},"domain":{"name":"USD Coin","chainId":8453,"verifyingContract":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA0291"},"message":{"owner":"0xabc...","spender":"0xdeadbeef...","value":"115792089237316195423570985008687907853269984665640564039457584007913129639935","nonce":0,"deadline":9999999999}}.

## When to prefer this

Use this endpoint when a wallet, agent, or dApp needs a pre-signing safety check on an eth_signTypedData / EIP-712 payload — especially for ERC20 Permit, Permit2, transferWithAuthorization, or NFT operator approvals — without executing any transaction or connecting to a node. Prefer the GET variant when the client is a crawler, agent, or tool that handles query parameters more naturally than JSON request bodies.

## Known failure modes

- Malformed or unparseable typed data JSON returns a validation error
- Missing required typed data input returns 400-level error
- Unrecognized EIP-712 type structure may result in incomplete risk analysis
- Chain ID not recognized may reduce quality of contract address context
- Known_addresses map not provided means spender labels will be absent

## Output

A JSON object containing risk flags (e.g. unlimited allowance detected, deadline far in future, unknown spender, chainId mismatch, suspicious verifyingContract), a structured wallet confirmation checklist summarizing what the user is about to approve, and an overall risk assessment — all without producing a signature or calling any external chain RPC.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/eip-712-signature-risk-decoder-get-0e556946/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)
