# DeFi Safety Oracle — Batch Token Screen

> DeFi Safety Oracle — Batch Token Screen is a paid API for AI agents from oracle.cyberwarex.com, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-15).

Screens up to 25 Base or BSC tokens in parallel for honeypot, rug-pull, and safety risks, returning per-token grade, tradability, and flags in a single call.

## Facts

- Endpoint: POST https://oracle.cyberwarex.com/screen
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/defi-safety-oracle-batch-token-screen-764af417
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xj3OJ1FuDba1EOE_eBOaj

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 defi-safety-oracle-batch-token-screen-764af417 -d '<json body>'
```

Example prompt: Can you batch-screen these 10 Base token addresses for honeypot and rug-pull risk and tell me which ones are safe to trade: 0xabc..., 0xdef..., (and the rest)?

## When to prefer this

Choose this endpoint when you need to assess multiple tokens (2–25) in a single API call rather than making repeated single-token calls. It is ideal for pre-trade screening pipelines, portfolio bots, or watchlist audits where throughput matters. Prefer it over the single /token endpoint whenever you have a batch of addresses ready to evaluate simultaneously on Base or BSC.

## Known failure modes

- Token times out after 20s and returns {address, error} rather than full result
- Invalid or unsupported chain value (only 'base' and 'bsc' accepted)
- Batch exceeds 25 tokens — request rejected
- Token address is malformed or not a deployed contract
- All workers busy causing increased latency under heavy load
- Payment of 0.1 USDC not fulfilled, resulting in 402 error

## How this service works

Batch token screen: up to 25 tokens (Base or BSC) assessed in parallel via the same in-process engine as /token. Per-token 20s timeout, runs on a ThreadPoolExecutor (max_workers=8); a token that times out or errors returns {address, error} instead of blocking the batch. Summary + per-token grade/tradeable/is_honeypot/flags.

## Output

Returns a batch summary plus a per-token breakdown including safety grade, tradeable boolean, is_honeypot flag, and specific risk flags. Tokens that time out (20s per-token limit) or error return an {address, error} object instead of blocking the whole batch.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tokens": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "address"
    ],
    "properties": {
     "chain": {
      "enum": [
       "base",
       "bsc",
       "ethereum",
       "polygon",
       "arbitrum",
       "robinhood"
      ],
      "type": "string",
      "default": "base"
     },
     "address": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$",
      "description": "ERC-20 token contract address."
     }
    }
   },
   "maxItems": 25,
   "minItems": 1,
   "description": "Tokens to screen, at most 25 per call."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/defi-safety-oracle-batch-token-screen-764af417/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oracle.cyberwarex.com](https://www.zero.xyz/host/oracle.cyberwarex.com/llms.txt)