Public Time API vs Remote OK Jobs API

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%98.3%
P50 · ms242741
P95 · ms3824191
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

Public Time API vs Remote OK Jobs API: common questions

Which is more reliable, Public Time API or Remote OK Jobs API?

On our scheduled checks, Public Time API leads on measured uptime — Public Time API at 100% 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, Public Time API or Remote OK Jobs API?

Public Time API has the lower median latency in our checks — Public Time API responds in 242 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 Public Time API and Remote OK Jobs API need an API key?

Neither needs a paid key — Public Time API 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 Public Time API and Remote OK Jobs API from the browser?

Only Remote OK Jobs API is browser-friendly — it returns CORS headers over HTTPS. Public Time API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Public Time API and Remote OK Jobs API free for commercial use?

Public Time API 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.