Get Started
Overview
What getting started looks like, and the path from zero to a grounded answer.
Getting started has two halves:
- Set up a project — sign up, create an organization, and create a project. Creating a project provisions a dedicated engine instance for you (its own container, volume, and graph). This takes a few seconds.
- Put knowledge in and ask — add a source, compile it into claims, then ask a question in the Playground or from your own AI tool over MCP.
No fabrication, by design
Until you compile a source, the graph is empty — and the engine will tell you it has nothing rather than invent an answer. Empty state is real state.
The shape of a project
Every project gives you:
- A dedicated engine — single-tenant, isolated at the container boundary. Nothing is shared with other projects.
- An auto-minted Console key — the Console mints a session-scoped
tr_sk_…key (console-<user>-<timestamp>) so its tabs can talk to your engine immediately. For your own apps and AI tools, you create your own keys in the API Keys tab. - A pre-filled MCP URL — ready to paste into Claude Code, Cursor, or any MCP client.