The audio market has a habit: build a friendly consumer app under one brand, build a developer API under another, and let them drift apart. Two products, two roadmaps, two things to keep in sync.
We took the other path. Scarleta is one platform with two front doors into the same engine: a conversational chat for people, and a REST API for developers.
Same engine, different doors
Under the hood there's one set of audio capabilities: separating stems, transcribing speech, finding key and tempo, cleaning up noise, and more. What changes is how you reach it.
If you're a person, you open the chat, describe what you want in plain language, and the AI figures out which capabilities to use, runs them, and shows you the results inline. You don't learn an API. You just ask.
If you're a developer, you call the API directly. The flagship developer surface is the batch API. Submit many files, get results back, with fair concurrency, retry, cancel, and honest error codes. There's also a Chat / Agent API for developers who want the "just describe it" experience programmatically, and an MCP server so other AIs can call the same tools.
Why not two brands?
Because the split is an accident of org charts, not of users. Splitting into two brands means the consumer app and the developer API get different teams, different priorities, and slowly different capabilities, and eventually the thing you can do by chatting isn't the thing you can do by API.
Keeping one engine behind both doors means the opposite: when we make the platform better at understanding a song, everyone gets it: the person chatting and the developer batching, on the same day.
Who this is for
- Creators and non-developers who want to store, understand, and change their audio without touching code. The chat is for you.
- Developers and teams who want to build audio understanding into their own products. The API is for you.
Two audiences that usually get two companies. We think they deserve one platform that's honest about both: a simple front door for people, and a real API for developers, opening onto the same room.
The conversational chat and the developer API (including the batch API, the Chat / Agent API, and the MCP server) are live surfaces. See Developers and Features.