Documentation
Open for Agents Docs
Practical guides for using Open for Agents as the WordPress control layer for the machine-readable web: review one canonical catalog, then publish only the understanding, discovery, and execution surfaces you intend to expose.
These are the canonical official Open for Agents documentation published by Enoki Limited. See the official identity policy.
Use the docs by phase
Discovery starts with the public surfaces agents can find. Understanding is about reviewing what those surfaces mean and validating how the active WordPress site behaves. Usage is where you publish only the read-only capabilities or reviewed workflows that should be available to agents.
Start Here
New users should begin with Getting Started to enable Standard Tools, then review Action Types and Publication Tiers before making a public publish decision. Run a discovery scan later if you need forms, AJAX routes, or plugin-specific flows.
Try the hosted demo first
Use the embedded Assistant on a real WooCommerce store, then explore the creative page-action demos and forms integration guidance before installing the plugin. No extension or API key is required.
Open demo guideStart here: Storefront Assistant
Getting Started
Start with discovery and a safe read-only baseline, then validate public behavior.
Read guideIntegrations
Compare provider detection, schema discovery, publication, execution maturity, defaults, and tested versions.
View compatibility matrixAssistant Add-on
Add a visitor-facing Assistant using the same reviewed WordPress capability catalog.
Read guideAction Types Reference
Understand what each capability means before it becomes usable by agents.
Open referencePublication Tiers
Choose which discovery and usage surfaces are public, private, or withheld.
View tiersTerminology
Use the canonical names for the product, Assistant, tools, tiers, WebMCP, and demos.
Open terminology registryFAQ
Operational answers on scans, forms, WooCommerce, compatibility, validation, and data.
Read FAQ