Make a video ad from your AI agent with adkix

Who drives adkix from an agent

adkix turns a website into a story-led vertical video ad, with no avatar and no shoot. On adkix.ai you click through each step yourself. With the API, your assistant does the clicking: it reads the project's state, shows you the images and voices, and waits for your go-ahead. Same steps, same prices as the web studio, just inside the conversation.

Agencies running several brands use it to start one video per client without opening the studio each time, and to get notified when a step needs a decision. Developers plug adkix into their product or scripts: eleven REST operations described in OpenAPI 3.1, JSON responses, and long polling instead of sleep loops.

And if you mostly build by talking to Claude Code or Cursor, there's nothing to write. Install the skill or add the MCP server, then ask for an ad for your site. The assistant makes the calls; you make the choices.

Connect adkix to your agent in 4 steps

The path is the same for a new account and an existing one.

1. Create a key, or let the agent sign you up

   On adkix.ai/compte under API, or right in the chat: the agent asks for your email, a 6-digit code arrives by mail (valid 15 minutes), and the agent trades it for a key. A new account gets 1,000 free credits.

2. Pick your entry point

   The skill for Claude Code, Claude Desktop and claude.ai; the MCP server for Cursor, VS Code, Codex or Claude Code; the REST API for your own code. The key lives in a private file or an environment variable, never in the conversation.

3. Give a website, an @account or an idea

   The agent creates the content (createContent or adkix_create_content). adkix reads your brand right away, and nothing paid starts at that point.

4. Approve step by step until the film

   The agent follows the state, shows you the previews and suggests the next action. Every paid step returns a quote first, and the agent confirms it only after your yes. At the end, a signed link opens the film in any browser.

REST, MCP or Claude skill: which to pick

All three lead to the same account, the same steps and the same quotes.

Per-key limits: 120 reads a minute, 30 actions a minute, 10 new contents a day (20 per account). Full details on the developers page.

What the person always approves, even with an agent

The agent proposes; it doesn't decide. The project's state carries a suggestion, the next click adkix would make, but the server never runs it. The assistant shows it to you and you say yes or no. The story angle, the visual style, the script line by line and the voice all go through you.

Money follows a strict rule. A paid action spends nothing: it returns a quote with the price in credits and a sentence to read to you. Only the confirm call charges, for that exact quote, and an unconfirmed quote expires after 10 minutes. Over MCP, the confirm tool is flagged as destructive, so your client asks for permission before calling it.

• The angle: three story ideas, you keep one.
• The style and the look: live action, motion design, cartoon…
• The script: every line, before any voice or image.
• The price: every quote, before a single credit is spent.