shipapis
StarSubmit an APISubmit API

ExchangeRate-API (open) vs Fed Treasury

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

APIExchangeRate-API (open)NEW—Fed TreasuryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedOpen U.S. Government data (public domain)
Free tierFree — limits not publishedFree — no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ExchangeRate-API (open) vs Fed Treasury: common questions

Which is more reliable, ExchangeRate-API (open) or Fed Treasury?

On our scheduled checks, Fed Treasury leads on measured uptime — ExchangeRate-API (open) at —% versus Fed Treasury 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 ExchangeRate-API (open) and Fed Treasury need an API key?

Neither needs a paid key — ExchangeRate-API (open) is callable with no signup, and Fed Treasury is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ExchangeRate-API (open) and Fed Treasury from the browser?

Only ExchangeRate-API (open) is browser-friendly — it returns CORS headers over HTTPS. Fed Treasury needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ExchangeRate-API (open) and Fed Treasury free for commercial use?

ExchangeRate-API (open) has unclear commercial terms, and Fed Treasury 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.