Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lyrcs.ai/llms.txt

Use this file to discover all available pages before exploring further.

Every request to the lyrcs.ai API (except GET /health and GET /languages) must include an Authorization header with your API key. 
Authorization: Bearer lyrcs_sk_live_...

​
Key format

Keys are prefixed with lyrcs_sk_live_ and are scoped to your organisation. All jobs, usage stats, and webhooks are isolated to the org that owns the key.

​
How to get a key

lyrcs.ai API access is available to music distributors, streaming platforms, and rights management companies. To request a key, email api@lyrcs.ai with:
  • Your company name
  • Your use case (e.g. “deliver LRC files to DSPs for Indian language catalog”)
  • Expected monthly volume (number of tracks)
  • Languages you primarily work with
We’ll respond within 2 business days with your key and webhook secret.
Keys are per-organisation and include a separate webhook_secret used to verify HMAC-SHA256 signatures on webhook deliveries. Keep both values secure.

​
Example usage

curl https://lyrcs.ai/api/v1/usage \
  -H "Authorization: Bearer lyrcs_sk_live_..."

​
Security

Never expose your API key in client-side code, public repositories, or logs. If a key is compromised, contact api@lyrcs.ai immediately.
  • Store keys in environment variables, not in source code
  • Rotate keys if you suspect exposure
  • Do not share keys across organisations