DocumentationCANONICAL PUBLIC DOCUMENTATION
Build with Eventium.
Keep every boundary explicit.
Understand the platform, choose a product surface, authenticate once, and integrate through documented APIs, MCP tools, SDKs, and webhooks.
Learn the operating model
See how identity, scope, memory, orchestration, governance, and execution fit together.
Platform overview → 02 · CONNECTAuthenticate safely
Use the shared browser session for Eventium products and scoped API keys for server clients.
Authentication guide → 03 · TESTRun a real request
Select an operation from the live OpenAPI schema and inspect its exact response.
Open playground →CHOOSE A SURFACE
Products for people. Interfaces for systems.
Each surface has a focused responsibility. They share identity and governed context without collapsing into one ambiguous product.
Private chat, projects, files, schedules, agents, and memory.
OrionWork planeOrganization workspaces, channels, teams, workflows, and approvals.
ForgeCreateTurn a brief into working visual, document, and application artifacts.
ApexEngineerOpen project code, governed Gaia runtimes, version control, and validation.
MCPConnectExpose allowlisted Atlas memory operations to authorized clients.
APIAutomateUse current request contracts, OpenAPI schemas, API keys, and webhooks.
WHY EVENTIUM
More than a standalone AI tool.
| Capability | Standalone assistant | Eventium platform |
|---|---|---|
| Context over time | Conversation or tool-local history | Scoped Atlas memory with provenance and explicit no-evidence states |
| Personal and organizational work | Usually one undifferentiated workspace | Nova personal space and Orion work plane with server-enforced scope |
| Creation to engineering | Disconnected exports and manual handoffs | Forge artifact creation, Pilot experience checks, and Apex code/runtime handoff |
| Governance | Prompt conventions or app-level settings | Identity, entitlement, policy, approval, and audit controls upstream of action |
| Integration | Vendor-specific plugins | Documented REST, MCP, SDK, webhook, and OpenAPI surfaces |
Capabilities depend on the user, workspace, entitlement, and deployment. The comparison describes architectural responsibility, not a performance guarantee.
IMPLEMENT WITH THE REAL CONTRACT