Developers
Start with familiar API shapes, then use Mission Control policies to constrain models, suppliers and regions without embedding those decisions throughout application code.
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.
Create a scoped key, select a supported endpoint and make a minimal request using the published model catalogue.
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.
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.