# intent402 Approve Check

> intent402 Approve Check is a paid API for AI agents from intent402.dylan-caponi.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Checks whether a token approval is in place and returns an unsigned approval transaction if more allowance is needed before executing a swap or transfer.

## Facts

- Endpoint: POST https://intent402.dylan-caponi.workers.dev/approve-check
- 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/intent402-approve-check-2fed26bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PnwahXsEJ5USuS7Pc-4af

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 intent402-approve-check-2fed26bf -d '<json body>'
```

Example prompt: Before executing my USDC swap on Base, check whether my wallet 0xABC...123 has approved enough allowance — and if not, give me the unsigned approval transaction I need to sign first.

## When to prefer this

Use this endpoint when an AI agent needs to pre-flight check token approvals before executing an EVM transaction on Base, especially in automated DeFi workflows where the agent must determine whether a signing step is required before proceeding. It is ideal when you need an unsigned, ready-to-sign approval transaction returned programmatically rather than constructing ERC-20 calldata manually. Prefer this over generic RPC calls when you want intent-level resolution rather than raw contract interaction.

## Known failure modes

- Invalid or missing wallet/token address returns an error
- Unsupported chain ID may cause resolution failure
- Malformed request body returns 400-level error
- RPC node unavailability may cause timeout or 5xx
- Insufficient USDC payment (below $0.005) results in 402 Payment Required

## How this service works

Check if a token approval is needed and return the approval transaction if so.

## Output

Returns a JSON object indicating whether the current allowance is sufficient (approved: true/false), the required token amount, the current allowance, and if approval is needed, a fully-formed unsigned transaction object (to, data, value, chainId) that the agent or user can sign and broadcast to grant the necessary token allowance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "example": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "approved": false,
  "requiredAmount": "100000000",
  "currentAllowance": "0",
  "approvalTransaction": {
   "to": "0x...",
   "data": "0x...",
   "value": "0",
   "chainId": 8453
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/intent402-approve-check-2fed26bf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intent402.dylan-caponi.workers.dev](https://www.zero.xyz/host/intent402.dylan-caponi.workers.dev/llms.txt)