# RelayShield Token Security Analyzer

> RelayShield Token Security Analyzer is a paid API for AI agents from api.relayshield.net, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Analyzes an EVM token contract address for security risks, returning risk level, warning flags (e.g. mintable supply), and critical flags (e.g. honeypot) along with holder count and token metadata.

## Facts

- Endpoint: POST https://api.relayshield.net/v1/payg/token-security
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relayshield-token-security-analyzer-23f4e152
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_juMvPEthTBbakYFBvR4pr

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 relayshield-token-security-analyzer-23f4e152 -d '<json body>'
```

Example prompt: Before I buy, can you run a security scan on this token contract 0x6982508145454ce325ddbe47a25d4ec3d2311933 on Ethereum mainnet (chain ID 1) and tell me the risk level and any honeypot or mintable supply flags?

## When to prefer this

Choose this endpoint when you need a quick, automated security assessment of an EVM token contract — especially for honeypot detection, mintable supply checks, and holder distribution — before executing a trade or adding a token to a portfolio. It is particularly useful for DeFi agents and trading bots that need a pay-per-call, low-friction risk signal without requiring API key management.

## Known failure modes

- Invalid or malformed contract address returns an error
- Unsupported chain ID returns an error or empty result
- Undeployed or non-token contract address may return low-confidence results
- Network or RPC timeout leads to a failed scan
- Payment failure (x402) results in 402 Payment Required before processing

## How this service works

RelayShield Landing Site

## Output

Returns a JSON object with ok status, the token's name and symbol, chain ID, contract address, a risk level string (e.g. HIGH, MEDIUM, LOW), holder count, a list of warning flags (e.g. 'mintable supply'), and a list of critical flags (e.g. 'honeypot'), plus a raw data object with underlying scan details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain_id": {
   "type": "string",
   "description": "EVM chain ID (default: 1 for Ethereum)"
  },
  "contract_address": {
   "type": "string",
   "description": "EVM token contract address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {
   "raw": {},
   "chain_id": "1",
   "risk_level": "HIGH",
   "token_name": "Example Token",
   "holder_count": "12345",
   "token_symbol": "EXT",
   "warning_flags": [
    "mintable supply"
   ],
   "critical_flags": [
    "honeypot"
   ],
   "contract_address": "0x6982508145454ce325ddbe47a25d4ec3d2311933"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relayshield-token-security-analyzer-23f4e152/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.relayshield.net](https://www.zero.xyz/host/api.relayshield.net/llms.txt)
