Federal Register vs OpenRegistry

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

Uptime · 30d
Uptime · 90d98.0%98.0%
Uptime · 30d98.3%96.7%
P50 · ms478363
P95 · ms31651313
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUS Government work — public domainUnverified
Free tierFree — no key or signup requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Federal Register vs OpenRegistry: common questions

Which is more reliable, Federal Register or OpenRegistry?

Both are neck-and-neck — Federal Register and OpenRegistry each measure 98.0% 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, Federal Register or OpenRegistry?

OpenRegistry has the lower median latency in our checks — Federal Register responds in 478 ms versus OpenRegistry at 363 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 Federal Register and OpenRegistry need an API key?

Federal Register needs no key, while OpenRegistry requires a free API key. If you want to start calling without signup, reach for Federal Register first.

Can I call Federal Register and OpenRegistry from the browser?

Yes — both Federal Register and OpenRegistry 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 Federal Register and OpenRegistry free for commercial use?

Federal Register allows commercial use on its free tier, and OpenRegistry 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.