# EVM Signature Intent Decoder

> EVM Signature Intent Decoder is a paid API for AI agents from x402.dailyelo.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-10).

Decodes EVM signature requests (EIP-712, Permit/Permit2, ERC-20 approve calldata) into structured human-readable intent with token, spender, amount, expiry, risk flags, and action hints

## Facts

- Endpoint: POST https://x402.dailyelo.com/v1/sign-decode?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-signature-intent-decoder-853ebd09
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4Np3BbekSLfj3_PPPWInd

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-signature-intent-decoder-853ebd09 -d '<json body>'
```

Example prompt: Before I sign this, can you decode what this EIP-712 Permit2 message is actually asking me to approve — the domain, message, and primaryType are here — and tell me what token, which spender, how much, when it expires, and whether there are any risk flags I should know about?

## When to prefer this

Use this endpoint when an AI agent or wallet interface needs to explain to a user what an EVM signing request will authorize before they sign it — especially for EIP-712, Permit, Permit2, or ERC-20 approve flows. Prefer this over generic calldata decoders because it specifically outputs structured risk_flags and action_hint fields tuned for token approval safety, and it is deterministic (no LLM hallucination risk).

## Known failure modes

- Unrecognized signature format returns parsing error — calldata or message must conform to EIP-712, Permit, Permit2, or ERC-20 approve ABI
- Missing required fields (domain or message for typed data, calldata for raw approve) returns validation error
- Malformed calldata hex string returns decode error
- Unsupported primaryType returns unknown type error

## How this service works

Decode an EVM signature request (EIP-712 typed data, Permit/Permit2, or ERC-20 approve calldata) into a structured intent: what token, which spender, how much, until when, plus risk_flags and an action_hint. Deterministic, no LLM. Answers an agent's question 'what am I about to sign?'

## Output

A structured intent object containing: the token being approved, spender address, approval amount, expiry timestamp, risk_flags (array of detected danger signals), and an action_hint summarizing what the signature would authorize — all determined deterministically without an LLM.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "object"
  },
  "message": {
   "type": "object"
  },
  "calldata": {
   "type": "string"
  },
  "primaryType": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "amount": "unlimited",
  "intent": "grant_allowance",
  "spender": "0x66a9893cC07D91D95644AEDD05D03f95e1dBA8Af",
  "standard": "Permit2-AllowanceTransfer (PermitSingle)",
  "confidence": 1,
  "expires_at": "2026-07-12T11:17:58Z",
  "risk_flags": [
   "unlimited_allowance"
  ],
  "action_hint": "ask_for_confirmation",
  "spender_known": "Uniswap Universal Router v2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-signature-intent-decoder-853ebd09/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.dailyelo.com](https://www.zero.xyz/host/x402.dailyelo.com/llms.txt)