Apiverket vs Federal Register

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%98.3%
P50 · ms444478
P95 · ms38273165
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedUS Government work — public domain
Free tierFree tier — API key requiredFree — no key or signup required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Apiverket vs Federal Register: common questions

Which is more reliable, Apiverket or Federal Register?

On our scheduled checks, Apiverket leads on measured uptime — Apiverket at 100% versus Federal Register at 98.0% 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, Apiverket or Federal Register?

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

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

Can I call Apiverket and Federal Register from the browser?

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

Apiverket has unclear commercial terms, and Federal Register 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.