shipapis
StarSubmit an APISubmit API

Lanyard vs xfetch

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

APILanyardNEW—xfetchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs xfetch: common questions

Which is more reliable, Lanyard or xfetch?

On our scheduled checks, xfetch leads on measured uptime — Lanyard at —% versus xfetch 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 Lanyard and xfetch need an API key?

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

Can I call Lanyard and xfetch from the browser?

Yes — both Lanyard and xfetch 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 xfetch free for commercial use?

Lanyard has unclear commercial terms, and xfetch 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.