# Invoket Batch Address Screening

> Invoket Batch Address Screening is a paid API for AI agents from api.invoket.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Screens multiple blockchain wallet addresses in a single batch call, returning provenance-backed verification results for each address

## Facts

- Endpoint: POST https://api.invoket.com/screen/address/batch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-batch-address-screening-8f5c892c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9f6xFE-JpFJsVDOANsM5j

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 invoket-batch-address-screening-8f5c892c -d '<json body>'
```

Example prompt: Before sending payments, screen these 10 wallet addresses on Ethereum to make sure they're all valid — run them through Invoket's batch address check and flag any that come back with errors.

## When to prefer this

Use this endpoint when you need to validate multiple blockchain addresses in a single API call rather than making individual requests per address. It is the right choice when an AI agent must verify a list of wallet addresses before executing bulk transfers, payouts, or airdrops — especially when cost efficiency matters (batch priced per unit) and you need per-address provenance in responses. Prefer it over single-address endpoints whenever you have 2 or more addresses to check.

## Known failure modes

- Empty batch array returns 400 and is not charged
- Batch exceeding 500 items returns 400 and is not charged
- Malformed or unrecognizable individual addresses return per-item error with code rather than failing the whole batch
- Invalid or missing 'items' field returns 400
- Unsupported chain identifier may yield INVALID_INPUT at item level
- Network or upstream service unavailability may return 5xx errors

## How this service works

The checks your agent runs before it acts: verify a bank account, a phone number, a law in force, the weather or a vehicle — computed from official sources, with provenance in every response. You only pay for answers.

## Output

A structured array of per-address results, one entry per input item. Each successful entry includes verification status and provenance data from official sources. Each failed or malformed entry includes an error object with a code (MISSING_PARAMETER, INVALID_INPUT, or UNRECOGNIZED_ADDRESS_FORMAT) at its array position without failing the entire batch. The overall batch response is a JSON object wrapping these results.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "items"
 ],
 "properties": {
  "items": {
   "type": "array",
   "description": "Array of addresses screened in one settlement. Its length is priced per unit (base + N x unit), capped at 500; an empty or oversized batch is a 400, never charged. Each item takes an 'address' and an optional 'chain' that is law for THAT item. A malformed or unrecognizable address yields {error, code} at its position without failing the batch - the codes are the single endpoint's, MISSING_PARAMETER, INVALID_INPUT and UNRECOGNIZED_ADDRESS_FORMAT"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-batch-address-screening-8f5c892c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.invoket.com](https://www.zero.xyz/host/api.invoket.com/llms.txt)