Automation & AI agents

Octa Editor is built so an AI agent or a script can read and write content safely, using the same rules a human does.

Surfaces for automation

An agent has three ways in.

• REST API. The full read and write surface, authenticated with Application Passwords. See REST API overview.
• Abilities (MCP). A native WordPress surface that exposes reading and writing as callable abilities. See Abilities and MCP.
• Bulk import with an agent guide. For batch content, the Add content page ships a downloadable guide that documents the exact JSON rules. See Bulk import.

All three go through the same pipeline, so identity, validation and warnings behave identically.

The safety model

Three rules make automated editing predictable.

• Dry-run first. Send "_dry_run": true to preview any write with zero database changes, then send it again without the flag to commit. See Dry-run, strict & warnings.
• Strict on write. Add "_strict": true so any warning fails the write rather than silently dropping a value. Recommended for unattended automation.
• Never guess identity. A failed match returns a precise error instead of overwriting the wrong record or creating a duplicate. See Record identity.

A typical flow

1. Read a pattern record (or export one from the bulk page) to learn the exact fields shape.
2. Produce the new document, keeping the pattern shape and changing only values.
3. Send it with _dry_run and read the warnings.
4. Fix anything the preview flags, then send again to write.