# EVM Token Safety & Rug-Risk Report (Base Chain)

> EVM Token Safety & Rug-Risk Report (Base Chain) is a paid API for AI agents from obol-x402.fly.dev, paid per call via x402, $0.1/call, status down (last checked 2026-10-13).

Returns a comprehensive token safety report for any EVM token contract on Base, including honeypot detection, rug-pull risk signals, ownership analysis, and a composite risk score.

## Facts

- Endpoint: POST https://obol-x402.fly.dev/v1/evm/token/:address?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: down
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-token-safety-rug-risk-report-base-chain-db567817
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7hubto91aHiDN1TGhzNLc

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-token-safety-rug-risk-report-base-chain-db567817 -d '<json body>'
```

Example prompt: Before I buy this token, can you run a full safety check on the Base contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 — I want to know if it's a honeypot, whether ownership is renounced, if minting is possible, and what the overall rug-pull risk verdict is?

## When to prefer this

Use this endpoint when an AI trading agent, wallet agent, or DeFi bot needs to screen an unknown EVM token on Base before executing a buy, swap, or approval. It is specifically tuned for Base chain, provides live on-chain data (not cached lists), and returns a cryptographically signed result suitable for audit trails. Prefer over generic token lists when you need fine-grained contract-level risk signals like proxy upgradeability and mint authority.

## Known failure modes

- Invalid or non-existent contract address returns an error
- Non-Base-chain addresses may not be supported
- Payment required (x402) — missing or invalid USDC payment returns 402
- Contract at address is not an ERC-20 token — conformance check may fail or return non-conformance
- Rate limiting or fly.dev infrastructure downtime causing 503

## Output

A cryptographically signed (Ed25519) JSON report containing: composite risk score and plain-language verdict, honeypot detection result, rug-pull risk signals, ownership type (renounced / EOA / multisig), upgradeable-proxy detection flag, mint capability flag, and ERC-20 conformance status — all derived from live on-chain reads of the specified Base token contract.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-token-safety-rug-risk-report-base-chain-db567817/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from obol-x402.fly.dev](https://www.zero.xyz/host/obol-x402.fly.dev/llms.txt)