# RelayShield Token Security Check

> RelayShield Token Security Check is a paid API for AI agents from atq6wtkp6k.execute-api.us-east-1.amazonaws.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Analyzes a crypto token's smart contract for security risks including honeypots, mintable supply, and other critical or warning flags.

## Facts

- Endpoint: POST https://atq6wtkp6k.execute-api.us-east-1.amazonaws.com/prod/v1/payg/token-security
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/relayshield-token-security-check-7c4b00d7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FFqoiDu_xePbekQExlHgF

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-check-7c4b00d7 -d '<json body>'
```

Example prompt: Can you run a RelayShield security check on the token at contract address 0x6982508145454ce325ddbe47a25d4ec3d2311933 on Ethereum (chain ID 1) and tell me the risk level, any honeypot flags, and how many holders it has?

## When to prefer this

Use this endpoint when an agent needs to assess the security of a specific ERC-20 or similar token contract before a trade, investment, or DeFi interaction — especially when screening for honeypots, rug pull risks, or abnormal tokenomics like mintable supply. Prefer this over generic blockchain explorers when you need structured risk flags and a summary risk level in one call.

## Known failure modes

- Invalid or unrecognized contract address returns an error
- Unsupported chain ID results in no data
- Contract not yet indexed on the specified chain returns empty or null results
- Malformed request body causes 400 bad request
- Payment failure or missing x402 payment header causes 402 or authentication error

## How this service works

Screen an ERC-20/BEP-20 token contract for honeypot, mintable-supply, hidden-owner, and other rug-pull risk signals before your agent trades it. Returns risk level, specific critical/warning flags, and basic token metadata. Call before an autonomous trading agent buys or approves spending on an unfamiliar token.

## Output

Returns a risk assessment including risk_level (e.g. HIGH/MEDIUM/LOW), token name and symbol, holder count, chain ID, contract address, a list of warning_flags (e.g. mintable supply), and critical_flags (e.g. honeypot), plus a raw data object with underlying 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/relayshield-token-security-check-7c4b00d7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from atq6wtkp6k.execute-api.us-east-1.amazonaws.com](https://www.zero.xyz/host/atq6wtkp6k.execute-api.us-east-1.amazonaws.com/llms.txt)