Choose your starting point¶
Start with one working request or Agent, then use the topic guides to build it out. The tutorials assume an existing Mission Control deployment. If you are installing the services, begin with Self-hosting.
I am building an application¶
Ask your administrator for the Console URL, inference gateway URL, your Team, and an allowed generation model. You need permission to create a user key, or an ordinary service key provisioned for your backend.
- Make your first model request: create a key, discover a model, send a bounded request, and find its Trace ID.
- Call your first MCP tool if your application needs remote tools.
- Choose an integration for streaming, function calling, PydanticAI or application tracing.
You do not need to create a managed Agent to use the gateway from code. Read access concepts when choosing between a user key and service ownership.
I am building an Agent in the Console¶
Follow Build your first Agent to save a small definition and test it privately. Then review and publish for a selected Chat audience or API callers, and evaluate before expanding access.
I want to use a shared Agent¶
- Sign in using your Organization's invitation or configured identity provider.
- Open Chat and choose a deployment shared with you.
- If a tool uses a personal account, connect your own account when prompted.
A Chat consumer needs the deployment's audience grant. They do not need a developer key or Team administration role.
I administer the Organization¶
Use Set up an organization to prepare people, Teams, catalog resources and limits. The customer launch checklist gives you concrete checks and a handoff for developers and operators.
I operate the deployment¶
Start with deployment options, service configuration, and bootstrap and first sign-in. Before admitting customer traffic, verify health, backups, and upgrade recovery.
How to use these docs¶
| Section | What you will find |
|---|---|
| Get started | Short paths to a first successful result |
| Concepts | How the parts work and why their boundaries matter |
| User guide | Focused procedures for everyday development and Console work |
| Integrations | Working client and SDK examples |
| API reference | Exact endpoints, credentials, compatibility and errors |
| Administration | People, access, catalog, policy and governance |
| Self-hosting | Installation, networking, storage and operations |
Examples use fictional domains, model names and secrets. Replace them with values from your deployment. The current release states what is implemented; planned architecture lives separately.