Connect ChatGPT

Give ChatGPT the keys to your Content Egg site using a Custom GPT Action and your OpenAPI link.

You'll connect ChatGPT by creating a Custom GPT with an Action that points at your site. ChatGPT reads your site's OpenAPI link, learns what it can do, and logs in with your application password.

Watch it in action

Before you start, finish Turning on Agent Access. You'll need two things from it:

• Your OpenAPI link (shown on the AI Agents page, ends in /wp-json/content-egg/v1/openapi).

• Your WordPress username and the application password you created.

Creating and using Custom GPTs requires a paid ChatGPT plan (Plus, Pro, or Team/Enterprise) — that's an OpenAI requirement, not a Content Egg one. You don't have to use a Custom GPT, though. Any assistant that can make web requests for you — an agent or coding tool like Claude Code or Cursor — can skip this page entirely: just hand it your agent guide link, give it your login, and ask. A Custom GPT is simply the most convenient way to get a reusable ChatGPT that already knows your site.

Step 1 — Create a GPT

In ChatGPT, open the sidebar, choose GPTs → Create, then switch to the Configure tab. Give it a name like "My Content Egg Assistant."

GPTs → Create, then the Configure tab

Step 2 — Add the Action

Scroll to Actions and click Create new action. Choose Import from URL and paste your OpenAPI link (copy it from the AI Agents page). ChatGPT reads it and fills in the list of things it can do on your site.

ChatGPT limits a Custom GPT Action to 30 operations, so the OpenAPI link on the AI Agents page is a ChatGPT-sized profile — it leaves out a few admin/rarely-used actions (module refresh/deactivate, feed status, connect-a-shop, multi-network search) to fit. Those still work in Claude and other clients, or directly in wp-admin. If you paste the un-trimmed spec instead, ChatGPT saves it but then fails at run time with a generic "something went wrong."

The Configure tab — scroll to Actions and click Create new action

Import from URL — paste your OpenAPI link

Step 3 — Set up authentication

ChatGPT's Actions don't have separate username and password boxes — there's a single secret field. So you give ChatGPT your login as one encoded value:

1. Set Authentication to API Key.

2. Set Auth Type to Basic.

3. In the API Key box, paste your base64 token (see below).

The easy way — build it on the AI Agents page. Go to Content Egg → AI Agents, open the ChatGPT tab under Connect your assistant, and expand "Make a Basic auth token". Confirm your username, paste your application password, and click Copy. The token is built right in your browser — nothing is sent anywhere — so you don't need a terminal or any other tool. Paste it into ChatGPT's API Key box.

Make a Basic auth token on the AI Agents page — no terminal needed

Authentication → API Key, Auth Type → Basic, with your encoded login

Step 4 — Give it the guide (don't skip this)

This is the step that makes the assistant genuinely good at your site. Without it, ChatGPT only knows the raw API and tends to build pages with Markdown tables and bare product blocks. With it, it follows your site's workflows and picks the right block every time.

In the GPT's Instructions box (the big field near the top of the Configure tab), add a line pointing to your guide — copy the URL from the Agent guide row on the AI Agents page (Copy link):

Before building or editing any page, read this guide first and follow it: https://YOUR-SITE.com/wp-json/content-egg/v1/agent-guide

ChatGPT fetches it on the first request using its built-in Web Browsing (on by default: Configure tab → Capabilities).

Add the agent guide to the GPT's Instructions

Step 5 — Save it privately, then test

Click Create (top right) to save. ChatGPT asks who can use the GPT — choose Only me.

Save the GPT as “Only me”

Keep this GPT set to "Only me." It carries an Action wired to your site with your application password baked in. Sharing it ("Anyone with the link" or publishing to the GPT Store) would hand other people a GPT that can act on your WordPress site. To cut off access later, delete the GPT and revoke that application password under Users → Profile → Application Passwords.

Now start a chat with it and try:

What can you do with Content Egg on my site? List my active modules.

You should get a short summary of your setup and a list of your active modules.

ChatGPT reporting your active modules

If that works, you're connected. Head to Example prompts & workflows for what to ask next.

If something goes wrong

• "Unauthorized" / 401 or 403 — the encoded login is wrong. Re-generate the base64 of username:application_password, make sure you used the application password (not your normal login password), and check there's a single : between the username and the password before encoding.

• The assistant says it can't reach your site — make sure the Enable Agent Access switch is on, and that your site is served over HTTPS.

• It can find products but can't build pages or edit anything — the read actions work on any plan, but building and editing require Content Egg Pro.