# Invoket IBAN Batch Repair

> Invoket IBAN Batch Repair 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 repairs a batch of malformed or ambiguous IBANs, returning corrected candidates with bank details and reachability status

## Facts

- Endpoint: POST https://api.invoket.com/iban/repair/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-repair-e118c62b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lyR3_iSEvhTsiiV2cpuAK

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-repair-e118c62b -d '<json body>'
```

Example prompt: I have a list of IBANs from our payment file and some look malformed or have typos — can you run them through batch IBAN repair and tell me which ones are fixed, which are ambiguous, and give me the corrected IBAN along with the bank name and BIC for each?

## When to prefer this

Use this endpoint when you have multiple IBANs that may be malformed, contain typos, or are of uncertain validity and you need bulk repair with enriched bank metadata (BIC, name, reachability) in one call. Prefer this over single-IBAN validation when processing payment files, onboarding data, or reconciling bank account lists at scale. Ideal for autonomous agents that need no account or API key and can settle per-call in USDC via x402.

## Known failure modes

- Input IBANs are so heavily malformed that no plausible candidate can be resolved — returns ambiguous=true with empty candidates
- Unsupported country prefix — IBAN country not in coverage database
- Batch too large — payload size limit exceeded returns 4xx error
- Payment not settled — x402 stablecoin payment fails, request rejected with 402
- Network timeout for large batches

## How this service works

Before a payment run over OCR or invoice data: fix up to 500 broken or garbled IBANs in one call — recompute check digits, recover unreadable characters and rank candidates by known bank from national bank registries

## Output

Returns a count and array of results per input IBAN, each indicating whether it was already valid, successfully repaired, or ambiguous, along with a list of candidate IBANs each containing the corrected IBAN string, a validity flag, the bank's BIC and name, country, bank code, coverage level, and reachability status. Also includes provenance metadata with source and freshness 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-repair-e118c62b/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)