Knowledge base video: a help article turned into an explainer
A knowledge base video made by API: a help-center article on pull requests became a narrated explainer video. Watch it, copy the request, see its cost.
How this was made. Audio and video overviews, slide decks, infographics and quizzes are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time.
- Length
- 5 min 42 s
- Credits used
- 50 credits
- Cost on the Starter plan
- €1.45
- Generation time
- 9 min 17 s
- Format
- Explainer video
- Job
- Product docs
- Language
- English
- Generated on
- 2026-11-03
This output used 50 credits, which is €1.45 on the Starter plan (€29 per month for 1,000 credits). Failed generations use none. Generation time runs from the request to the finished file; it depends on the sources, the options and the queue.
What came out, and what we would change
We sent one help article from GitHub Docs, the reference page on pull requests, and asked for a knowledge base video for people who are new to pull requests: what a pull request is, what each tab shows, how drafts work, and the two ways teams collaborate, using only what the article says. The result is a 1280 × 720 MP4 of 5 min 42 s in four numbered sections.
The content follows the article: a pull request as a proposal to merge changes; the Conversation, Commits, Checks, Files changed and Findings tabs; the merge status in the header and the merge box; drafts that cannot be merged and do not ask code owners for a review until they are marked ready; the temporary refs that let integrations test a merge without touching the base branch; and the fork and pull and shared repository models, with the warning that a fork shares its Git data with the upstream.
The additions are small: green and red lines in the diff, and teams in the shared model that are "already trusted". Two points are simplified. A slide says anyone can fork an upstream repository, where the article says anyone with read access, if the owner allows it; the narration gets this right. And the article says GitHub creates the simulated merge ref only when possible.
For a help center, one article per request keeps each video focused, and a webhook can tell your system when each one is ready. The video took 9 min 17 s to generate and used 50 credits.
Transcript excerpt
Speech-to-text of the output, not edited and without speaker labels. It is part of the sample output.
Then we have our safety nets. The checks tab displays automated tests and builds, while the findings tab shows automated review results, like code scanning alerts. And finally, perhaps the biggest one for reviewers, the Files Changed tab. This shows the actual diff, you know, the line-by-line additions in green and deletions in red, so everyone can easily see exactly what's being proposed. Now, aside from those tabs, you're also going to see the Merge status. This sits right up top in the header and down below in the Merge box.
And crucially, it doesn't automatically ask code owners for a review. It's the perfect way to say, hey, here's my work in progress, but please hold off on the formal critique. Then whenever you're ready for that feedback, you just click ready for review. That automatically pings the code owners and preps everything for final feedback. And honestly, the best part is how fluid it is. You can totally convert a pull request back to a draft anytime if you realize you need to go back to the drawing board.
The exact request
The body that was sent to POST /content/Create, unchanged, and the same request as curl.
{
"resources": [
{
"type": "website",
"content": "https://docs.github.com/en/pull-requests/reference/pull-requests"
}
],
"outputType": "video",
"format": "explainer",
"text": "A knowledge base video for people who are new to pull requests: what a pull request is, what each tab shows, how draft pull requests work, and the two collaborative development models. Use only what the article says.",
"language": "English"
}curl -X POST "https://api.autocontentapi.com/content/Create" \
-H "Authorization: Bearer $AUTOCONTENT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"resources":[{"type":"website","content":"https://docs.github.com/en/pull-requests/reference/pull-requests"}],"outputType":"video","format":"explainer","text":"A knowledge base video for people who are new to pull requests: what a pull request is, what each tab shows, how draft pull requests work, and the two collaborative development models. Use only what the article says.","language":"English"}'
# then poll until "status" is 100:
curl -H "Authorization: Bearer $AUTOCONTENT_API_KEY" "https://api.autocontentapi.com/content/Status/<request_id>"How we checked it
- Transcript
- We transcribed the output with Whisper large-v3-turbo and compared the transcript with the source.
- Language
- Detected en, requested en.
- Loudness
- -20.9 LUFS integrated, true peak -1 dBTP.
- Notes
- Tabs, merge status, drafts, refs and both models match the article. Small additions (diff colors, "trusted"); the fork slide drops "with read access, if the owner allows it"; "when possible" dropped for the merge ref.
- Checked on
- 2026-11-03. Failed generations are run again and never published.
More examples
All examples
Explainer video · EnglishDoc to video: Kubernetes documentation as an explainer video9 min 16 s · 50 credits (€1.45 on Starter)
Slide deck · EnglishDoc to slides: the Kubernetes page on Deployments as a deck15 slides · 10 credits (€0.29 on Starter)- Podcast · FrenchProduct docs turned into a French podcast: Kubernetes components5 min 29 s · 10 credits (€0.29 on Starter)