Authentication vs dead-drop
Same instrument, two spec sheets — measured, not claimed.
Authentication vs dead-drop: common questions
Which is more reliable, Authentication or dead-drop?
On our scheduled checks, Authentication leads on measured uptime — Authentication at 100% versus dead-drop at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, Authentication or dead-drop?
Authentication has the lower median latency in our checks — Authentication responds in 720 ms versus dead-drop at 722 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 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.