Lobsters vs Disify

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

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 limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lobsters vs Disify: common questions

Which is more reliable, Lobsters or Disify?

Only Disify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Lobsters and Disify need an API key?

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

Can I call Lobsters and Disify from the browser?

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

Are Lobsters and Disify free for commercial use?

Lobsters has unclear commercial terms, and Disify 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.