Genrenator vs Lyrics.ovh

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms4831241
P95 · ms14712725
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (lyrics are third-party copyrighted)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Genrenator vs Lyrics.ovh: common questions

Which is more reliable, Genrenator or Lyrics.ovh?

Both are neck-and-neck — Genrenator and Lyrics.ovh 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, Genrenator or Lyrics.ovh?

Genrenator has the lower median latency in our checks — Genrenator responds in 483 ms versus Lyrics.ovh at 1241 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 Genrenator and Lyrics.ovh need an API key?

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

Can I call Genrenator and Lyrics.ovh from the browser?

Yes — both Genrenator and Lyrics.ovh 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 Genrenator and Lyrics.ovh free for commercial use?

Genrenator has unclear commercial terms, and Lyrics.ovh 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.