Documentation

Everything an operator or a prospect needs to run Rekkan.Ai Agent Boxes. Use the search box to jump to a section by heading.

• API contract

  Base path /api/v1. JSON only. Authorization: Bearer <accesstoken on every route except /health, /auth/register, /auth/login. Errors use FastAPI's shape: {"detail": "..."} (valid…

• Changelog

  The boxes are now provisioned on orca01 (10.172.55.3), in the LXD project Rekkan, on lxdbr0 — the same host and project that already run the platform's own instances — instead o…

• Deploy wizard

  A customer answers exactly three things. Everything else about an Agent Box is set by Rekan.Ai.

• Gateway setup — the catalog, the credentials, and what the box does with them

  The deploy wizard's third question is where the coworker talks to people, and with what credentials. That answer spans four places — the panel, the control plane, the job payloa…

• Landing page i18n — the ID EN switch at /

  The public landing page (web/landing/, served at / by rekan-api.service) is bilingual. It mirrors the control panel's approach exactly — no build step, no framework, plain ES mo…

• Library — the shared file server, with authority classes

  The Library is the platform's shared storage: the SMB file server on the storage tier, served to the operator panel over the control plane's API and to every agent box over WebD…

• Rekan.Ai Workload Packs

  A workload pack is the declarative template for one business-function agent box. It answers a single question: if a customer says "give me a finance coworker", what box do we sh…

• Roadmap — Rekkan.Ai Agent Box

  The incremental path from a working control plane to a GTM-ready product. Each version is a milestone that ships on its own: it has a goal, deliverables, and acceptance criteria…

• The Hermes dashboard inside the Rekan.Ai panel

  Every box runs the Hermes web dashboard. The panel shows it in two modes: a simple view built from the answers a business owner actually asks, and an Advanced view that passes t…