Developers
Start with a familiar API shape, choose the interface that matches your workload, and use Mission Control policies to constrain models, suppliers and regions without embedding those decisions throughout application code. This public page explains the path; setup happens after sign-in.
POST /v1/chat/completionsmodel "selected-id"region "allowed"Capabilities and boundaries
Each capability below describes its operating scope so technical and commercial teams can evaluate the same proposition.
Use the endpoint family that matches the client you already run. The guide and API reference provide the exact request shapes after you sign in.
After sign-in, create a scoped key, choose a supported model and run the smallest useful request. The onboarding guide walks through the steps and the success signal.
Name a model directly or opt in to supported chat autorouting. Credential controls remain authoritative over eligible choices.
Use response metadata, request logs and usage reporting to understand what ran and what it cost. Keep the request ID with your application run when troubleshooting or reviewing spend.
Move the same workload from a personal test to a governed team service by putting access, budget and supplier decisions in the control plane.
Build resources
Use the maintained API references and practical guide for current request formats, authentication and supported model identifiers.
Make the next decision concrete
Review workload, control, spending, location and integration requirements with our team.