# Vextorium IBAN Validator

> Vextorium IBAN Validator is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-15).

Validates an IBAN using ISO 13616 mod-97 check, per-country length rules, SEPA membership, and for Spanish IBANs also the national CCC check digits and bank name lookup — computed locally, never stored.

## Facts

- Endpoint: POST https://api.vextorium.com/v1/iban-validate?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-iban-validator-7f553245
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WVzUSZEOLrWH2Ff60oDfD

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 vextorium-iban-validator-7f553245 -d '<json body>'
```

Example prompt: Can you check whether ES91 2100 0418 4502 0005 1332 is a valid IBAN, and tell me if it's in the SEPA zone and which bank issued it?

## When to prefer this

Choose this endpoint when you need a privacy-preserving, locally-computed IBAN validation that does not transmit or store the account number externally. It is especially useful for Spanish IBANs where you need the additional CCC national check digit validation and the resolved bank name. Prefer it over generic regex checks when full ISO 13616 compliance and SEPA membership status are required in a single low-latency call.

## Known failure modes

- Malformed or unsupported country prefix returns valid=false with error details
- Incorrect mod-97 check digit causes valid=false
- Wrong length for the given country returns an error in the errors array
- Entirely missing or empty IBAN field returns an input validation error
- Non-string or null IBAN input may return a 400-level error

## How this service works

IBAN validation (ISO 13616 mod-97 and per-country length, SEPA membership; for Spain also the national CCC check digits and bank name). Computed locally, IBAN is not stored.

## Output

A JSON object containing: the normalized IBAN (partially masked), a boolean 'valid' flag, the 2-letter country code, a boolean 'sepa_zone' indicating SEPA membership, the bank/entity name (for Spain), and an array of 'errors' describing any validation failures (e.g. wrong length, bad check digits, unknown country prefix).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "iban": {
   "type": "string",
   "description": "IBAN, spaces allowed"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "iban": "ES91 **** 1332",
  "valid": true,
  "entity": "CaixaBank",
  "errors": [],
  "country": "ES",
  "sepa_zone": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-iban-validator-7f553245/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)