# Base Token Batch Screen

> Base Token Batch Screen is a paid API for AI agents from base-facts.yankii.fr, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-12).

Batch-screens up to 10 Base token addresses in one call, simulating buy/sell to detect honeypots, taxes, and trading risks without executing real trades.

## Facts

- Endpoint: POST https://base-facts.yankii.fr/v1/batch?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-token-batch-screen-6a3f6af4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Bmo_2_pJKP-Ne3LoI7nk3

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-token-batch-screen-6a3f6af4 -d '<json body>'
```

Example prompt: Can you batch screen these 5 Base token addresses for honeypots and sell tax in one go: 0xAbc...1, 0xDef...2, 0xGhi...3, 0xJkl...4, 0xMno...5?

## When to prefer this

Use this endpoint when you need to screen multiple Base tokens in a single API call and payment, making it 6x cheaper per token than the single-token endpoint ($0.03 for 10 vs $0.005 each). Ideal for bots monitoring new token launches, sniper bots that need to pre-filter many candidates quickly, or any workflow where you have a batch of token addresses to evaluate simultaneously. Prefer the single-token endpoint only when you need trade-size-specific simulation or have just one address to check.

## Known failure modes

- Token address is not a valid 0x-prefixed 20-byte hex — returns validation error
- Token contract not deployed on Base or is a non-standard contract — returned as not_simulated with reason
- More than 10 addresses submitted — request rejected
- Simulation fails due to contract logic (e.g. paused trading, blacklisted addresses) — returned as not_simulated
- Payment insufficient or x402 protocol error — call rejected before processing

## How this service works

Base token BATCH sell check: up to 10 token addresses in one call and one payment. For each token it simulates a small buy and an immediate sell inside eth_call (no trade is sent) and returns buy tax, sell tax, round-trip loss, flags and a plain summary; a token it cannot simulate is returned as not_simulated with the reason. Built for bots that screen many new tokens: $0.03 for up to 10 (single check: $0.005). Facts, not advice.

## Output

For each submitted token address, returns buy tax percentage, sell tax percentage, round-trip loss, risk flags (e.g. honeypot, high tax), and a plain-language summary. Tokens that cannot be simulated are returned with status not_simulated and a reason explaining why.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tokens": {
   "type": "array",
   "items": {
    "type": "string",
    "description": "Token contract address (0x-prefixed hex, 20 bytes)"
   },
   "maxItems": 10,
   "minItems": 1,
   "description": "1 to 10 distinct Base token addresses"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-token-batch-screen-6a3f6af4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from base-facts.yankii.fr](https://www.zero.xyz/host/base-facts.yankii.fr/llms.txt)