shipapis
StarSubmit an APISubmit API

Datasette vs Registrum API

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

APIDatasetteHEALTHY97Registrum APIHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms293246
P95 · ms8921553
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Datasette vs Registrum API: common questions

Which is more reliable, Datasette or Registrum API?

Both are neck-and-neck — Datasette and Registrum API 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, Datasette or Registrum API?

Registrum API has the lower median latency in our checks — Datasette responds in 293 ms versus Registrum API at 246 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 Datasette and Registrum API need an API key?

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

Can I call Datasette and Registrum API from the browser?

Only Datasette is browser-friendly — it returns CORS headers over HTTPS. Registrum API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Datasette and Registrum API free for commercial use?

Datasette has unclear commercial terms, and Registrum API 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.