API OVERVIEW
The API is split into small endpoints so it can grow without turning into a single monolith. Public routes expose status, logs, and docs data. Admin routes stay behind login and CSRF checks.
Responses are documented as plain text and code blocks here, not as clickable links, so the page reads like API docs instead of navigation.
API STATUS
| Status | Online |
| Version | beta |
| Base URL | /api |
| Authentication | public for status/logs, session-based for admin |
| Rate limit | deployment and admin actions are gated by server controls |
ENDPOINTS
Returns the current runtime snapshot, including uptime, branch, commit, memory, and deployment state.
Returns the current log snapshot as plain text lines. ANSI escape sequences are preserved for colour-aware rendering.
Authenticated summary for the admin dashboard. Includes status, command usage, recent logs, and feedback previews.
Accepts control actions such as start, stop, restart, refresh, and redeploy after CSRF verification.
EXPANSION
The endpoint surface is intentionally modular. New read-only routes can be added beside status and logs, while admin actions can stay behind the same session and CSRF model.
{
"ok": true,
"data": "extend with new endpoint groups as the bot grows"
}