Don't poll. We call you when it's done.
Submit an async audio job, hand us a webhook URL, and go. The moment the batch finishes, Scarleta POSTs your endpoint with the outcome. No polling loop to babysit. Batch and single-recipe completions both call back.
How it works
No setup, no plugins. Just ask, and get the file back.
Submit with a webhook URL
POST a batch (or a single recipe run) and include your webhook_url in the request. That's the whole setup. No dashboard to register endpoints in, no extra call.
We run it async
Your job fans out and runs in the background. You get a batch_id back immediately and a 202. Nothing to keep open, nothing to poll.
We POST you the moment it's done
When the batch finishes, Scarleta sends a batch_completed callback to your URL with the status and final cost, so you can fetch the results and move on.
Built-in storage
Every result is saved to your library, 1 TB free.
The files you bring and the completed job results you get are kept in one place, so you can come back, compare earlier versions, share a link, or ask across everything you’ve stored, whenever you want.
Recipes
Make a completed job result one step in a pipeline you run by name.
Chain it with other steps into a recipe you design once, then run on a single file in chat or on thousands at once.
See it in action
Don't poll. We call you when it's done.
Simple, transparent pricing
Only pay for the audio you actually process.
1 token = 1 second of audio, minimum 1 token per job.
More than one trick
Scarleta does a whole lot more.
The same account handles all of it. Here are a few very different things you can do with your audio.
For developers
Submit a job, receive the callback
Include webhook_url when you submit and we POST your endpoint on completion. Full payload schema, retry behavior, and receiver hardening live in the docs.
curl -X POST https://api.scarleta.ai/v1/batch \
-H "Authorization: Bearer scar_live_your_key" \
-H "Content-Type: application/json" \
-d '{
"recipe_id": "rec_0001_example",
"audio_urls": [
"https://example.com/track1.mp3",
"https://example.com/track2.mp3"
],
"webhook_url": "https://your-app.com/hooks/scarleta"
}'
# → 202 { "batch_id": "…", "status": "IN_QUEUE" }
# No polling needed. We POST your webhook_url when the batch completes.Ship the async flow without a polling loop
Start on your free tokens. Submit a batch with a webhook_url and let us call you back the moment it's done. Top up only when you need more.
Frequently asked questions
Where do I set up the callback URL?
There's nothing to set up in advance. You pass a webhook_url on the request that submits the job, and the URL travels with each submission. No separate dashboard.
What's in the callback?
The batch_completed callback tells you the batch finished and how it went: the batch id, final status, item counts, and the actual total cost. You then fetch the per-item results from the batch results endpoint. The full field list is in the docs.
Do I still have to poll?
No. That is the point. Submit, then wait for our call. (Polling the status endpoint still works if you ever want it, but you don't need to.)
What if my endpoint is down when the job finishes?
We retry delivery a few times with backoff before giving up, and delivery is idempotent. You won't get a duplicate POST for the same batch. Details are in the docs.
How much does it cost?
You pay per second of audio processed, $0.10 per minute, from prepaid tokens (1 token = 1 second). New accounts start with 300 free tokens; top-ups start at $10. No subscription. Webhook delivery itself costs nothing extra.