# Ethereum Token Safety Checker

> Ethereum Token Safety Checker 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).

Analyzes an ERC-20 token contract address on Ethereum for safety signals and risk indicators

## Facts

- Endpoint: POST https://true402.dev/api/v1/ethereum/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/ethereum-token-safety-checker-a8b0c2cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hw0nE2oSZFI7gGhe3inzd

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 ethereum-token-safety-checker-a8b0c2cf -d '<json body>'
```

Example prompt: Before I buy any, can you check if this Ethereum token contract is safe? The address is 0xdAC17F958D2ee523a2206206994597C13D831ec7.

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call token safety assessment for an ERC-20 contract on Ethereum, especially in automated DeFi workflows where wallet-based micropayment via HTTP 402 is acceptable. Prefer this over manual block explorer lookups when you need programmatic risk signals integrated into an agent pipeline.

## Known failure modes

- Invalid or malformed contract address returns an error
- Contract address not found on Ethereum mainnet
- Unsupported chain (only Ethereum is supported)
- Rate limiting or payment failure via HTTP 402
- Token contract too new to have sufficient analysis data

## How this service works

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

## Output

Returns a JSON object containing safety signals and risk assessment for the specified ERC-20 token contract on Ethereum, potentially including honeypot detection, ownership risks, liquidity flags, and contract vulnerability indicators.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "token"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "Chain to check; only 'ethereum' is supported on this endpoint (default)"
  },
  "token": {
   "type": "string",
   "description": "ERC-20 contract address on Ethereum"
  }
 }
}
```

## 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 + uniswap-v2 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/ethereum-token-safety-checker-a8b0c2cf/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)