The repurposing grind
You recorded once. Now you need titles, descriptions, chapters, captions, a newsletter and a thread. By hand.
For creators and creator platforms
Turn one long video into a newsletter, ten clips' worth of captions and a week of community posts. Build it into your own workflow or into the platform your creators love.
repurpose without starting over
know what each draft cost
one endpoint for every feature
The problem
You recorded once. Now you need titles, descriptions, chapters, captions, a newsletter and a thread. By hand.
Your community is growing faster than your ability to reply thoughtfully.
If you build tools for creators, unpredictable model bills make it hard to price a plan.
Capabilities
Send a transcript and ask for titles, chapters, a newsletter draft and social posts in one structured response.
Include a few of your real replies as examples and get draft responses you can approve in seconds.
Captions and hashtags do not need a heavyweight. The router picks the lowest-priced model for the capability you ask for.
Every call returns tokens and price, so you can set fair limits and plans for your own creators.
When the same prompt runs again within the cache window, the answer is served from cache and not billed.
No code needed to test a prompt. Open the console, paste, run.
Use cases
Timestamps, summaries and links pulled from your transcript.
This week's episode, rewritten as a reader-friendly email with a strong subject line.
Warm, on-brand replies to comments and DMs for you to review and send.
Talking points that fit your style and the sponsor's brief.
How it works
Every account starts with a monthly free token allowance.
Use the playground to shape prompts for each format you publish.
Hook the endpoint into your editing workflow or your platform's backend with an API key.
Control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'Not to start. The playground works in the browser. To automate, one HTTP request does the job.
Yes. Call the API from your backend, keep the key server-side, and use the per-call price to design your plans.
Give it examples of your writing in the prompt. The model works from what you send.
Pricing is per token and shown for each model in the catalog. A free monthly allowance covers your first experiments.
Start repurposing on the free allowance. Your audience is waiting.