Authentication vs FullHunt

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms720334
P95 · ms18011156
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Authentication vs FullHunt: common questions

Which is more reliable, Authentication or FullHunt?

Both are neck-and-neck — Authentication and FullHunt 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, Authentication or FullHunt?

FullHunt has the lower median latency in our checks — Authentication responds in 720 ms versus FullHunt at 334 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 FullHunt need an API key?

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

Can I call Authentication and FullHunt from the browser?

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

Are Authentication and FullHunt free for commercial use?

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