shipapis
StarSubmit an APISubmit API

Hunter vs Kroki

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

APIHunterHEALTHY96KrokiHEALTHY92
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362633
P95 · ms8593183
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hunter vs Kroki: common questions

Which is more reliable, Hunter or Kroki?

Both are neck-and-neck — Hunter and Kroki 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, Hunter or Kroki?

Hunter has the lower median latency in our checks — Hunter responds in 362 ms versus Kroki at 633 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 Hunter and Kroki need an API key?

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

Can I call Hunter and Kroki from the browser?

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

Are Hunter and Kroki free for commercial use?

Hunter has unclear commercial terms, and Kroki 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.