IBANforge

{
  "protocolVersion": "1.0",
  "supportedInterfaces": [
    {
      "url": "https://api.ibanforge.com",
      "protocolBinding": "HTTP+JSON",
      "protocolVersion": "1.0"
    }
  ],
  "name": "IBANforge",
  "description": "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.",
  "url": "https://api.ibanforge.com",
  "preferredTransport": "HTTP+JSON",
  "provider": {
    "organization": "IBANforge",
    "url": "https://ibanforge.com"
  },
  "version": "1.9.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 a free key with no e-mail: POST /v1/keys/generate with no body at all (25 req/month), POST /v1/keys/claim lifts it to 200 a 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) 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"
      ],
      "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: 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"
      ]
    },
    {
      "id": "check_compliance",
      "name": "Compliance Check",
      "description": "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"
      ]
    },
    {
      "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 (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"
      ],
      "examples": [
        "Does this QR-bill still carry a combined (type K) creditor address that the bank may refuse at payment?"
      ]
    }
  ]
}