# true402 Token Safety Check

> true402 Token Safety Check is a paid API for AI agents from true402.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Checks the safety and risk profile of an ERC-20 token contract on the Base blockchain

## Facts

- Endpoint: POST https://true402.dev/api/v1/token-safety
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/true402-token-safety-check-a359c07b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-SJGTh-_McyXa-0Emwo_a

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 true402-token-safety-check-a359c07b -d '<json body>'
```

Example prompt: Can you run a token safety check on this ERC-20 contract address on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913? I want to know if it's safe before I interact with it.

## When to prefer this

Use this endpoint when you need a quick, pay-per-call token safety screening for ERC-20 contracts on the Base blockchain without requiring an API key — ideal for AI agents operating with crypto wallets that need on-demand DeFi risk assessment before executing trades or interactions.

## Known failure modes

- Invalid or malformed contract address returns error
- Contract address not found on Base network
- Network unavailable or timeout returns 5xx
- Unsupported chain value returns validation error
- Payment failure via HTTP 402 if wallet has insufficient USDC

## How this service works

The machine-native marketplace. Wallet = identity. Pay per call with HTTP 402.

## Output

Returns a safety assessment object for the given ERC-20 token contract on Base, likely including risk flags, honeypot detection, contract verification status, ownership renouncement, liquidity lock status, and other indicators of malicious or suspicious behavior.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "token"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "'base' (default)"
  },
  "token": {
   "type": "string",
   "description": "ERC-20 contract address on Base"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "risk": {
   "type": "string",
   "description": "low | medium | high | critical"
  },
  "chain": {
   "type": "string"
  },
  "erc20": {
   "type": "object",
   "description": "name/symbol/decimals/totalSupply (null if the read failed)"
  },
  "flags": {
   "type": "array",
   "description": "risk flags raised"
  },
  "score": {
   "type": "number",
   "description": "0–100 structural safety score"
  },
  "token": {
   "type": "string"
  },
  "honeypot": {
   "type": "object",
   "description": "buy/sell simulation: sellable, roundTripBps, dex (null if it could not be simulated — never assume safe)"
  },
  "mintable": {
   "type": "boolean",
   "description": "deployed bytecode exposes a mint selector (heuristic)"
  },
  "liquidity": {
   "type": "object",
   "description": "quote-side WETH/USDC liquidity across Uniswap V3 + Aerodrome pools, in USD"
  },
  "ownership": {
   "type": "string",
   "description": "renounced | active | none | unknown"
  },
  "isContract": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/true402-token-safety-check-a359c07b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from true402.dev](https://www.zero.xyz/host/true402.dev/llms.txt)