How the gateway enforces access
What AI2WP checks, what it records, and where its control ends.
Every routed request is checked
The gateway checks token validity, account access, destination ownership, connected status and the current domain allowance. Read-only tokens cannot write. Disconnected sites and revoked or expired credentials cannot continue through the gateway. Domain allowances are enforced on the server, not by hiding dashboard buttons.
Free conversions cannot be reset by retrying
When the ordinary free plan is enabled, it assigns one domain and reserves one conversion brief. Writes must belong to that brief and its resulting page. Creation uses a stable request identity, so retries and additional tokens cannot create a second free conversion. Early access currently requires an invitation or paid access for own-site work.
One account shares a request budget
MCP requests share an account-level rate limit, including requests using different tokens. Rotating tokens does not create a fresh request budget. Excess traffic receives a 429 response; retry later rather than repeatedly submitting the same request.
Bounded operations
The hosted gateway supports inspection, page reads, preflight, audits, draft creation and supported section/style updates. It does not offer arbitrary server commands, unrestricted plugin installation or page publication. Local custom code still needs review and authorized installation.
Evidence, not surveillance
Activity includes routed operation outcomes and short, filtered feedback reports. The platform cannot see the entire AI conversation, local files or browser session. Assistant-reported milestones are distinguished from gateway-observed events. Never send page source or secrets in feedback.
The control boundary
AI2WP regulates its own service. A website administrator can still edit WordPress directly or install other software. Self-hosted direct connections are a separate workflow and are not evidence that hosted quotas can be bypassed.