shipapis
StarSubmit an APISubmit API

District of Columbia Open Data vs USAspending.gov

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

APIDistrict of Columbia Open DataNEW—USAspending.govNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverified (DC Open Data terms)U.S. Government Work (public domain)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

District of Columbia Open Data vs USAspending.gov: common questions

Which is more reliable, District of Columbia Open Data or USAspending.gov?

On our scheduled checks, USAspending.gov leads on measured uptime — District of Columbia Open Data at —% versus USAspending.gov 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 District of Columbia Open Data and USAspending.gov need an API key?

Neither needs a paid key — District of Columbia Open Data is callable with no signup, and USAspending.gov is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call District of Columbia Open Data and USAspending.gov from the browser?

Only District of Columbia Open Data is browser-friendly — it returns CORS headers over HTTPS. USAspending.gov needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are District of Columbia Open Data and USAspending.gov free for commercial use?

District of Columbia Open Data has unclear commercial terms, and USAspending.gov 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.