# Invoket IBAN Batch Sanctions Screening

> Invoket IBAN Batch Sanctions 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-16).

Screens a batch of IBANs against OFAC, EU, and UN sanctions lists and returns AML risk assessments with bank details per IBAN

## Facts

- Endpoint: POST https://api.invoket.com/iban/screen/batch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-iban-batch-sanctions-screening-4322aa46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0cMTQSSeck3kClX0CjiBJ

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-iban-batch-sanctions-screening-4322aa46 -d '<json body>'
```

Example prompt: Can you screen these IBANs for sanctions and AML risk: DE89370400440532013000 and AE070331234567890123456 — I need to know if either is flagged on OFAC, EU, or UN lists and what the overall risk level is before we process a payment?

## When to prefer this

Choose this endpoint when you need to screen multiple IBANs in a single call against OFAC, EU, and UN sanctions databases without setting up an account or API key — ideal for autonomous agents, one-off compliance checks, or workflows that process international payment counterparties. Prefer this over single-IBAN endpoints when you have 2+ IBANs to check and want to minimize round trips and per-call costs.

## Known failure modes

- Invalid IBAN format returns validation error per entry
- Payment not settled (x402) causes 402 Payment Required with no results
- Empty batch array returns count 0 with empty results
- IBAN from unsupported region may return coverage: structure_only with no bank details
- Stale sanctions data if snapshot is outdated — check provenance.freshness.as_of
- Network timeout on large batches

## How this service works

Before onboarding or a payment run: screen up to 500 IBANs in one call for sanctioned banks (BIC) and high-risk jurisdictions against the official OFAC, EU, UN and FATF lists, for KYB/AML compliance

## Output

Returns per-IBAN results including validity, country, BIC, bank name, coverage level (full or structure_only), sanctions hits with type and source, overall risk rating (clear or high), jurisdiction risk level and matched AML lists, and whether the bank itself is sanctioned. Also includes provenance metadata: which sanctions datasets were checked (OFAC, EU, UN), snapshot date, and fetch timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "ibans"
 ],
 "properties": {
  "ibans": {
   "type": "array"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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