# Agent402 UK IBAN Full Validator

> Agent402 UK IBAN Full Validator is a paid API for AI agents from agent402.co.uk, paid per call via x402, $0.001/call, status down (last checked 2026-10-12).

Validates an IBAN string via ISO-13616 country length table, mod-97 checksum, and BBAN structural parse, returning per-check breakdown.

## Facts

- Endpoint: POST https://agent402.co.uk/v1/validate/iban-full?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent402-uk-iban-full-validator-91c19bab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GRU4eYPG8E63kJSzkv_T1

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 agent402-uk-iban-full-validator-91c19bab -d '<json body>'
```

Example prompt: Can you validate this IBAN for me — DE89370400440532013000 — and tell me whether the checksum and length are correct for Germany?

## When to prefer this

Use this endpoint when you need a rigorous, per-component IBAN breakdown (country recognition, length table check, and mod-97 checksum) rather than a simple regex pass/fail. Prefer it over generic format validators when you need to know exactly which part of the IBAN is invalid, or when preparing for SEPA payment submission and needing auditability. It does not check account existence, so combine with a bank directory lookup if live account verification is required.

## Known failure modes

- Malformed or empty IBAN string returns validation failure with per-field breakdown
- Unrecognized country code prefix causes length_ok and potentially checksum_ok to fail
- IBAN with correct structure but wrong checksum returns valid:false with checksum_ok:false
- Service does not verify real-world account existence — a structurally valid IBAN may not correspond to a live account
- Network or payment failure (402 not settled) results in no response

## How this service works

Don't burn tokens on deterministic work. Go/no-go jobs first: payout preflight, text firewall (PII/secrets), budget check — then rails, calendars, finmath. x402 USDC on Base. UK + global. agent402.co.uk — not agent402.tools. $0.001–$0.002 USDC on Base. No API keys.

## Output

Returns a JSON object with: `valid` (boolean overall result), `country` (2-letter ISO country code parsed from the IBAN), `length_ok` (whether the IBAN length matches the ISO-13616 table for that country), `checksum_ok` (whether the mod-97 checksum passes), and `expected_length` (the correct IBAN length for that country). Does NOT verify whether the account actually exists at a bank.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "valid": true,
  "country": "DE",
  "length_ok": true,
  "checksum_ok": true,
  "expected_length": 22
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent402-uk-iban-full-validator-91c19bab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.co.uk](https://www.zero.xyz/host/agent402.co.uk/llms.txt)