How-to Guides
How to Let AI Help Operate Your Content
gcms does not call an AI API itself. It gives AI tools a controlled interface: key, OpenAPI, assistant guide and scoped write access.
Letting AI help with content operations does not mean handing over your admin account. gcms exposes a limited interface for posts, pages and links, and each external tool gets its own access key.
Step 1: Create one key per tool
Go to Settings → Automation API and create an access key. Use a clear name, such as Content Assistant or SEO Draft Assistant. If you stop using that tool, revoke only that key.
Step 2: Grant only necessary scopes
Start with read and draft-write access. Do not grant publish permission by default. Let AI create drafts, improve titles, excerpts, keywords and structure; keep final review and publish in the admin.
Step 3: Download the AI package
The full key is shown once. After creating it, download the dedicated AI package. It includes OpenAPI, env examples, assistant instructions and a helper script. Give that package to Codex, Claude Code, Cursor or another compatible tool.
Step 4: State the boundaries
A good instruction is explicit: list posts first, find the target ID, only edit drafts, improve SEO descriptions, never delete content, and summarize changes for review before publishing. The important part is not only what AI can do, but what it must not do.
Step 5: Clean up access regularly
One key should serve one tool or workflow. Revoke it when a project ends, a member leaves, or you suspect exposure. gcms records recent use so stale keys are easy to spot.
AI is good at repetition, organization and drafts. Judgment should stay with people.