# Base Rugcheck - EVM Token Safety Verdict

> Base Rugcheck - EVM Token Safety Verdict is a paid API for AI agents from base-rugcheck.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns a GO/CAUTION/DANGER safety verdict for an EVM token by reading on-chain data, with reasons explaining the verdict

## Facts

- Endpoint: GET https://base-rugcheck.vercel.app/api/rugcheck
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-rugcheck-evm-token-safety-verdict-eecb8cfd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dd2vwanzWSMT7FbN0lxUx

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-rugcheck-evm-token-safety-verdict-eecb8cfd
```

Example prompt: Is this BNB chain token safe to trade? Check address 0x4B0F1812e5Df2A09796481Ff14017e6005508003 on BNB and give me a GO, CAUTION, or DANGER verdict with the reasons.

## When to prefer this

Use this endpoint when you need a quick, pay-per-call on-chain safety verdict for an EVM token and want a structured GO/CAUTION/DANGER classification with reasons — especially useful in DeFi agent workflows where you need to gate trades or warn users before interacting with unknown tokens.

## Known failure modes

- Invalid or malformed token address returns an error
- Unsupported chain name causes a rejection
- Token not found on-chain may return an error or inconclusive result
- Payment failure via x402 USDC prevents the call from completing
- Network timeouts when reading on-chain data

## How this service works

Token safety check with honeypot simulation, buy/sell tax, holder concentration and deployer privileges (GO/CAUTION/DANGER) for EVM tokens on eth, bnb, or base.

## Output

A JSON object containing the chain name, token address, a verdict (GO, CAUTION, or DANGER), and an array of human-readable reasons explaining why the verdict was assigned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "auto",
    "new",
    "mature"
   ],
   "type": "string",
   "description": "Scoring mode."
  },
  "chain": {
   "enum": [
    "eth",
    "bnb",
    "base"
   ],
   "type": "string",
   "description": "EVM chain."
  },
  "token": {
   "type": "string",
   "description": "Token contract address (0x...)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "bnb",
  "token": "0x...",
  "reasons": [
   "..."
  ],
  "verdict": "CAUTION"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-rugcheck-evm-token-safety-verdict-eecb8cfd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from base-rugcheck.vercel.app](https://www.zero.xyz/host/base-rugcheck.vercel.app/llms.txt)