Skip to main content
Glama

Lookup BIC/SWIFT

lookup_bic
Read-onlyIdempotent

Resolve a BIC / SWIFT code into the underlying bank: name, country, city, LEI, and registered head-office address (where available). USE WHEN: the user already has a BIC/SWIFT (8 or 11 chars, alphanumeric, e.g., "UBSWCHZH80A", "DEUTDEFF") and asks which bank it belongs to, where the bank is, or its LEI for compliance/regulatory matching. DO NOT USE for IBAN inputs — call validate_iban instead, it resolves the BIC for you. BACKED BY: 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. 39,000+ of the rows carry an LEI from GLEIF. SOURCE: source names the dataset of this row and source_name spells it out; source_as_of is present only when that dataset is a copy frozen at that month (the public copy of the SWIFT directory, frozen in January 2018). listed_in_current_source says whether this BIC8 still appears in a list refreshed this cycle (GLEIF, a national register, the EPC scheme registers, the EBA STEP2 and NBP lists): true when one of them carries it, null when it was not found in what could be read in full. It never answers false today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, which can drop a BIC they carry, so an absence is not proven. It does not prove the bank still exists under this name. COST: $0.003 per call (free with no key on this transport: 25 units a week per source address, one per call and one per IBAN in batch_validate_iban, reset on Monday 00:00 UTC. Or an ifk_ key with no e-mail at all: POST https://api.ibanforge.com/v1/keys/generate with no body for 25 calls/month, on the REST API or on this transport, and POST /v1/keys/claim lifts that same key to 200 a month. Send the key here as Authorization: Bearer ifk_… (or X-API-Key) and each call counts against it exactly as on the REST API).

Input Schema

NameRequiredDescriptionDefault
bicYesBIC/SWIFT code (8 or 11 chars)

Output Schema

NameRequiredDescriptionDefault
bicYesEcho of the input, normalized to uppercase.
leiNoLegal Entity Identifier (ISO 17442) if available.
bic8No8-char form (institution-level).
cityNoNull, never an empty string, when the source leaves the town blank.
noteNoPresent only when found is false and the part of the directory served from a private file (EBA STEP2, NBP and OeNB records) is not loaded on this deployment: the absence was not looked up there.
bic11No11-char form including branch.
errorNo
foundNoTrue only when the row names an institution: a record is complete or not found.
validNoSet when the BIC failed format validation.
sourceNoCode of the dataset this row comes from.
addressNoRegistered head-office address of the legal entity, from the same directory row as GET /v1/bic/:code and the bic.address of validate_iban, with its source and as_of (the date the entity last filed it, usually older than the bank name beside it). Null when the source publishes no address for this BIC. It is the seat of the legal entity, not the branch, so address.city may differ from city.
countryNoSame shape as REST GET /v1/bic/:code. name is the row's country name, then the ISO name, and falls back to the country code only when neither exists.
lei_statusNo
branch_codeNo
branch_infoNo
institutionNoBank legal name.
is_test_bicNo
source_nameNosource names the dataset of this row and source_name spells it out; source_as_of is present only when that dataset is a copy frozen at that month. listed_in_current_source says whether this BIC8 still appears in a list refreshed this cycle (GLEIF, a national register, the EPC scheme registers, the EBA STEP2 and NBP lists): true when one of them carries it, null when it was not found in what could be read in full. It never answers false today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, which can drop a BIC they carry, so an absence is not proven. It does not prove the bank still exists under this name.
country_codeNoDEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.code.
country_nameNoDEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which is never null: the row's country name, else the ISO name, else the code.
source_as_ofNoYear-month the source DATA is from, present only for a frozen copy.
valid_formatNo
address_availableNoTrue when address is not null.
listed_in_current_sourceNoWhether this BIC8 still appears in a list refreshed this cycle: GLEIF, the directory sources that carry no vintage, a national register, the EPC scheme registers. true when one of them carries it; null when it was not found in what could be read in full (never false by default). false is reserved for an index built from every list read in full, which is not the case today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, so this field answers true or null. It does NOT prove the bank still exists under this name: a clearing list can keep the name of a bank that was absorbed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / address
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "as_of": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "city": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "country": {
      +          "type": "string"
      +        },
      +        "language": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "post_code": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "region": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "romanization": {
      +          "enum": [
      +            "original_latin",
      +            "gleif_english",
      +            "unavailable"
      +          ],
      +          "type": "string"
      +        },
      +        "romanized": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "source": {
      +          "type": "string"
      +        },
      +        "street": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "type": {
      +          "const": "registered",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "type",
      +        "street",
      +        "post_code",
      +        "region",
      +        "city",
      +        "country",
      +        "romanized",
      +        "romanization",
      +        "source",
      +        "language",
      +        "as_of"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Registered head-office address of the legal entity, from the same directory row as GET /v1/bic/:code and the bic.address of validate_iban, with its source and as_of (the date the entity last filed it, usually older than the bank name beside it). Null when the source publishes no address for this BIC. It is the seat of the legal entity, not the branch, so address.city may differ from city."
      +}
    • addedOutput schema / properties / address_available
      Added value: +{
      +  "description": "True when address is not null.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "Present only when found is false and the part of the directory served from a private file (EBA STEP2, NBP and OeNB records) is not loaded on this deployment: the absence was not looked up there.",
      +  "type": "string"
      +}
  3. Changed8 schema fields changed
    • addedOutput schema / properties / city / description
      Added value: +"Null, never an empty string, when the source leaves the town blank."
    • changedOutput schema / properties / country / description
      Previous value: -"Same shape as REST GET /v1/bic/:code. name falls back to the country code when the row carries no name."New value: +"Same shape as REST GET /v1/bic/:code. name is the row's country name, then the ISO name, and falls back to the country code only when neither exists."
    • changedOutput schema / properties / country_name / description
      Previous value: -"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which falls back to the code rather than to null."New value: +"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which is never null: the row's country name, else the ISO name, else the code."
    • addedOutput schema / properties / found / description
      Added value: +"True only when the row names an institution: a record is complete or not found."
    • addedOutput schema / properties / listed_in_current_source
      Added value: +{
      +  "description": "Whether this BIC8 still appears in a list refreshed this cycle: GLEIF, the directory sources that carry no vintage, a national register, the EPC scheme registers. true when one of them carries it; null when it was not found in what could be read in full (never false by default). false is reserved for an index built from every list read in full, which is not the case today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, so this field answers true or null. It does NOT prove the bank still exists under this name: a clearing list can keep the name of a bank that was absorbed.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / source
      Added value: +{
      +  "description": "Code of the dataset this row comes from.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / source_as_of
      Added value: +{
      +  "description": "Year-month the source DATA is from, present only for a frozen copy.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / source_name
      Added value: +{
      +  "description": "source names the dataset of this row and source_name spells it out; source_as_of is present only when that dataset is a copy frozen at that month. listed_in_current_source says whether this BIC8 still appears in a list refreshed this cycle (GLEIF, a national register, the EPC scheme registers, the EBA STEP2 and NBP lists): true when one of them carries it, null when it was not found in what could be read in full. It never answers false today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, which can drop a BIC they carry, so an absence is not proven. It does not prove the bank still exists under this name.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  4. Changed12 schema fields changed
    • removedOutput schema / properties / branch_info / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / branch_info / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / city / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / city / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / country_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / country_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / institution / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / institution / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / lei / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / lei / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / lei_status / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / lei_status / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  5. Changed3 schema fields changed
    • addedOutput schema / properties / country
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Same shape as REST GET /v1/bic/:code. name falls back to the country code when the row carries no name.",
      +  "properties": {
      +    "code": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "name"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / country_code / description
      Added value: +"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.code."
    • addedOutput schema / properties / country_name / description
      Added value: +"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which falls back to the code rather than to null."
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "bic": {
      +      "description": "Echo of the input, normalized to uppercase.",
      +      "type": "string"
      +    },
      +    "bic11": {
      +      "description": "11-char form including branch.",
      +      "type": "string"
      +    },
      +    "bic8": {
      +      "description": "8-char form (institution-level).",
      +      "type": "string"
      +    },
      +    "branch_code": {
      +      "type": "string"
      +    },
      +    "branch_info": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "city": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "country_code": {
      +      "type": "string"
      +    },
      +    "country_name": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "found": {
      +      "type": "boolean"
      +    },
      +    "institution": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Bank legal name."
      +    },
      +    "is_test_bic": {
      +      "type": "boolean"
      +    },
      +    "lei": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Legal Entity Identifier (ISO 17442) if available."
      +    },
      +    "lei_status": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "valid": {
      +      "description": "Set when the BIC failed format validation.",
      +      "type": "boolean"
      +    },
      +    "valid_format": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "bic"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered; the description goes well beyond by disclosing coverage (121k rows, 39k with LEI), staleness (SWIFT directory copy frozen January 2018 comprising ~two thirds of rows), and the important caveat that listed_in_current_source is never false today because absences are unproven. That caveat is exactly the kind of trust signal an agent needs. It loses a point only because this disclosure is entangled with a long pricing/API-key aside that is billing, not tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Use/do-not-use guidance is front-loaded, which is good, but the back half is bloated: a long paragraph on source/source_as_of/listed_in_current_source semantics that largely restates output-schema territory, plus a lengthy parenthetical on free-tier quotas and generating an ifk_ key via REST endpoints. The $0.003 cost line earns its place; the multi-sentence key-provisioning detour does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with an output schema and full annotation coverage, this is more than adequate: input format, data provenance, provenance caveats, and cost are all present. The only shortfall is allocation rather than omission — field-level return semantics for source/list flags are elaborated in the description where the output schema could carry them, while the billing detail crowds out nothing useful but adds noise.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented as an 8-or-11-char code. The description adds concrete format guidance and worked examples ("UBSWCHZH80A", "DEUTDEFF") plus the alphanumeric constraint, which marginally exceeds the schema but does not discuss normalization or what happens to malformed input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Resolve a BIC / SWIFT code into the underlying bank") and enumerates the returned fields (name, country, city, LEI, head-office address). It also explicitly distinguishes itself from the sibling that handles a related but different input (validate_iban), so an agent can pick correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contains explicit USE WHEN conditions (user already holds an 8/11-char BIC and asks which bank it belongs to, where it is, or its LEI) and an explicit DO NOT USE clause routing IBAN inputs to validate_iban. Both the positive and negative case are named, with the alternative tool identified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.