Skip to main content
All models are served through FedRAMP and DoD IL authorized government cloud environments. All endpoints use FIPS 140-2 validated connections.

​
Model ID Format

Model IDs use a composite format: {model_name}:{compliance_level}. FedRAMP levels: DoD Impact Levels: These are two independent frameworks. Higher levels satisfy lower ones within the same framework, so a model authorized at IL5 can be requested as :il5, :il4, or :il2. A model at FedRAMP High can be requested as :fedramp-high, :fedramp-moderate, or :fedramp-low. ITAR: For ITAR / export-controlled workloads you can either append +itar to a compliance level (e.g., claude-sonnet-4-5:il5+itar), or — if you gate only on export control — request ITAR on its own with :itar (e.g., claude-sonnet-4-5:itar). The :itar form routes to the model’s ITAR-authorized provider without requiring you to name a FedRAMP or DoD IL level. A bare model name with no : suffix (e.g., claude-sonnet-4-5) is rejected with a 400 error — every request must carry a compliance level or :itar. There is no provider prefix.

​
Available Models

Filter by compliance level, ITAR authorization, and provider.

​
Embedding Models

Embedding models appear in the explorer above labelled embeddings and are served only by POST /v1/embeddings. They use the same model:level naming and the same compliance guarantees as chat models; requesting one on a chat endpoint (or a chat model on the embeddings endpoint) returns a 400 naming the correct endpoint.