Lanyard vs Remote OK Jobs API

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

Uptime · 30d
Uptime · 90d99.02%98.0%
Uptime · 30d100%98.3%
P50 · ms279741
P95 · ms15884191
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs Remote OK Jobs API: common questions

Which is more reliable, Lanyard or Remote OK Jobs API?

On our scheduled checks, Lanyard leads on measured uptime — Lanyard at 99.02% versus Remote OK Jobs API at 98.0% 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, Lanyard or Remote OK Jobs API?

Lanyard has the lower median latency in our checks — Lanyard responds in 279 ms versus Remote OK Jobs API at 741 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 Lanyard and Remote OK Jobs API need an API key?

Neither needs a paid key — Lanyard is callable with no signup, and Remote OK Jobs API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Lanyard and Remote OK Jobs API from the browser?

Yes — both Lanyard and Remote OK Jobs API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Lanyard and Remote OK Jobs API free for commercial use?

Lanyard has unclear commercial terms, and Remote OK Jobs API 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.