Model Catalog
Providers, models, and the
@provider/model slug you use in codeGateway Models
The models the AI Gateway serves and how they are named
Getting models into the catalog
An Integration connects the AI Gateway to a provider — OpenAI, Anthropic, Bedrock, or a self-hosted endpoint. Creating one is what puts that provider’s models in the catalog, and it is also where you decide which workspaces see them and what they are allowed to spend.LLM Integrations
Create an Integration and connect a provider
Custom Models
Add models the AI Gateway does not know about yet
Tuning what the catalog reports
Pricing and model metadata come from the provider by default. Where your contract differs, or where a model behaves differently in your deployment, override it.Pricing Adjustments
Apply your negotiated rates so cost reporting is accurate
Model Overrides
Change token limits, capabilities, and other model details
Related
- Workspace Provisioning — which workspaces get an Integration
- Model Provisioning — which models within it they may call
- Budget Limits and Rate Limits — the guardrails on that access
- Bedrock with an assumed role — AWS-specific setup

