Brazil vs Open Government, ACT

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

Uptime · 30d
Uptime · 90d100%93.1%
Uptime · 30d100%90.0%
P50 · ms1223297
P95 · ms8624902
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedPer-dataset
Free tierFree — no key (beta)Free — app token optional (raises limits)
Rate limitFair use — no loops or full-range scanningThrottled; higher limits with a free Socrata app token
In directory since2026-07-052026-07-05
operationalpartialdownno data

Brazil vs Open Government, ACT: common questions

Which is more reliable, Brazil or Open Government, ACT?

On our scheduled checks, Brazil leads on measured uptime — Brazil at 100% versus Open Government, ACT at 93.1% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Brazil or Open Government, ACT?

Brazil has the lower median latency in our checks — Brazil responds in 122 ms versus Open Government, ACT at 3297 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 Brazil and Open Government, ACT need an API key?

Neither needs a paid key — Brazil is callable with no signup, and Open Government, ACT is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Brazil and Open Government, ACT from the browser?

Yes — both Brazil and Open Government, ACT 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 Brazil and Open Government, ACT free for commercial use?

Brazil has unclear commercial terms, and Open Government, ACT 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.