Synced lyrics for every song in your catalog — one REST integration.

Two composable halves. The data half serves any platform: submit a song, we transcribe and time-align it in the original script, someone checks the words — on our pages or inside your product — and the outputs come back as LRC, SRT and word-level data. The optional layer on top: your users create lyric videos under your brand, paid by you or by them.

Find yourself first — everything below serves all three

Five steps, two of them optional

1. 1Submit a songOne POST /v1/transcribe with the audio, the artist’s reference, and how you want review to run. Batches of up to 20 via POST /v1/batch.
2. 2We transcribe and alignOriginal script, romanisation and translation, then line and word timing against the recording. Most songs finish in under a minute; a second, independent listener flags lines it heard differently.
3. 3Someone checks the words (optional)Submit with review=true and the job holds until a human approves it — the artist on our hosted review page, or your own catalog team inside your product. Corrections feed the timing pass.
4. 4Outputs deliveredA signed webhook tells you the moment a job lands; LRC, SRT and word-level JSON download per script. Poll instead if you prefer.
5. 5Your user orders a lyric video (optional layer)From the same page they reviewed on: full-song 16:9, a 9:16 vertical, and a short teaser cut. Paid from your prepaid balance, or by your user directly with a commission accruing to you. Partners who only want the data never touch this step.

One call carries everything

Audio arrives as a direct file upload or an HTTPS audio_url(the only option above 4.5 MB; supported up to 100 MB). We only send GET requests, so presigned S3 and GCS links work, and a link its host refuses is rejected at submission before anything is charged. The link must stay valid until we fetch it — a minute or two for one song, longer when you submit in bulk and songs wait their turn, so make bulk links valid for 24 hours. After that we keep our own copy. Send an Idempotency-Key header and a retried submission can never create a second job or a second charge.

curl -X POST https://lyrcs.ai/api/v1/transcribe \
  -H "Authorization: Bearer $LYRCS_API_KEY" \
  -H "Idempotency-Key: rv-88121-lyrics-1" \
  -H "Content-Type: application/json" \
  -d '{
    "audio_url": "https://cdn.example.com/masters/rv-88121.wav",
    "language": "hindi",
    "isrc": "INWAV2600347",          // dedupe + reporting
    "end_user": {                     // who the song belongs to
      "external_id": "rv-88121",     // your customer id — required
      "email": "artist@example.com", // optional, notifications only
      "name": "Ritika Verma"
    },
    "review": true,                   // hold for the artist's approval
    "review_delivery": "both",        // "both" | "link" | "api"
    "webhook_url": "https://api.example.com/hooks/lyrcs"
  }'

isrc is normalised and indexed — GET /v1/jobs?isrc=…answers “have we already done this song?” before you submit it twice. end_user.external_idis your customer reference and is what the artist’s whole downstream experience hangs off; the email is never used to match accounts. Every field is specified in the API reference.

You choose where the words get checked

A held job is one job with two doors, chosen per submission with review_delivery. Both doors edit and approve the same lyrics; nothing downstream cares which one was used.

Signed, retried, and never silently lost

// headers on every delivery
X-Lyrcs-Event:     job.complete
X-Lyrcs-Job-Id:    9f3a…
X-Lyrcs-Timestamp: 1788500000
X-Lyrcs-Signature: sha256=hex(
  HMAC-SHA256(webhook_secret, raw_body)
)

Let your users create lyric videos

Optional, and off until you switch it on: it exists only when a job carries an end_user and your price book offers products. Every such job gives that person — an artist, a label client, a sync manager — a private page listing their songs: review links, synced-lyric downloads (LRC and SRT, original or romanised), and lyric video ordering with a full studio: their artwork or ours, their styling, karaoke or static, full-song 16:9, a 9:16 vertical, and a short teaser cut for Reels and Shorts. White-label means they see your name on every one of these pages. Enabling it later needs no re-integration — the end_userreference you’ve been sending from day one is the hook it hangs on.

Prices and shares are set per agreement, in your currency — there is no public rate card. Default API limits (10 submissions a minute, 1,000 a day) suit a pilot and are raised per organisation when volume calls for it.