# Invoket IBAN Batch Resolver

> Invoket IBAN Batch Resolver 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-15).

Validates and resolves a batch of IBANs to bank details (BIC, bank name, country, reachability) in a single call

## Facts

- Endpoint: POST https://api.invoket.com/iban/resolve/batch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-iban-batch-resolver-ed9f9e5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JXMUHkvyJczQ6R61XwM3i

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-resolver-ed9f9e5b -d '<json body>'
```

Example prompt: Can you validate these two IBANs for me — DE89370400440532013000 and FR7630006000011234567890189 — and tell me which ones are valid and what banks they belong to?

## When to prefer this

Use this endpoint when you need to validate or enrich multiple IBANs in a single API call without an account or API key, paying per-call in USDC via x402. Ideal for autonomous agents processing payment data, verifying beneficiary accounts before transfers, or enriching financial records with bank metadata at low volume without subscription overhead.

## Known failure modes

- Invalid IBAN format causes per-entry invalid flag with issue code rather than endpoint error
- Payment not settled (402) if USDC payment header missing or insufficient
- Batch too large may result in request rejection
- Unknown IBAN prefix may return partial coverage or no bank data
- Stale registry data if bank has recently changed BIC

## How this service works

Before a payment run: validate up to 500 IBANs in one call, resolve bank and BIC from national bank registries, and check SEPA reachability per scheme (SCT, SCT Inst, SDD Core/B2B) against the EPC register

## Output

A JSON object containing per-IBAN results: validity flag, country code, BIC, bank name, bank code, reachability status, and coverage level. Invalid IBANs include an issue code (e.g. BAD_CHECKSUM). Provenance metadata includes data source (national-bank-registries) and snapshot freshness date.

## 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-resolver-ed9f9e5b/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)