
01 · READ AN IBAN
Every piece of information finds its place.
Format, bank, BIC: distinct data, with its provenance and its limits.
Back to the checkerFROM IBAN TO USEFUL INFORMATION
IBANforge is the lens that reveals the format, bank and BIC.

One incoming stream. Three distinct pieces of information.
Run a check: the rays lead to the resulting data.
This result confirms neither account existence, nor account ownership, nor payment success. Enrichment depends on available sources.
Open the full playground ↗GLEIF · SIX BankMaster · SwiftCodes (MIT) · Bundesbank · EBA STEP2 · NBP · Bank of England (List of Banks, 2026-08)
Refreshed monthly · last refresh September 1, 2026OFAC · EU · UN + FATF
Bank-level (BIC8) screeningMade in Switzerland
Swiss clearing data straight from SIXIBANs never stored · self-deleting telemetry
Erased 30 days after you leave — DPA clause 4.7ONE LIGHT, THREE USES
Read an IBAN, examine a file, feed your tools.

01 · READ AN IBAN
Format, bank, BIC: distinct data, with its provenance and its limits.
Back to the checker
02 · EXAMINE A FILE
Bank details in a file become structured results you can read and use.
Explore file audits
03 · CONNECT YOUR TOOLS
APIs, agents and automations can reuse a structured response in their own workflows.
Read the documentationEvery BC-Nummer from the SIX BankMaster with its SIC, euroSIC and CHF instant rail participation, the QR-IID and the institution type. The deepest Swiss clearing data of any public API.
Native Model Context Protocol server (stdio + HTTP). Claude, Cursor and any MCP agent install in one line: npx -y ibanforge-mcp.
ISO 13616 mod-97 and BBAN parsing across 89 countries, backed by 121,773 BIC entries from GLEIF, SwiftCodes, the Bundesbank, SIX, the NBP and EBA STEP2.
Detect virtual IBANs and EMIs (Wise, Revolut, N26, Mercury…) — a real compliance signal a mod-97 check can never give you.
Bank-BIC sanctions screening (OFAC, EU, UN) + FATF + SEPA + VoP reachability, distilled into a 0-100 risk score.
Autonomous agents pay per request in USDC via x402, no account, no checkout. Humans keep the free key or card credits.
D-54days before 14 November 2026
POST /v1/address/check says for free whether an address passes the Swiss, HVPS+ or Fedwire rules, naming the document; the file audit takes a whole workbook.
Upload a CSV or Excel file and preview the findings for free. The annotated workbook costs $149 for up to 5,000 rows, or $349 for up to 20,000 rows.
Start free with 25 requests a month and no e-mail. Claim the same key for 200 a month. Pay as you grow — by card or in USDC.
Free: 25 requests a month with no e-mail, 200 a month once claimed · Pro: $29 a month for 10,000 requests · credit packs from $4 · vendor licence from $149 a month · file audit $149. See pricing
Every package below exists and installs today. What is not published yet says so.
npm install @ibanforge/sdkpip install ibanforgecom.ibanforge:ibanforge-sdkdotnet add package IBANforge.Sdknpx -y ibanforge-mcpnpm install n8n-nodes-ibanforgeibanforge_bank_autofill=IBAN_CONTROLE(A2)ibanforge.postman_collection.jsonThis page speaks robot too — every claim above is machine-readable, and every endpoint is payable without a human in the loop.
MCP tools, no signup. Claude, Cursor and any MCP agent install in one line:
npx -y ibanforge-mcp
Autonomous agents pay per request in USDC — no account, no checkout, settlement on-chain.
402 → pay → 200 OK
OpenAPI spec, structured data and a plain-text summary built for crawlers and agents.
“The most artifact-complete submission the inbox has had.”
Kin Lane rebuilt IBANforge's API Evangelist profile from fetched artifacts in August 2026 — and found our x402 support to be the first across the 3,767 MCP servers in his catalog.
Start with a free key — 25 requests a month, no e-mail and no card. Claiming the same key takes it to 200 a month. Scale with prepaid credits by card, or pay per call in USDC.