IBANforge
ibanforge.com
· IBANforge
Pre-payout IBAN screening: validation, issuing-bank identification, sanctions (OFAC), Swiss clearing, SEPA + VoP reachability and risk scoring. 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.
ibanforge.com via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
D
Conformance score: 43/100
D-grade: significant issues, auth-gated, partially broken, or stale.
click to expand breakdown ▾
click to collapse breakdown ▴
agent-card.json changed within the last 7 days. We track these so downstream callers can react.
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Card history
1 snapshot Every change toagent-card.json
| Captured | Hash | |
|---|---|---|
| 2026-09-09 08:49:35 current | 90d18d3df7ef… |
view → |
Endpoints
| Agent card | https://ibanforge.com/.well-known/agent-card.json |
| Provider | https://ibanforge.com |
| Docs | https://ibanforge.com/docs |
Skills · 8 declared · mapped to canonical taxonomy
Structure (mod-97 + country BBAN), issuing bank with BIC, bank-code check against 6 national registers, EMI/vIBAN classification, SEPA + VoP reachability.
Up to 100 IBANs per call, one credit per IBAN, same enrichment as single validation.
Resolve a BIC against 121k+ entries (39k+ LEI-enriched via GLEIF): bank name, city, country, LEI, address where published.
Bank-level sanctions (OFAC + EU, BIC8 level — not name screening), FATF lists, SEPA/VoP reachability, 0-100 risk score.
BC-Nummer / IID against the SIX BankMaster (1,100+ entries): institution, seat address, SIC/euroSIC/instant participation, QR-IID semantics.
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 pairin…
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 …
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…
Health · last 1 probes
Cheaper or better alternatives per-skill
For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/ibanforge.com) [](https://agenstry.com/agents/ibanforge.com) [](https://agenstry.com/agents/ibanforge.com) [](https://agenstry.com/agents/ibanforge.com)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"protocolVersion": "1.0",
"supportedInterfaces": [
{
"url": "https://api.ibanforge.com",
"protocolBinding": "HTTP+JSON",
"protocolVersion": "1.0"
}
],
"name": "IBANforge",
"description": "Pre-payout IBAN screening: validation, issuing-bank identification, sanctions (OFAC), Swiss clearing, SEPA + VoP reachability and risk scoring. 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.",
"url": "https://api.ibanforge.com",
"preferredTransport": "HTTP+JSON",
"provider": {
"organization": "IBANforge",
"url": "https://ibanforge.com"
},
"version": "1.5.0",
"documentationUrl": "https://ibanforge.com/docs",
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false,
"stateTransitionHistory": false
},
"securitySchemes": {
"apiKey": {
"type": "apiKey",
"in": "header",
"name": "Authorization",
"description": "Bearer ifk_\u2026 \u2014 free key via POST /v1/keys/generate (200 req/month). x402/USDC accepted on paid routes without any key."
}
},
"defaultInputModes": [
"application/json"
],
"defaultOutputModes": [
"application/json"
],
"skills": [
{
"id": "validate_iban",
"name": "Validate IBAN",
"description": "Structure (mod-97 + country BBAN), issuing bank with BIC, bank-code check against 6 national registers, EMI/vIBAN classification, SEPA + VoP reachability.",
"tags": [
"iban",
"validation",
"sepa",
"vop",
"bank"
],
"examples": [
"Validate DE89370400440532013000 and tell me the issuing bank."
]
},
{
"id": "batch_validate_iban",
"name": "Batch Validate IBANs",
"description": "Up to 100 IBANs per call, one credit per IBAN, same enrichment as single validation.",
"tags": [
"iban",
"batch",
"payout"
]
},
{
"id": "lookup_bic",
"name": "Lookup BIC/SWIFT",
"description": "Resolve a BIC against 121k+ entries (39k+ LEI-enriched via GLEIF): bank name, city, country, LEI, address where published.",
"tags": [
"bic",
"swift",
"lei"
]
},
{
"id": "check_compliance",
"name": "Compliance Check",
"description": "Bank-level sanctions (OFAC + EU, BIC8 level \u2014 not name screening), FATF lists, SEPA/VoP reachability, 0-100 risk score.",
"tags": [
"sanctions",
"fatf",
"risk",
"compliance"
]
},
{
"id": "lookup_ch_clearing",
"name": "Swiss Clearing Lookup",
"description": "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"
]
},
{
"id": "validate_payment_reference",
"name": "Validate Payment Reference",
"description": "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"
],
"examples": [
"Is RF18539007547034 a valid creditor reference, and may it travel with this Swiss IBAN?"
]
},
{
"id": "check_postal_address",
"name": "Check ISO 20022 Postal Address",
"description": "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"
],
"examples": [
"Does this ISO 20022 address pass the Swiss SPS rules before I build the pain.001?"
]
},
{
"id": "check_swiss_qr_bill",
"name": "Check Swiss QR-bill Payload",
"description": "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 ahead of the SIX deadline of 14.11.2026, with a proposed structured form for combined addresses. Free.",
"tags": [
"swiss",
"qr-bill",
"qr-iban",
"iso-20022",
"postal-address",
"free"
],
"examples": [
"Is this QR-bill ready for 14 November 2026, or does its creditor address still use type K?"
]
}
]
}