How do I pick a Canadian route?

Select a Tier 3 Managed Cloud route from the catalog. Tier 3 requires the Northern Inference controlled path and the selected provider region to stay in Canada, and it fails closed instead of silently rerouting outside Canada.

What does it mean that Tier 3 fails closed?

If a Tier 3 request cannot be served from a Canadian-resident route, Northern Inference refuses it instead of sending it to a route outside Canada. Nothing is silently substituted.

How is the jurisdiction of a request recorded?

Each routed request has a chain-of-custody record naming the provider, region, jurisdiction and credential source Northern Inference selected, with a canonical digest and, when signing is available, Northern Inference's Ed25519 signature. It attests the route Northern Inference selected up to the provider boundary.

Which models can I route to through Northern Inference?

The live catalog lists every route: frontier models such as the Claude, GPT and Grok families and open-weight models such as DeepSeek, GLM, gpt-oss, Llama and Mistral, each with its privacy tier, jurisdiction and pricing. The catalog is authoritative; copy the exact route id from it.

Models | Northern Inference

Model Catalog

Every model currently routable through Northern Inference. Copy the Routing key into your OpenAI-compatible client (Cursor, Aider, Continue, Zed, LibreChat, LangChain, …) and POST to /v1/chat/completions. Anthropic-native clients work too: same base URL, POST to /v1/messages with native model IDs (claude-sonnet-4-5-20250929). That's the exact string you put in the model: field.

Every route below is a sovereign Canadian path or a provider-direct path to the latest frontier and open-weight models, with the jurisdiction recorded on each request. The catalog is built for government, defence, health and regulated teams, including organizations under the Controlled Goods Program, under PIPEDA.

Served today: 53 routes to 52 models, under the vendors' own names: Claude Fable 5, Claude Fable 5.1, Claude Haiku 4.5, Claude Haiku 5.5, Claude Opus 4.5, Claude Opus 4.6, Claude Opus 4.7, Claude Opus 4.8, Claude Opus 5, Claude Opus 5.5, Claude Sonnet 4.5, Claude Sonnet 4.6, Claude Sonnet 5, DeepSeek V3.2, DeepSeek-R1, DeepSeek-V3.1, DeepSeek-V3.2, DeepSeek-V4-Flash, DeepSeek-V4-Pro, Gemma 3 27B PT, GLM 5, gpt-4.1-mini, gpt-4.1-nano, gpt-4o-mini-transcribe, gpt-5.6-luna, GPT-6 Astra, GPT-6 Luna, GPT-6 Sol, GPT-6.1 Sol, gpt-oss-120b, Grok 4.6, Grok 4.7, Kimi K3, Llama 3 70B Instruct, Llama 3 8B Instruct, MAI-Thinking-1, Mistral 7B Instruct, Mistral Large (24.02), Mistral Large (24.07), Mistral Small (24.02), Mixtral 8x7B Instruct, Nova 2 Lite, Nova Lite, Nova Micro, Nova Pro, Pixtral Large (25.02), Rerank 1.0, text-embedding-3-large, text-embedding-3-small, Titan Embeddings G1 - Text, Titan Embeddings G2 - Text, Titan Multimodal Embeddings G1. Each card below carries the route's jurisdiction, pricing and exact routing key.

Loading…

Tier 3: Canadian Cloud

Managed Canadian cloud routes. Use when Canadian data residency is required.

Tier 4: Global Access

Provider-default or global routes. Use for broader model access outside Canadian residency.

How to read data residency: CA Canadian data residency (Bedrock ca-central-1 / Azure Canada East). US US-hosted routes and Bedrock us.* profiles. EU/APAC Bedrock geographic CRIS profiles stay inside their geography. Multi Global or cross-region routing. Suffixed routing keys (-ca, -us, -eu, -apac, -jp, -au, -global) make the route explicit in your dropdown.

Loading models from /api/billing/models…

Data-use posture: what each claim means

Every route can publish dated provider evidence for training, logging, retention, and the agreement that governs the request. Open Data use on a model card to inspect that route.

Training

Whether the provider commits not to use prompts and completions to train or fine-tune models.

Logging

Whether the provider logs or samples request content, including abuse-monitoring review.

Retention

How long the provider retains logged content, based on the cited route-specific evidence.

Basis

For BYOK, the customer's provider agreement governs data use; NI does not replace that agreement.