shipapis
StarSubmit an APISubmit API

Hunter vs Shodan EntityDB API

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

APIHunterHEALTHY96Shodan EntityDB APIHEALTHY87
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362918
P95 · ms8591306
AuthapiKeynone
CORSnono
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 Shodan EntityDB API: common questions

Which is more reliable, Hunter or Shodan EntityDB API?

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

Hunter has the lower median latency in our checks — Hunter responds in 362 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 Hunter and Shodan EntityDB API need an API key?

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

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

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

Are Hunter and Shodan EntityDB API free for commercial use?

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