AI Dev Jobs vs LectServe

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms339786
P95 · ms9411633
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — public read endpoints openFree — limits not published
Rate limitHourly abuse throttle; optional free API keyUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AI Dev Jobs vs LectServe: common questions

Which is more reliable, AI Dev Jobs or LectServe?

On our scheduled checks, AI Dev Jobs leads on measured uptime — AI Dev Jobs at 100% versus LectServe at 99.02% 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, AI Dev Jobs or LectServe?

AI Dev Jobs has the lower median latency in our checks — AI Dev Jobs responds in 339 ms versus LectServe at 786 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 AI Dev Jobs and LectServe need an API key?

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

Can I call AI Dev Jobs and LectServe from the browser?

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

Are AI Dev Jobs and LectServe free for commercial use?

AI Dev Jobs has unclear commercial terms, and LectServe 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.