Divi AI is a $193 second AI bill
Updated October 31, 2026
Divi AI costs $193 a year as of October 2026, or $21.36 a month. If you already pay for Claude or ChatGPT, that's a second AI subscription that only works inside one builder.
Sometimes it's worth it. Divi AI generates images and builds from a screenshot, and your own assistant can't do either inside the Visual Builder. But a lot of what people actually buy it for (rewrite this blurb, change these prices, fix that footer) your own assistant can already do on a Divi page through Kitepod, which is free.
What $193 a year buys
Elegant Themes' AI page covers four areas: text (write and refine copy), images (generate, edit, extend, upscale), code (HTML, CSS and JavaScript in Divi's code module, "fine-tuned on the Divi module codebase") and layouts up to whole sites with Divi Quick Sites. It says generation is unlimited under a fair use policy.
The Divi AI Agent is billed differently. It draws from a separate balance, and the plan includes $60 a year of agent spend. Elegant Themes' help center says it has "more than 190 purpose-built tools for Divi and WordPress". It builds layouts from a brief, a screenshot or a URL, edits presets, global variables and global colors, and manages pages, menus and Theme Builder templates.
Two limits are in Elegant Themes' own docs. Requests made outside the Visual Builder get a smaller set of abilities. And the agent doesn't connect to outside tools through MCP yet.
| Divi AI | Kitepod | |
|---|---|---|
| Price, October 2026 | $193/yr or $21.36/mo, agent usage from a separate balance | Free; the AI runs on the Claude or ChatGPT you pay for |
| Where you work | The Divi 5 Visual Builder for the agent | Whichever MCP app you use, Claude and ChatGPT included |
| Image generation | Yes | No (finds free stock photos instead) |
| MCP | Not yet, per Elegant Themes | It's an MCP server |
| Other sites and plugins | No | Every connected WordPress site |
| Staged preview, 90-day undo | Not published | Yes |
On Divi, the layout is the content
Most builders hide their layout in a separate field. Divi doesn't. A Divi 4 page is [et_pb_*] shortcodes in the post content, and a Divi 5 page is divi/* block markup in the same place.
That's good news and bad news. Your assistant can reach a Divi layout with ordinary content tools, so nothing exotic is needed. But one stray square bracket can turn a module into broken text, so every Kitepod edit to a Divi page lands on a staged preview first.
It also means Kitepod handles both generations. Elegant Themes' agent docs and launch post are written for Divi 5. If half your client sites still run Divi 4 shortcodes, your assistant edits those the same way it edits Divi 5 blocks.
Three Divi requests
Picture a dental practice, Brightside Dental, with four locations on a Divi site.
On the Fees page, change the hygiene appointment from £65 to £70 in the pricing table, and show me before it's live.
Your assistant reads the whole page, edits only that pricing table module and keeps your site's existing attribute style, including _builder_version. You get a preview link. Say publish, and Kitepod screenshots the live page before and after.
Our "Book online" call-to-action is a global module. Change the button text to "Book your check-up".
Global modules live in the Divi Library and show on every page that uses them. You'll hear that from your assistant up front. Then it changes the library item once, and all four location pages pick it up.
Add an "Emergency appointments" section to the Harrogate location page, in the same style as the opening hours section.
On Divi 5, the attribute schema is large and changes between versions, so your assistant copies a module of the same type from a page already on your site and changes only its values. It never writes Divi 5 attributes from memory. On Divi 4 it copies an existing row's shortcode structure, with columns that add up to one row.
Getting Kitepod on a Divi site
Kitepod is a small plugin plus a URL. Add the plugin to your Divi site (it supports WordPress 6.4 and up, PHP 7.4 and up), then press Connect and say which WordPress user the AI may act as; an Editor account can't do more than an Editor. Your assistant gets the address https://kitepod.com/mcp, you sign in once, and that's it. Per-app screens are on WordPress MCP.
Divi-specific snags
- Divi writes static CSS per page into
wp-content/et-cache. Saving the post through WordPress clears that page's files. If styles still look stale, clear the static CSS yourself in Divi > Theme Options > Builder > Advanced, then Kitepod can flush the page cache. - A brand new Divi page needs Divi's builder flag, which is protected. Your assistant either copies an existing Divi page's structure, or you open the new page once in the Divi builder.
- Code modules with scripts need a user with
unfiltered_html, usually an administrator. Otherwise WordPress strips the script. - Divi 5 converts Divi 4 shortcodes when it opens a page, so your assistant keeps whichever format the page already uses and never mixes them.
Finer points
Is there a Divi MCP server?
Not from Elegant Themes yet: its help center says the Divi AI Agent doesn't support MCP. Kitepod is one, and it edits Divi 4 and Divi 5 pages along with the rest of your site.
Does Kitepod work with Divi 5?
Yes. It edits Divi 5 block markup as full page content, copying modules that already exist on your site rather than guessing attributes.
Do I need Divi AI to use Kitepod on a Divi site?
No. Divi AI and Kitepod don't depend on each other. Kitepod has no model and no credits; the work is done by your Claude or ChatGPT subscription.
Can it build a whole Divi site from one prompt?
It builds pages section by section in Divi's format. For a full site from one prompt, Divi Quick Sites is made for exactly that.
If you live in the Visual Builder, Divi AI earns its $193. If your week is spread across other builders and other people's sites, most of it sits unused.