ExchangeRate-API (open) vs SEC EDGAR Data

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms221119
P95 · ms1091755
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

ExchangeRate-API (open) vs SEC EDGAR Data: common questions

Which is more reliable, ExchangeRate-API (open) or SEC EDGAR Data?

Both are neck-and-neck — ExchangeRate-API (open) and SEC EDGAR Data 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, ExchangeRate-API (open) or SEC EDGAR Data?

SEC EDGAR Data has the lower median latency in our checks — ExchangeRate-API (open) responds in 221 ms versus SEC EDGAR Data at 119 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 ExchangeRate-API (open) and SEC EDGAR Data need an API key?

Neither needs a paid key — ExchangeRate-API (open) 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 ExchangeRate-API (open) and SEC EDGAR Data from the browser?

Yes — both ExchangeRate-API (open) 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 ExchangeRate-API (open) and SEC EDGAR Data free for commercial use?

ExchangeRate-API (open) 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.