Excuser vs kanye.rest

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms30348
P95 · ms932512
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Excuser vs kanye.rest: common questions

Which is more reliable, Excuser or kanye.rest?

Both are neck-and-neck — Excuser and kanye.rest each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Excuser or kanye.rest?

kanye.rest has the lower median latency in our checks — Excuser responds in 303 ms versus kanye.rest at 48 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 Excuser and kanye.rest need an API key?

Neither needs a paid key — Excuser is callable with no signup, and kanye.rest is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Excuser and kanye.rest from the browser?

Yes — both Excuser and kanye.rest 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 Excuser and kanye.rest free for commercial use?

Excuser has unclear commercial terms, and kanye.rest 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.