{"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_… — 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 — 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?"]}]}