shipapis
StarSubmit an APISubmit API

RSQ API vs Shodan EntityDB API

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

APIRSQ APIHEALTHY91Shodan EntityDB APIHEALTHY87
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms783918
P95 · ms13871306
Authnonenone
CORSyesno
HTTPSnoyes
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

RSQ API vs Shodan EntityDB API: common questions

Which is more reliable, RSQ API or Shodan EntityDB API?

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

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

Neither needs a paid key — RSQ API 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 RSQ API and Shodan EntityDB API from the browser?

Neither sends browser-friendly CORS headers reliably, so call RSQ API 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 RSQ API and Shodan EntityDB API free for commercial use?

RSQ API 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.