shipapis
StarSubmit an APISubmit API

Footer Year Update vs LectServe

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

APIFooter Year UpdateNEW—LectServeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesno
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

Footer Year Update vs LectServe: common questions

Which is more reliable, Footer Year Update or LectServe?

On our scheduled checks, LectServe leads on measured uptime — Footer Year Update at —% versus LectServe at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Footer Year Update and LectServe need an API key?

Neither needs a paid key — Footer Year Update 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 Footer Year Update and LectServe from the browser?

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

Are Footer Year Update and LectServe free for commercial use?

Footer Year Update 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.