shipapis
StarSubmit an APISubmit API

City, Analyze Boston vs Data.gov

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

APICity, Analyze BostonHEALTHY90Data.govHEALTHY79
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms663931
P95 · ms14102035
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Analyze Boston vs Data.gov: common questions

Which is more reliable, City, Analyze Boston or Data.gov?

Both are neck-and-neck — City, Analyze Boston and Data.gov 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, City, Analyze Boston or Data.gov?

City, Analyze Boston has the lower median latency in our checks — City, Analyze Boston responds in 663 ms versus Data.gov at 931 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 City, Analyze Boston and Data.gov need an API key?

Data.gov needs no key, while City, Analyze Boston requires a free API key. If you want to start calling without signup, reach for Data.gov first.

Can I call City, Analyze Boston and Data.gov from the browser?

Neither sends browser-friendly CORS headers reliably, so call City, Analyze Boston and Data.gov from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are City, Analyze Boston and Data.gov free for commercial use?

City, Analyze Boston has unclear commercial terms, and Data.gov has unclear commercial terms. 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.