# Base ERC-20 Token Safety Score

> Base ERC-20 Token Safety Score is a paid API for AI agents from 47620.xyz, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-02).

Returns a 0-100 safety score with detailed reasons for a Base chain ERC-20 token address, covering code presence, metadata, total supply, proxy signals, DEX liquidity, and volume.

## Facts

- Endpoint: GET https://47620.xyz/x/base/token-safety/:address?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-erc-20-token-safety-score-cf46f944
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qJJa2bjVs0n99wwvGrLi7

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-erc-20-token-safety-score-cf46f944
```

Example prompt: Before I buy this token, can you run a safety check on the Base ERC-20 at address 0x1234...abcd and tell me the safety score and any red flags like missing liquidity, proxy contracts, or suspicious metadata?

## When to prefer this

Choose this endpoint when you need a single-call pre-trade safety verdict specifically for ERC-20 tokens on the Base chain. It is ideal for DeFi trading agents, token listing pipelines, or any workflow that needs to quickly triage unknown tokens before committing funds. Prefer it over generic contract explorers when you want a structured numeric score with reasons rather than raw on-chain data, and when you need DEX liquidity and volume signals bundled with metadata checks in one response.

## Known failure modes

- Invalid or non-checksummed address format returns a 400 error
- Address that is a wallet (not a contract) returns low score with 'no code' reason
- Token not listed on any Base DEX returns low liquidity/volume scores
- Network congestion or RPC issues may cause timeout or 503 error
- Very new tokens may lack liquidity data, resulting in partial scores
- Proxy detection may produce false positives for legitimate upgradeable contracts

## How this service works

0-100 safety score with reasons for a base ERC-20: does the address have code, name/symbol/decimals, total supply, proxy signal, DEX liquidity and volume. A pre-trade due-diligence verdict.

## Output

Returns a 0-100 integer safety score accompanied by a set of human-readable reason strings explaining the score. Individual checks include: whether the address contains deployed contract code, presence and validity of ERC-20 metadata (name, symbol, decimals), total supply value, detection of proxy/upgradeable contract patterns, DEX liquidity depth, and recent DEX trading volume. A higher score indicates lower risk; a lower score highlights specific failure reasons.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-erc-20-token-safety-score-cf46f944/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 47620.xyz](https://www.zero.xyz/host/47620.xyz/llms.txt)
