Update ·
Make images, clips and music from your own code
The Kuro API makes images, clips, voice-overs and music, runs recipes and tells your server when they are done, with keys limited to what they may do.
Kuro now has a public API. Everything you make in the app, an image, a clip, a voice-over, a piece of music or a recipe run, you can now make from your own code, a script, or a tool like n8n or Zapier.
Start in a minute
Make a key in Settings → Connections, send it as Authorization: Bearer KR_…, and post to /v1/generations. Add ?wait=60 and the answer is the finished picture when it is ready within a minute. The guide and every operation are at meetkuro.com/developers, and the whole API is described at /v1/openapi.json, so you can import it into Postman or hand it to an agent.
If you write TypeScript, npm install @meetkuro/sdk gives you the same calls with types, and retries that never pay twice.
Keys that do only what you let them
When you make a key you can now choose what it may do: read your library, make things, run recipes, and so on. A key like that works only with the API and with MCP, so a key you paste into an automation can’t reach the rest of your account.
Hear when it’s done
Pass a webhook_url and Kuro calls your server when the work is ready, has failed, or a recipe run is waiting on you. Each call is signed with a secret you find in Settings → Connections, and Kuro tries again for a day if your server doesn’t answer.
Work runs on your own provider keys when you hold one that can run it, exactly as in the app: your provider bills you, and Kuro charges no credits. Otherwise it spends credits, and POST /v1/quotes tells you how many before you spend anything.