shipapis
StarSubmit an APISubmit API

Kroki vs Shodan EntityDB API

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

APIKrokiHEALTHY92Shodan EntityDB APIHEALTHY87
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms633918
P95 · ms31831306
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Kroki vs Shodan EntityDB API: common questions

Which is more reliable, Kroki or Shodan EntityDB API?

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

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

Neither needs a paid key — Kroki is callable with no signup, and Shodan EntityDB API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Kroki and Shodan EntityDB API from the browser?

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

Are Kroki and Shodan EntityDB API free for commercial use?

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