Lanyard vs The SMS Works API

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms279518
P95 · ms15881101
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 The SMS Works API: common questions

Which is more reliable, Lanyard or The SMS Works API?

On our scheduled checks, The SMS Works API leads on measured uptime — Lanyard at 99.02% versus The SMS Works API at 100% 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 The SMS Works API?

Lanyard has the lower median latency in our checks — Lanyard responds in 279 ms versus The SMS Works API at 518 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 The SMS Works API need an API key?

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

Can I call Lanyard and The SMS Works API from the browser?

Yes — both Lanyard and The SMS Works 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 The SMS Works API free for commercial use?

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