shipapis
StarSubmit an APISubmit API

Registrum API vs Wikidata

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

APIRegistrum APIHEALTHY96WikidataHEALTHY90
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms246585
P95 · ms15533283
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

Registrum API vs Wikidata: common questions

Which is more reliable, Registrum API or Wikidata?

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

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

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

Can I call Registrum API and Wikidata from the browser?

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

Are Registrum API and Wikidata free for commercial use?

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