IBANforge vs TaxID

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms694729
P95 · ms22461556
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tier200 requests/month with a free API key; /v1/demo and /health are keylessFree tier — key may be required
Rate limitUnpublished (200/month free quota)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBANforge vs TaxID: common questions

Which is more reliable, IBANforge or TaxID?

Both are neck-and-neck — IBANforge and TaxID each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, IBANforge or TaxID?

IBANforge has the lower median latency in our checks — IBANforge responds in 694 ms versus TaxID at 729 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do IBANforge and TaxID need an API key?

IBANforge needs no key, while TaxID requires a free API key. If you want to start calling without signup, reach for IBANforge first.

Can I call IBANforge and TaxID from the browser?

Only IBANforge is browser-friendly — it returns CORS headers over HTTPS. TaxID needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are IBANforge and TaxID free for commercial use?

IBANforge has unclear commercial terms, and TaxID 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.