IBAN Validation API vs Markbase

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783519324
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBAN Validation API vs Markbase: common questions

Which is more reliable, IBAN Validation API or Markbase?

On our scheduled checks, Markbase leads on measured uptime — IBAN Validation API at —% versus Markbase at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do IBAN Validation API and Markbase need an API key?

Neither needs a paid key — IBAN Validation API is callable with no signup, and Markbase is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IBAN Validation API and Markbase from the browser?

Yes — both IBAN Validation API and Markbase send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are IBAN Validation API and Markbase free for commercial use?

IBAN Validation API has unclear commercial terms, and Markbase has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.