shipapis
StarSubmit an APISubmit API

Authentication vs dead-drop

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

APIAuthenticationNEW—dead-dropNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished100 req/window · 100 remaining · resets 1783513841
In directory since2026-07-052026-07-05
operationalpartialdownno data

Authentication vs dead-drop: common questions

Which is more reliable, Authentication or dead-drop?

On our scheduled checks, dead-drop leads on measured uptime — Authentication at —% versus dead-drop at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Authentication and dead-drop need an API key?

Neither needs a paid key — Authentication is callable with no signup, and dead-drop is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Authentication and dead-drop from the browser?

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

Are Authentication and dead-drop free for commercial use?

Authentication has unclear commercial terms, and dead-drop 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.