Hand Repetitive Ops to Automation

Content operations have repetitive work: syncing links, drafting posts, filling SEO descriptions, updating pages in batches. gcms exposes language and category reads plus posts, pages and links through controlled APIs so automation can handle the chores.

Scoped API keys

Issue keys from the admin, grant scopes by posts, pages and links, revoke anytime, and see when each was last used. A key is shown in full once at creation; only its hash is stored — lost one? Revoke and reissue.

A standard description

It ships an OpenAPI description and call logs, so wiring up any HTTP client, webhook or automation platform is straightforward — and every write is traceable.

A skill package for AI

Export a 'skill package' that describes the site's publishing capabilities to an AI assistant — so it can draft, fill in SEO and schedule posts by your rules.

No AI API required

gcms does not call an AI model for you. It provides public docs, an OpenAPI description and an assistant package. Give those files to Codex, Cursor, Claude, ChatGPT or an automation tool, and they can operate the site over HTTP. Your source repo stays private, and a site key can be revoked whenever the boundary changes.

Permission boundary

Only languages, category reads, and content operations for posts, pages and links are exposed by default — not themes, security, users, system settings, or category writes. Use one key for one tool or one workflow; revoke what you stop using, and regenerate anything you suspect has leaked.

Hand the repetitive work to automation; keep the judgment yourself.