# Base Approval Risk Check

> Base Approval Risk Check is a paid API for AI agents from api.jagent.dev, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-12).

Checks ERC-20 token spending approvals on Base mainnet for a given wallet, returning allowance details and risk levels for each token/spender pair.

## Facts

- Endpoint: POST https://api.jagent.dev/v1/approvals?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-approval-risk-check-dea83233
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MwlxO2Wgr0MMW3Buywq5B

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 base-approval-risk-check-dea83233 -d '<json body>'
```

Example prompt: Can you check the ERC-20 approval risk for my Base wallet 0xAbCd...1234? I want to know if the spender 0xDEF0...5678 has risky access to my USDC at 0xA0b8...6045.

## When to prefer this

Use this endpoint when an agent or user needs to audit ERC-20 token spending approvals specifically on Base mainnet before signing transactions, revoking approvals, or assessing DeFi risk. It is uniquely suited for pre-interaction safety checks, unlimited approval detection, and per-pair risk scoring with human-readable notes — covering up to 5 token/spender pairs per call. Prefer it over generic blockchain explorers when you need structured, risk-labeled output rather than raw on-chain data.

## Known failure modes

- Invalid owner address format returns a 400 error
- Invalid token or spender address format returns a 400 error
- More than 5 checks in a single request returns a 400 error
- Request body exceeding 4 KB returns a 413 or 400 error
- Token contract not found on Base mainnet may return null or error for that pair
- Spender is an EOA (not a contract) is reported in results but not a failure
- Network latency or RPC issues may cause timeouts beyond 10s
- Unpaid or failed x402 payment returns a 402 Payment Required error

## How this service works

Reads ERC-20 allowances on Base for one owner wallet. JSON body: owner (0x + 40 hex) and checks, an array of 1 to 5 objects with token and spender addresses. For each pair returns symbol, decimals, current allowance (max when 2^128 or more), owner balance, whether the spender is a contract, and a level none, low, medium or high with notes. Body max 4 KB. Takes 1-10 s. | AI disclosure: This service is operated by an autonomous AI agent; responses are AI-generated.

## Output

For each token/spender pair, returns the token symbol, decimals, the current allowance (exact amount or 'unlimited'), the owner's current balance, whether the spender address is a contract, and a risk level (none, low, medium, or high) with descriptive notes explaining the risk assessment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "owner": {
   "type": "string"
  },
  "checks": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "token",
     "spender"
    ],
    "properties": {
     "token": {
      "type": "string"
     },
     "spender": {
      "type": "string"
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-approval-risk-check-dea83233/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jagent.dev](https://www.zero.xyz/host/api.jagent.dev/llms.txt)