# AgentForge ERC-20 Approval Risk Scanner

> AgentForge ERC-20 Approval Risk Scanner is a paid API for AI agents from agentforge-taupe.vercel.app, paid per call via x402, $0.015/call, status unknown (last checked 2026-10-01).

Scans a wallet address for risky ERC-20 token approvals, flagging unlimited allowances and unverified spender contracts before an agent authorizes a new one.

## Facts

- Endpoint: GET https://agentforge-taupe.vercel.app/v1/approval-scan?utm_source=zero.xyz
- Price: $0.015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentforge-erc-20-approval-risk-scanner-c9704134
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Zu245QHL0IcSA_29junRA

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 agentforge-erc-20-approval-risk-scanner-c9704134
```

Example prompt: Before I approve this new DeFi contract, scan my Ethereum wallet 0xAbC1234567890AbCdEf1234567890AbCdEf123456 for any existing unlimited ERC-20 allowances or unverified spender contracts that I should know about.

## When to prefer this

Choose this endpoint when an AI agent or user needs to audit existing ERC-20 token allowances on a specific wallet before authorizing a new DeFi interaction. It is particularly valuable as a pre-transaction safety gate to prevent approval-based exploits such as allowance draining. Prefer it over generic transaction decoders or contract auditors when the specific concern is token approval risk across multiple EVM-compatible chains.

## Known failure modes

- Invalid wallet address format — must be a valid 0x-prefixed 40-character hex address
- Unsupported chain value — must be one of: ethereum, base, polygon, arbitrum, optimism, avalanche
- Missing required wallet address parameter
- RPC or blockchain data unavailability causing incomplete scan results
- Payment failure (x402) if USDC balance or payment channel is insufficient

## How this service works

ERC-20 approval risk scanner for wallets: flags unlimited allowances and unverified spender contracts before an agent authorizes a new one. Category: data.

## Output

Returns a risk report for the scanned wallet, including a list of detected ERC-20 approvals, flags for unlimited (infinite) allowances, identification of unverified or suspicious spender contracts, and an overall risk assessment to help an agent decide whether it is safe to proceed with a new approval.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "ethereum",
    "base",
    "polygon",
    "arbitrum",
    "optimism",
    "avalanche"
   ],
   "type": "string",
   "default": "ethereum"
  },
  "address": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$",
   "description": "Wallet address to scan"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentforge-erc-20-approval-risk-scanner-c9704134/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentforge-taupe.vercel.app](https://www.zero.xyz/host/agentforge-taupe.vercel.app/llms.txt)
