canonical: https://jentic.com/apis/generaterandomiban.com/generaterandomiban

# Generate Random IBAN API

The Generate Random IBAN API generates and validates structurally valid IBANs for 91 countries, following ISO 13616 and the MOD-97 checksum with correct national check digits where a country defines them. An optional realistic mode builds IBANs from real bank codes and digits, and the API lists every supported country and its IBAN format. Generated IBANs always pass checksum validation but were never issued by a bank, so they are for testing, QA, and education and never for payments. Validation accepts an IBAN in the URL or in a JSON body and reports whether it is structurally correct.

## For AI agents

Generate structurally valid IBANs for 91 countries and validate any IBAN against ISO 13616 and the MOD-97 checksum. Generated IBANs are for testing and QA only, and the API is secured with an API key in the X-API-Key header.

## Scope

Does not issue real bank accounts, process payments, or confirm account ownership. Use for generating and validating test IBANs for QA and education only.

## Capabilities

- Generate structurally valid IBANs for 91 countries with correct national check digits
- Generate IBANs in a realistic mode built from real bank codes and digits
- Validate an IBAN against ISO 13616 and the MOD-97 checksum
- List supported countries and their IBAN formats
- Generate one or many test IBANs from a path parameter or a JSON body

## Use cases

### AI Agent Test IBAN Generation via Jentic

An AI agent reaches Generate Random IBAN through Jentic to produce safe test data without wiring the API key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the key injected at run time. Because the IBANs pass checksum validation but were never issued by a bank, the agent can seed tests without touching a real account.

Example prompt: Search Jentic for 'generate a valid IBAN for a country', load the GET `/generate/{country}` schema, and execute it with the key injected at run time

### Test Data Generation for QA

A QA or test suite needs valid-looking IBANs that will not touch a real bank. Generate Random IBAN produces one or many IBANs for a country that pass the MOD-97 checksum, with an optional realistic mode built from real bank codes. The agent controls the country, count, and mode so a fixture can cover many banking locales.

Example prompt: Call GET `/generate/{country}` to produce test IBANs for a country, or POST /generate with a JSON body to control the count and mode

### IBAN Validation

An application checks whether an IBAN a user entered is structurally correct before it stores or submits it. Generate Random IBAN validates the IBAN against ISO 13616 and the MOD-97 checksum, taking it from the URL or a JSON body. The result tells the agent whether the structure and check digits are valid, though it does not confirm the account exists at a bank.

Example prompt: Call GET `/validate/{iban}` to check an IBAN in the URL, or POST /validate to validate one from a JSON body

### Country Format Lookup

A form or a validator needs to know the IBAN layout for a country before generating or checking one. Generate Random IBAN lists every supported country and returns a single country's IBAN format, including its length and structure. The agent can use the format to label fields or to decide which countries a workflow supports.

Example prompt: Call GET /countries to list supported countries, then GET `/countries/{code}` for one country's IBAN format

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/countries` | List supported countries and their IBAN formats |
| GET | `/countries/{code}` | A single country's IBAN format |
| GET | `/generate/{country}` | Generate random IBANs for a country |
| POST | `/generate` | Generate IBANs from a JSON body |
| GET | `/validate/{iban}` | Validate an IBAN passed in the URL |
| POST | `/validate` | Validate an IBAN from a JSON body |

## Key resources

- **Generation** — Generate test IBANs by path or JSON body via `/generate/{country}` and /generate
- **Validation** — Validate IBANs by URL or JSON body via `/validate/{iban}` and /validate
- **Countries** — List supported countries and read one country's IBAN format via /countries and `/countries/{code}`

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/generaterandomiban.com/generaterandomiban/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Generate Random IBAN by hand means requesting a key by email, sending it in the X-API-Key header, and choosing between the path and JSON-body forms of generate and validate yourself. Through Jentic you install once, import Generate Random IBAN from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The API carries the country and IBAN in the URL path, so scoping is by operation: a rule can limit your agent to the generate and validate operations and nothing else. You choose which operations it may call, so the country-format reads can be allowed while generation is withheld, or the reverse.
- **Credential handling:** Your Generate Random IBAN key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate a valid IBAN for a country' or 'validate an IBAN', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Abstract API** — A suite of validation APIs including IBAN, VAT, email, and phone checks
- **Mockaroo** — Generate realistic mock datasets across many field types
- **Random User Generator** — Generate random user profiles for testing and prototyping

## FAQ

### What authentication does the Generate Random IBAN API use?

The Generate Random IBAN API authenticates with an API key in the X-API-Key header, requested by email, per its OpenAPI spec; an Authorization: Bearer token carrying the same key also works. The service index and the OpenAPI document are public endpoints that need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

### What are the rate limits for the Generate Random IBAN API?

The OpenAPI spec does not specify request rate limits. Keys are issued on request, so any limit depends on the arrangement with the provider. See https://generaterandomiban.com/en/apis for current details.

### Can I validate an IBAN with the Generate Random IBAN API?

Yes. GET `/validate/{iban}` checks an IBAN passed in the URL against ISO 13616 and the MOD-97 checksum, and POST /validate validates one from a JSON body. Generated IBANs always pass checksum validation but are not real accounts, so they are suitable for testing only.

### Is there a Generate Random IBAN MCP server?

You don't need an MCP server to give your agent Generate Random IBAN. Jentic connects it directly from the API Directory: import it and your agent calls the generate and validate operations on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context.

### How do I generate a test IBAN with the Generate Random IBAN API through Jentic?

Search Jentic for 'generate a valid IBAN for a country', and it returns the generate operation with its input schema. Load it and execute GET `/generate/{country}` with the key injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Generate Random IBAN API?

Yes. Write a rule that allows only the operations a task needs, for example generating IBANs for one set of countries or validating IBANs, so the agent does nothing else with the key. Because every call runs through your own instance, each one is logged for you to review.