bitpay API vs Fed Treasury

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedOpen U.S. Government data (public domain)
Free tierFree tier — API key may be required for productionFree — no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

bitpay API vs Fed Treasury: common questions

Which is more reliable, bitpay API or Fed Treasury?

On our scheduled checks, Fed Treasury leads on measured uptime — bitpay API 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 bitpay API and Fed Treasury need an API key?

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

Can I call bitpay API and Fed Treasury from the browser?

Only bitpay API 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 bitpay API and Fed Treasury free for commercial use?

bitpay API 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.