Home / Businesses / BIC (SWIFT Code) Form Check
BIC (SWIFT Code) Form Check
Check the form of a BIC (SWIFT code, ISO 9362): institution, country (ISO 3166), location, branch, 8 and 11 character forms and test flags, with a signed record; does not say the bank exists.
Testing
- What it does
- Check the form of a BIC (SWIFT code, ISO 9362): institution, country (ISO 3166), location, branch, 8 and 11 character forms and test flags, with a signed record; does not say the bank exists.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
swift_bic_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
BIC (SWIFT Code) Form Check is for agents that set up vendor payments or clean a payee list and must catch a mistyped BIC before a wire is sent. Check the form of a BIC, the Business Identifier Code (ISO 9362, commonly called a SWIFT code) of a bank or business. Send bic (8 or 11 characters) or bics (up to 200). Get back whether the form is right, the parts (institution code, country, location, branch), whether the country code is an ISO 3166-1 country, the 8 and 11 character forms, and whether the location code marks a test BIC or one not connected to the SWIFT network. It does not say which bank it is or that the code is in use. It is one of the Payments department tools LLPRO builds for the work agents do across business software (Stripe, PayPal, QuickBooks, NetSuite, Xero). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that set up vendor payments or clean a payee list and must catch a mistyped BIC before a wire is sent.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, bics up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not say whether the BIC exists, which institution holds it, whether it is active, or whether a payment to it will arrive: only the official SWIFT BIC directory can say that. Does not check an account or IBAN (use an IBAN check for that). A form-valid code can still be unissued. It does not apply the finer SWIFT directory rules (a location code starting with 0 or 1, a branch starting with X other than XXX): such a code can pass here and be refused by SWIFT. The country list is the ISO 3166-1 list in the IANA tz database release 2026a; a code assigned later is not known. Not financial advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "swift_bic_check", "arguments": {"bic": "DEUTDEFF"}}}For agents
Tool swift_bic_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:345vc2x757c5ekfydiqb7rtrsa): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): 6Fjg+aP4UHy/D69JPTU3D3ob3kWTkXdIfMyu/mUB6UA=
For agents that search MCP registries for BIC check, SWIFT code, ISO 9362 tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: A BIC check is one step of paying a vendor. Tell LLPRO the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card