Introduction
What EgoX is, the surfaces it exposes, and where to go next.
EgoX is a multi-tenant LLM Orchestrator. Instead of wiring an LLM, a vector
store, a tool runner, and conversation memory together yourself, you call one
endpoint — POST /egox/ask — and EgoX handles model selection, RAG retrieval, tool
calls, conversation memory, and safety rails, scoped to your project.
There are three surfaces, split by who uses them:
- The
/askAPI is the product. Your systems integrate with it — directly or via the Client SDK. - The Console is the control plane. Project owners configure models, tools, knowledge, and prompts, then monitor traffic — see Console.
- MCP is the agent plane. AI coding agents build and review your tools and knowledge in natural language — see MCP.
How it fits together
Vocabulary
The Console speaks product language; the backend speaks domain language. Both are correct — don't let one leak into the other.
| Console (user-facing) | Backend (domain) | What it is |
|---|---|---|
| Project | Tenant | Isolation unit; owns everything below it |
| AI Configuration | Tenant Config | Model, temperature, response format |
| Endpoints | Tools | External APIs the LLM can call |
| Knowledge Base | RAG Documents / Chunks | Embedded content the LLM retrieves |
| Threads | Threads + Messages | Turn history for one user session |