Showcase: code that types itself, for developer launches
If your buyer is a developer, the most convincing thing you can show them is the code. This clip is a dark editor window, a file called make-video.ts, and a few lines that import the client, create it with a key and ask for a 30 second launch explainer. It types itself out at a steady pace with syntax colors, over a dark green and navy glow.
How we made it
The editor is an HTML panel with a monospace font and a blinking cursor. Each line of code is stored with the moment it starts typing and a typing speed, about 42 characters a second here. Keywords, strings and comments get their own colors, the same way a real editor would show them. Because every frame is rendered from the page, the text is pin sharp and you can pause on any frame and read it.
The code on screen is a short example, not a full program. That is deliberate. Nine seconds is enough for about eight lines before people stop reading.
How your agent can make one
The public API does not have a dedicated code scene yet. Two routes work today:
- Record it for real. Put the snippet in a page with your editor theme, or open it in a web based editor, and have the agent record it with
record_url. Add the recording to your brand kit's clips and it becomes avideoscene in an explainer. - Use an
imagescene with a screenshot of the code and let the render add motion, a headline and narration around it. Only images saved in your brand kit can appear in a video, so add the image to the kit first.
POST /v1/recordings
{
"url": "https://your-docs.example/snippets/make-video",
"steps": [ { "type": "hold", "seconds": 8 } ]
}
Then add it to your brand kit's clips, reference it in a script and render it with create_explainer.
What it costs
| Step | Credits |
|---|---|
| Record the page | 3 |
| Script | 2 |
| Render, under a minute | 12 |
| Total | 17 |
About $1.70 on the starter pack. If you want a native typing scene in the API, tell us. It is high on our list.