Skip to main content
Agent Autonomy is a project-level safety switch. A user must enable it in Project → Brand → API / Developer before an OAuth-connected agent can run write, generation, publishing, audit, Issue or Autopilot actions without individual confirmations.

​
Autonomous workflow

  1. List projects and select exactly one for the chat.
  2. Read Site Health, open Issues, evidence and affected pages.
  3. Modify the customer website through an independently authorized CMS, shop or repository connector.
  4. Mark only the fixed issue/page occurrences as done.
  5. Start one recheck and poll the current audit status.
  6. Treat newly detected or regressed Issues as open work.
Genseo diagnoses and verifies site and content work for AI visibility. It cannot edit an arbitrary website unless the agent also has a write-capable Webflow, Shopify, WordPress, Wix, Framer or repository connection.

​
Always excluded

OAuth-connected agents cannot use this connector to manage billing, users, team permissions, raw credentials, project creation, project deletion, or other destructive deletion actions. Connecting a new CMS and approving OAuth remain human actions. Project-bound API endpoints retain keyword, post and webhook removal for deliberate non-OAuth administration, but Autopilot cannot invoke those removals. Disabling Agent Autonomy immediately blocks subsequent OAuth write operations. Read-only inspection remains available while the OAuth grant and project membership are valid.

​
Limits

  • 30 requests per minute and 5,000 per UTC day for each OAuth connection or API key.
  • 10 write requests per minute per connection.
  • 150 requests per minute and 25,000 per UTC day across a workspace.
  • One Audit/Recheck start per project every ten minutes, six per project per day and 25 per workspace per day.
  • Monthly plan limits for Audit pages, keyword generation and AI costs still apply.
When a limit is reached, stop and honor Retry-After; do not create a rapid retry loop.