Getting started
Understand the model, boot the stack, and send your first authenticated request.
Implemented Ledger class: shipped-local
Verified 2026-10-21
This section takes you from zero to a verified local request without hiding the parts that are still provisional.
Recommended order
- Introduction — what the platform is and what runs today.
- Concepts — organizations, agents, PATs, sessions, memory, and context.
- Quickstart — boot dependencies and send a mock completion.
- Local development — run services from source and know which ports they use.
- FAQ — short answers to the questions people ask first.
“Implemented locally” does not mean hosted, HA, or production-ready. The platform has real auth, tenancy, and proxy code, but the production gates in Production readiness are still open.
What you need
- Go 1.25+ and GNU Make for the Go services.
- Python 3.12+ with
uvfor the Python services. - Docker Compose v2 for PostgreSQL, Redis, ClickHouse, and MinIO.
- No provider key for mock mode. Live mode requires an OpenAI, Anthropic, or self-hosted endpoint.
What success looks like
A successful mock chat request proves that:
- The proxy parsed your bearer PAT and called auth over gRPC.
X-IBEX-Agent-IDbelongs to the token's organization and is active.- Rate limiting and request validation admitted the call.
- The model resolved to a registered provider.
- The response passed back through the proxy with correlation headers.
It does not prove that memory, context assembly, billing, or production recovery work. Those are separate surfaces with separate evidence.