Integrations

JetEngine

Describe the content your site needs and your AI models it end to end, no code.

JetEngine is how your site grows past plain pages and posts. You describe the content structure you need in plain English, and your AI models it end to end: post types, fields, taxonomies, relations, queries, and the listings that display them. No code, no clicking through settings panels.

What it does

Ask your AI for a content structure and it builds the whole thing through native CRUD tools. The JetEngine surface covers:

Custom post types, taxonomies, and the meta boxes and custom fields that hang off them.
Relations between content, kept in sync both directions (link a Property to an Agent and the reverse link follows).
Options pages and glossaries for site-wide settings and reusable value lists.
Query Builder queries that power listings and Listing Grids on your pages.
Custom Content Types (standalone database tables) for high-volume data that does not belong in the posts table.
Forms, dynamic visibility, REST listings, and a profile builder.
Injecting JetEngine dynamic widgets into Elementor so your fields and queries render on the page.

Coming soon

Screenshot: a freshly modeled custom post type in WordPress admin, showing its custom fields and an attached taxonomy created in one AI session.

How it works

Your AI bridges JetEngine's own features and adds native CRUD tools with read-back verification, so every structure it creates is confirmed by reading the result back, not assumed from a tool call returning success. A few details shape how a request unfolds:

Some families need their JetEngine module active first: forms, dynamic visibility, REST listings, the profile builder, Custom Content Types, and glossaries. Your AI lists the available modules before it builds, and can turn one on for you.
Post types are addressed by slug, never by an internal id, so a request reads the same way you would describe it.
Order matters. Your AI creates the post type, flushes rewrite rules, adds the taxonomy and attaches it, then adds the fields. The rewrite flush is why your archives do not 404 after a cache clear.
A listing always needs a query first. Your AI builds the query, then the listing, then drops the Listing Grid on the page, and verifies the listing actually yields results.

One surface per post type

Register any single post type on exactly one surface: JetEngine, or ACF, or WordPress core. Registering the same post type on two surfaces causes conflicts. Pick one and tell your AI if you have a preference.

Trigger the AI

Talk in plain English. You name the content, your AI models it. Paste any of these into your client:

Model a post type with fields and a taxonomytext

Create a 'Properties' custom post type with price, bedrooms, square footage, and a photo gallery, plus a 'Location' taxonomy.

Relate two post typestext

Set up a many-to-many relationship between Properties and Agents.

Build a listing gridtext

Build a listing grid of my latest Projects, 3 columns, newest first, on the homepage.

Show content conditionallytext

Show this pricing section only to logged-in users using JetEngine dynamic visibility.

For the listing grid, your AI builds the query and the listing before placing the grid, then runs render verification to confirm the grid actually returned your Projects rather than rendering empty.

Coming soon

Walkthrough: asking the AI for a 3-column Listing Grid of the latest Projects, watching it build the query and listing, then verifying the rendered grid on the homepage.

Requirements

The JetEngine plugin by Crocoblock, 3.8+ recommended.
Injecting JetEngine dynamic widgets onto a page needs an active builder.
A family that depends on a JetEngine module needs that module active. Your AI checks and offers to enable it.

For a full walkthrough that ties post types, fields, and listings into a finished site, see Build a content site.