Integration

IBANAPI integration

IBANAPI validates bank account identifiers and looks up the bank behind them. Check one IBAN (length, checksum, country structure and national account checksum) and get the bank name, BIC, address and SEPA scheme support, check up to 200 IBANs in one call, validate a BIC/SWIFT code or an Indian IFSC code against the bank registry, look up a country's currency, and read the remaining credit balance. Every validation consumes credits from the account balance. The JSONP form, the legacy duplicate paths and the service status routes are left out. Authentication is the API key from the IBANAPI dashboard, sent as the raw value of the Authorization header.

Connect IBANAPI How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in IBANAPI.Built from the 8 IBANAPI tools below, on the connection you add once.

What you can do with IBANAPI

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Validate, 3 operations

validate_ibanValidate ibanGETValidate one IBAN (length, checksum, country structure and, by default, the national account-number checksum) and resolve its bank: name, BIC, address and SEPA scheme support.
validate_ifsc_codeValidate ifsc codeGETValidate an 11-character Indian Financial System Code and resolve the bank and branch: name, address, district, state, MICR code and NEFT, RTGS, IMPS and UPI support.
validate_swift_codeValidate swift codeGETValidate a BIC/SWIFT code (characters, length, structure, country) and match it in the bank registry, returning the bank name, city, address and country.

Balance, 1 operation

get_balanceGet balanceGETRead the remaining basic-validation and bank-lookup credits of the API key, and the plan expiry date. Free to call, and still answers when the balance is exhausted.

Bulk validate, 1 operation

bulk_validate_ibansBulk validate ibansPOSTRun the full IBAN validation, bank lookup included, on up to 200 IBANs in one call. Returns one result per IBAN in the order sent. One credit per IBAN; the whole request is refused up front when the balance cannot cover the batch.

Bulk validate basic, 1 operation

bulk_validate_ibans_basicBulk validate ibans basicPOSTValidate up to 200 IBANs in one call (length, checksum and country structure), without the bank lookup. Returns one result per IBAN in the order sent, with basic credits deducted per IBAN.

Currency, 1 operation

get_country_currencyGet country currencyGETLook up a country by its two-letter ISO code and return its name, ISO alpha-2 and alpha-3 codes and currency code.

Validate basic, 1 operation

validate_iban_basicValidate iban basicGETValidate one IBAN's length, checksum and country structure without the bank lookup. Costs one basic credit only. Use validate_iban when the bank name or BIC is needed.

Use IBANAPI from Claude Code, Cursor or Codex

Connect IBANAPI in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its IBANAPI operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect IBANAPI

Create your workspace
Sign up free. Nothing to install.
Connect IBANAPI once
Add your IBANAPI connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.