Two tiers, one table
The page is one flat table of models, not a tab per tier. Each row is a model with its provider,
who manages it, its upstream model id, its spend, its usage, and its status — so the tier is just a
column you can sort and filter by. A registered account with no models yet still gets a row, so it
is visible rather than something you have to remember exists.
Above the table sits the workspace’s gateway budget. That strip is the only place the managed tier’s
account-level numbers appear.
Bringing your own provider
Supported providers are OpenAI, Anthropic, Azure, Bedrock, Vertex AI, Gemini, Mistral, Groq, DeepSeek, OpenRouter, Together AI, xAI, Cohere, Ollama, Baseten, Nebius Token Factory, and a hosted vLLM endpoint.1
Credential
Name the account and supply its API key. The key is stored so model discovery can authenticate
with it later.
2
Models
Register one or more upstream model ids against that credential. Nothing is written until this
step submits — the credential is created, then each model against it, as one action.
3
Verify
Each new deployment is health-checked, and you can talk to it directly to confirm it answers.
Registering your own provider does not replace the managed tier — both stay callable, and an agent
picks a model from either.
Next steps
Credentials & secrets
How a provider key is stored and delivered to a run.
Agent spend & attribution
What the fleet costs, attributed per run, agent, and model.
Model Evaluation
Decide whether a model is good enough for a given job.
Build from scratch
Where an agent picks the model it runs on.