EgoZDocs
Console

Overview

The admin dashboard for configuring and monitoring an EgoZ project.

The Console is the admin dashboard for the EgoZ Orchestrator. It's where a project owner configures a project, wires up tools and knowledge, and monitors what production traffic is doing. It is not an end-user chat app — the /ask API is the product; the Console is the control plane.

Console isConsole is not
Admin dashboard for project ownersEnd-user chat interface
Configuration managementProduction traffic handler
Usage analytics & auditingCustomer-facing product
Testing / debugging playgroundReal-time conversation app

The user journey

1. Create an account
2. Create a Project (Tenant)
3. Configure it:
     • pick model & temperature
     • write system prompts
     • add tool endpoints (APIs the AI can call)
     • upload knowledge documents (RAG)
4. Test it in the Playground
5. Grab credentials           (Tenant ID + API key)
6. Integrate /ask in your own backend
7. Production traffic flows:   Your App → /ask → EgoZ Orchestrator
8. Monitor usage & cost in Analytics
9. Audit conversations in Threads

Areas of the Console

The Console has a global area (all your projects) and a project area (one project's configuration + monitoring). Each area is documented on its own page:

PageCovers
ProjectsThe projects picker, creating a project, and a project's Overview.
Agent ConfigurationLLM settings, provider keys, system prompts, personality (Your Agent), and tool settings.
Endpoints & KnowledgeEndpoints (the APIs the agent can call), the knowledge base (RAG), and extensions.
MonitoringAnalytics, Threads, Tool Health, Incidents, and Model Pricing.
PlaygroundTesting the live agent before production.
Access & MCPAPI keys and connecting external MCP clients.
Account & TemplatesAccount settings, personal access tokens, and reusable templates.

The Console is the control plane; the /ask API is the product. Everything you configure here shapes how /ask answers in production.

On this page