# Site Commander

Site Commander is a centralized command center for managing connected websites, tasks, agents, support, SEO, performance, and approvals.

Machine interfaces:
- REST discovery: /.well-known/ai-plugin.json
- REST status: /api/control-plane/status
- REST sites: /api/control-plane/sites
- REST tasks: /api/control-plane/tasks
- REST activity: /api/control-plane/activity
- REST reviews: /api/control-plane/reviews?site_id=123
- REST conversations: /api/control-plane/conversations?site_id=123
- REST messages: /api/control-plane/messages?conversation_id=123
- REST reply to review: POST /api/control-plane/reviews/reply
- REST reply to conversation: POST /api/control-plane/messages/reply
- REST ingest: POST /api/control-plane/events (message, subscription, contact, or lead)
- MCP JSON-RPC: /mcp
- Complete API guide: /api/control-plane/guide
- Central Zernio gateway: /api/control-plane/zernio/accounts, /api/control-plane/zernio/reviews, /api/control-plane/zernio/posts
- Public effects library: /effects (36 recipes, eight free MIT library starters)
- Public effects catalog: GET /api/effects, GET /api/effects/{effect_id}, POST /api/effects/compose
- MCP effects tools: sitecommander_effects_search, sitecommander_effects_fetch, sitecommander_effects_compose

Authentication uses `Authorization: Bearer <token>`. Tokens are created once by an authenticated administrator from the control-plane token action. Read operations are available through the API; changes must be proposed and approved in Site Commander.

The effects endpoints are read-only, public, and do not require command-center access. LLMs should search the catalog before writing new motion, prefer native recipes, pin third-party versions, and preserve keyboard, touch, and prefers-reduced-motion behavior.