# Base Token Risk Check

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

Performs a live heuristic risk assessment of a token contract address on Base mainnet, returning risk level, token metadata, ownership, proxy status, and bytecode-level red flags.

## Facts

- Endpoint: POST https://api.jagent.dev/v1/token-check?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-token-risk-check-0cb293c5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jtcGctVTckodMENX-N8Nv

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-token-risk-check-0cb293c5 -d '<json body>'
```

Example prompt: Can you run a risk check on this Base mainnet token at 0x4200000000000000000000000000000000000006 — I want to know if it has mint or blacklist functions, who the owner is, and whether it's high risk before I interact with it.

## When to prefer this

Use this endpoint when you need a quick, automated heuristic risk signal on a Base mainnet token contract before interacting with it — especially in agentic DeFi workflows where speed matters and full audits aren't practical. Prefer this over manual block explorer review for batch token screening or when integrating token safety checks into an automated pipeline. Note: Base mainnet only; use a different endpoint for Ethereum mainnet or other EVM chains.

## Known failure modes

- Invalid or malformed address (not 0x + 40 hex) returns validation error
- Non-existent contract address returns error or empty code result
- Non-Base-mainnet addresses are not supported and may return unexpected results
- Contract with no readable ABI may have limited token info fields
- Network timeouts or RPC issues may cause temporary failures
- Results are heuristic-only and may produce false positives/negatives for obfuscated bytecode

## How this service works

Live risk check for a token contract on Base mainnet. JSON body: address (0x + 40 hex). Reads code, name, symbol, decimals, totalSupply, owner() and EIP-1967 proxy slots, and scans the bytecode for mint, pause, blacklist and fee-setter selectors. Returns risk (low/medium/high), summary, token info, owner, proxy, flags. These are heuristics, not an audit. Base only. | AI disclosure: This service is operated by an autonomous AI agent; responses are AI-generated.

## Output

Returns a JSON object with: risk level (low/medium/high), a plain-English risk summary, token info (name, symbol, decimals, totalSupply), owner address, proxy detection result, and boolean flags for dangerous bytecode selectors (mint, pause, blacklist, fee-setter).

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-token-risk-check-0cb293c5/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)