Content & website
Propose the fix. A person publishes it.
Agents read published pages and prepare corrections as drafts. Publishing is a separate capability and an approval on every plan, because a website that edits itself is not an improvement.
What connects
Your website or CMS, through its API.
What crosses the boundary
- Into the agent: live page content, status, last change, and broken link reports.
- Out of the agent: drafts, awaiting a person.
- Never: published changes without approval, or deletions.
The capabilities this exposes
- Read published content
- Draft a content change
Setting it up
- 1Authorise the connection.
- 2Choose which pages or sections are in scope.
- 3Grant draft creation. Publishing stays with people.
Permissions
Read published content and create drafts. We do not request publish or delete permissions for agent use. Pages about pricing and terms can be excluded from agent scope entirely.
Jobs an agent can own once this is connected
- Find pages that contradict approved knowledge
- Draft a fix for four broken product links
- Rank improvement opportunities by measured impact
Where it stops
No agent publishes. Every change stops at a draft and needs a person, including a correction the agent is certain about. Agents also cannot alter navigation, tracking or consent behaviour, and cannot delete a page under any configuration.
Content & website
Others in this category.
Give AI a job.
Build an agent, choose what it can access, define what it may do, and deploy it to work safely across your business.
No code required · Full SDKs and API · Stop any agent instantly · [email protected]