For developers
Docs, changelogs and the API to automate both
Documentation is the work that always loses to shipping. The gap is rarely knowledge, it is that turning what you know into prose takes a different mode of thinking than the one you were just in.
Explain the code you inherited
Paste a file and get an explanation of what it does, which parts are load-bearing and which context it would need to be sure. It says when it is guessing, which is the property that makes it usable.
Changelogs from commits
Feed a list of commits or tickets to the release notes template and get something a customer would read, with fixes and features marked separately.
Automate it from the API
Scale includes a REST API and webhooks, so transcription and generation become steps in a pipeline rather than a tab someone remembers to open. Bring your own model key if you would rather pay the provider directly.
The workflow, in three moves
Connect
API key from the dashboard, or a webhook per event.
Pipe work in
POST an audio file or a prompt; poll or receive the callback.
Publish
Pull the finished document as Markdown into your own site build.