Every recording just got a table of contents.
Chapters turns any recording you can transcribe into titled, timestamped segments — so you skim it in seconds and jump straight to the moment. No editor, no scrubbing, no timeline. One call, checked against 48 fail-closed gateway scopes before anything runs.
$ curl -sX POST https://api.wave.online/v1/chapters -H "Authorization: Bearer <key>" -d '{}'
403 {"error":{"code":"SCOPE_INSUFFICIENT","required_scope":"chapters:write"}} fail-closed at the gateway, live
The dead hour is over
That two-hour recording nobody ever rewatches becomes something you skim in seconds — titled chapters, real timestamps, jump straight to the moment that matters. No scrubbing. No editor. No timeline to drag.
The whole catch
Feed it the transcript; it comes back as clean chapters — each a titled segment with a timestamp. No manual chaptering, no video editor, no per-seat tool. It runs on any recording you can transcribe — podcast, webinar, lecture, standup, sales call — and you pay only for the recordings you chapter.
Where it composes
It's one call on the WAVE plane: auth and pay-per-use settle at the gateway, so Chapters drops into any pipeline right next to the rest of WAVE — transcribe upstream, chapter here, stream and search downstream. Chapters is the layer where your recordings stop being opaque and become navigable.
Federated — auth, entitlement, and metering run through api.wave.online; this spoke renders the front-door and forwards the rest.