# gigsai Batch Token Risk Check

> gigsai Batch Token Risk Check is a paid API for AI agents from gigsai.xyz, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-10).

Runs honeypot, tax, liquidity, holder, and owner-power risk checks on up to 10 Base token contracts in a single API call.

## Facts

- Endpoint: POST https://gigsai.xyz/api/token/batch?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gigsai-batch-token-risk-check-86475c52
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ndd4nfz81A-cfv77wyiAU

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 gigsai-batch-token-risk-check-86475c52 -d '<json body>'
```

Example prompt: Can you batch-check these 5 Base token contracts for honeypot traps, suspicious taxes, and dangerous owner permissions: 0xABC...1, 0xABC...2, 0xABC...3, 0xABC...4, 0xABC...5?

## When to prefer this

Choose this endpoint when you need to evaluate multiple Base tokens simultaneously, such as in a bot scanning new token launches, a portfolio screener, or an alert pipeline. It is more cost-effective and faster than calling the single-token endpoint repeatedly, and is ideal when you have between 2 and 10 tokens to assess in one pass. Use the single-token endpoint instead when you only have one address to check.

## Known failure modes

- Invalid or non-EVM address format returns validation error
- Token contract not deployed on Base returns not-found or empty result
- More than 10 tokens submitted returns 400 bad request
- Payment not included or insufficient USDC results in 402 Payment Required
- Token with unverified or non-standard contract may return incomplete data
- Newly deployed contract with no trades may yield inconclusive sell simulation

## How this service works

Call when screening several Base tokens at once, e.g. new launches: up to 10 tokens per call, same checks as /api/token/check (sell simulation, taxes, owner powers, liquidity, holders). All-or-nothing: a failed batch is not charged.

## Output

Returns per-token risk data for each submitted contract address, including sell simulation outcome (honeypot yes/no), buy and sell tax percentages, owner privilege flags, liquidity depth, and holder distribution metrics — mirroring the single-token /api/token/check response but batched across up to 10 tokens.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tokens": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^0x[0-9a-fA-F]{40}$"
   },
   "maxItems": 10,
   "minItems": 1,
   "description": "Base token contract addresses"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gigsai-batch-token-risk-check-86475c52/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gigsai.xyz](https://www.zero.xyz/host/gigsai.xyz/llms.txt)