IBAN Validation API vs SEC EDGAR Data

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic domain (U.S. government work)
Free tierFree — limits not publishedFree — public government data
Rate limitUnpublishedMax 10 requests/second; descriptive User-Agent required (SEC fair-access policy)
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBAN Validation API vs SEC EDGAR Data: common questions

Which is more reliable, IBAN Validation API or SEC EDGAR Data?

On our scheduled checks, SEC EDGAR Data leads on measured uptime — IBAN Validation API at —% versus SEC EDGAR Data 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 SEC EDGAR Data need an API key?

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

Can I call IBAN Validation API and SEC EDGAR Data from the browser?

Yes — both IBAN Validation API and SEC EDGAR Data 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 SEC EDGAR Data free for commercial use?

IBAN Validation API has unclear commercial terms, and SEC EDGAR Data allows commercial use on its free tier. 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.