Your source material,ready for any format.

The documented content API supports source-driven outputs including video, audio and podcasts, infographics, slide decks, quizzes, deep research, and shorts. The current API documentation is the source of truth for available formats and request fields.

No. AutoContent API is an independent service and is not affiliated with or endorsed by Google. Google Cloud documents selected Enterprise APIs; AutoContent provides its own public REST endpoints for finished-content workflows and the separately offered Private Notebooks service.

Create an AutoContent API key in the platform, keep it server-side, and send it as a Bearer token to the documented REST endpoints. Do not place API keys in browser code, URLs, analytics, or public repositories.

Because AutoContent uses standard HTTP requests, you can integrate from any language. The documentation includes examples for common environments such as cURL, Node.js, Python, C#, and PHP.

Finished-content generation uses the existing AutoContent credit plans, which start at €29 per month. Private Notebooks is an additional €99 monthly subscription with its own dedicated provider capacity and no AutoContent generation credits or per-call fees within that capacity.

Private Notebooks gives you persistent notebooks and source capacity for work you need to return to. One license is assigned one dedicated account, and its notebooks, sources, and provider capacity are separated from other licenses. It does not replace the existing content-generation API.

One license includes capacity for 200 notebooks, 100 sources per notebook, 200 questions per rolling 24 hours, 6 audio overviews per rolling 24 hours, and 6 video overviews per rolling 24 hours. Provider limits can change.

No. Private Notebooks does not consume AutoContent generation credits and has no per-call fees within its licensed provider capacity. The separate content-generation plans continue to use credits for video, audio, infographics, slide decks, and other request-based outputs.

An operation is available only when the dedicated Private Notebooks guide lists it as currently enabled and production-verified. Licensed capacity for questions, audio, video, or another provider feature does not by itself mean a corresponding public endpoint exists.

Yes. Each license uses one dedicated account, and its notebooks, sources, and provider capacity are separated from other licenses. “Private” describes this separation; AutoContent and its third-party processors still process submitted content as needed to operate documented features.

After a successful checkout, AutoContent activates the dedicated account and sends access details to the checkout email within one business day. You receive AutoContent API access, not credentials for the underlying third-party account.