Skip to main content
POST
Batch screening
Screens up to 50 subjects in one call — crypto addresses, emails, websites, government IDs, countries and names, mixed freely. Each item is screened exactly as its own endpoint would screen it, and its result has that endpoint’s shape. Use it to re-screen a customer base on a schedule, to check every counterparty on an invoice run, or to screen everything known about one customer at once.
object[]
required
1–50 subjects. Each item:
string
Comma-separated list slugs for every item (default: all enabled lists).
Example request

Response

results holds one entry per item, in request order, with its index, your ref, type, value and a status:
  • ok — result is exactly what the item’s own endpoint returns: the screening envelope, or for name items the scored /screen/name envelope.
  • error — the item’s input was rejected (an unknown list slug, a malformed birth date, an unknown country…); error says why, and the item is not metered.
Top-level screened and errors count the two, and flagged / sanctioned are true when any screened item is.
Example response

Quota and billing

Each screened item is one request against your monthly quota; rejected items cost nothing. Before screening, the batch is checked against the requests remaining in your period: if they cannot cover every item, the whole batch is refused with 429 (code: "QUOTA_EXCEEDED", the detail saying how many it needed and how many remain) and nothing is screened or charged — send a smaller batch or upgrade. Every screened item is written to your organization’s audit trail like a single call. Batch screening requires an API token; it is not available with x402 pay-per-request, and PEP screening, VPN detection and geolocation are not batchable.