# Invoket Batch Entity Screening

> Invoket Batch Entity 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).

Screen up to 200 entities (IBANs, phone numbers, laws, weather, vehicles) in a single batch call with provenance-backed verdicts

## Facts

- Endpoint: POST https://api.invoket.com/screen/entity/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-entity-screening-f142ec64
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LjjLMXHJJYJvBQftx3UPo

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-entity-screening-f142ec64 -d '<json body>'
```

Example prompt: Before we process these 5 wire transfers, screen all the recipient IBANs at once to make sure they're valid — include weak matches in the verdict so I can review anything borderline.

## When to prefer this

Use this batch endpoint instead of the single-entity endpoint when you need to verify more than one entity in a single operation — it amortizes the per-call cost across up to 200 items and returns results in one settlement. Prefer it in pre-action workflows where an agent must clear multiple IBANs, phones, vehicles, or other entities before proceeding.

## Known failure modes

- 400 error for empty batch or batch exceeding 200 items (not charged)
- 400 error for malformed individual items returns per-position error without failing the whole batch
- Invalid kind/country/birth_year filters may yield no results rather than an error
- Network timeout for very large batches near the 200-item cap
- Ambiguous entity names may return only weak matches

## 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

An array of per-item results corresponding to each submitted entity. Each result includes a verdict (pass/fail/weak), a hits array listing any matches found with provenance from official sources, and for malformed items an error object with a code. The include_weak flag determines whether weak matches affect the overall verdict for the whole batch.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "items",
  "include_weak"
 ],
 "properties": {
  "items": {
   "type": "array",
   "description": "Array of names screened in one settlement. Its length is priced per unit (base + N x unit), capped at 200; an empty or oversized batch is a 400, never charged. Each item takes a 'name' (2 to 200 characters) plus the same optional filters as the single endpoint - 'kind', 'country', 'birth_year'. A malformed item yields {error, code} at its position without failing the batch"
  },
  "include_weak": {
   "type": "boolean",
   "description": "Whether weak matches count towards the verdict, for the WHOLE batch; default false. It is a caller policy (what you count as a signal), not a property of one name. Weak matches are returned in hits[] either way"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-batch-entity-screening-f142ec64/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)