Findwork vs Lobsters

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms481243
P95 · ms19151175
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limit4294967295 req/window · 4294967295 remaining · resets 0Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Findwork vs Lobsters: common questions

Which is more reliable, Findwork or Lobsters?

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

Lobsters has the lower median latency in our checks — Findwork responds in 481 ms versus Lobsters at 243 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 Findwork and Lobsters need an API key?

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

Can I call Findwork and Lobsters from the browser?

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

Are Findwork and Lobsters free for commercial use?

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