shipapis
StarSubmit an APISubmit API

Invokely vs Registrum API

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

APIInvokelyREACHABLE100Registrum APIHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms227138
P95 · ms2451553
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-10-122026-07-05
operationalpartialdownno data

Invokely vs Registrum API: common questions

Which is more reliable, Invokely or Registrum API?

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

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

Both ask you to authenticate — Invokely uses an API key and Registrum API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Invokely and Registrum API from the browser?

Only Invokely 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 Invokely and Registrum API free for commercial use?

Invokely 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.