Built for autonomous agents.

Three ways for an agent to use IBANforge

Install in Claude Desktop, Cursor or Cline

11 tools on the remote HTTP server, 13 in the installed npm package. The two additional tools analyse a creditor file and track its report.

https://api.ibanforge.com/mcp

Does your client require a local process? Use this configuration.

{
  "mcpServers": {
    "ibanforge": {
      "command": "npx",
      "args": ["-y", "ibanforge-mcp"]
    }
  }
}

11 remote tools · 13 with npm

25 free calls a month — no e-mail, no signup

POST an empty body and receive a key. The key is shown once. Add it as Authorization: Bearer ifk_… on every call. To reach 200 a month, call /v1/keys/claim with an address you can read.

curl -X POST https://api.ibanforge.com/v1/keys/generate

# → { "api_key": "ifk_...", "monthly_limit": 25 }

When the monthly quota is exhausted, the API automatically falls back to x402: the same agent can keep calling, paying $0.005 per request, with no extra setup until the quota resets on the 1st of the next month.

Integrate with an SDK

Store the key obtained above in the server-side IBANFORGE_API_KEY environment variable for Python, or replace ifk_... in the TypeScript configuration. SDKs expose quota and payment errors; they do not automatically sign payments.

# pip install ibanforge
import os
from ibanforge import IBANforge

with IBANforge(api_key=os.environ["IBANFORGE_API_KEY"]) as client:
    out = client.validate_iban("DE89370400440532013000")
    print(out["valid"])
    print(out.get("bank_code_check"))
    print(out.get("bic"))

// npm install @ibanforge/sdk
import { IBANforge } from "@ibanforge/sdk";

const ibanforge = new IBANforge({ apiKey: "ifk_..." });

const out = await ibanforge.validateIban("CH1000230000000012345");

console.log(out.country?.code);          // CH
console.log(out.bic?.bank_name);         // UBS Switzerland AG
console.log(out.sepa?.member);           // true

Pay-per-call in USDC on Base

No quota, no signup, no email. Your agent's wallet signs an authorization, the Coinbase CDP facilitator settles the payment, and the API returns the response. ~1-2 second round-trip.

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/fetch";
import { ExactEvmScheme, toClientEvmSigner } from "@x402/evm";
import { createPublicClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { base } from "viem/chains";

const account = privateKeyToAccount(process.env.WALLET_KEY as `0x${string}`);
const publicClient = createPublicClient({ chain: base, transport: http() });
const evmSigner = toClientEvmSigner(account, publicClient);

const client = new x402Client()
  .register("eip155:8453", new ExactEvmScheme(evmSigner));

const paid = wrapFetchWithPayment(fetch, client);

const r = await paid("https://api.ibanforge.com/v1/iban/validate", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ iban: "CH1000230000000012345" }),
});
// pays $0.005 USDC autonomously, returns 200 with the response

Pricing is advertised on every paid endpoint via 402 responses with full payment requirements (network: base, asset: USDC, payTo, amount, schema). Listed on Coinbase Bazaar discovery for autonomous discovery.

5 paid endpoints, all available via MCP + x402 + API key

Same data, three integration paths.

Machine-readable metadata

Standard discovery endpoints for agents that crawl the web for usable APIs:

• api.ibanforge.com/.well-known/x402
• api.ibanforge.com/.well-known/agents.json
• api.ibanforge.com/.well-known/mcp.json
• api.ibanforge.com/openapi.json
• api.ibanforge.com/llms.txt