Providers & BYOK

Tempr is bring-your-own-key (BYOK): you add your own API key for the providers you want, and Tempr relays requests to that provider directly using your key. This applies identically to Chat and Gateway — it's the same allowlist and the same key storage underneath.

How BYOK works

There's no shared usage pool. Every model request goes out on a key you supplied, billed by that provider at their own rates. Tempr's fee is for the product wrapped around it — the IDE tooling for Chat, or the virtual keys/logs/analytics for Gateway — never a markup on tokens.

• Keys are encrypted at rest and never logged in plaintext.
• You can remove a key at any time, which immediately stops future requests from using it.
• A key can be scoped to a personal account or, on Teams, pooled at the organization level with per-member budget, rate, and model limits.

Supported providers

This is the allowlist Tempr enforces server-side today, not a wishlist. If a provider isn't listed, requests naming it are rejected before ever reaching a provider.

First-party model providers

The model creator's own API.

AI21 Labs, Aleph Alpha, Alibaba Cloud (DashScope), Anthropic, Codestral, Cohere, DeepSeek, Google Gemini, Inception Labs, Meta (Llama API), Meta AI, MiniMax, Mistral, Moonshot AI, Morph, OpenAI, Perplexity, Public AI, Sarvam AI, xAI, Xiaomi MiMo, Z.ai.

Inference providers

Hosts other companies' open-weight models on its own infrastructure.

Together AI, Fireworks AI.

Cloud providers

A cloud platform hosting first-party models under its own managed service.

AWS Bedrock, Azure OpenAI, Azure AI Foundry.

Gateways & aggregators

One key, routed to many providers and models through a single API.

OpenRouter.

Model naming

Models are addressed as provider/model (for example openai/gpt-4o or anthropic/claude-opus-4). On Gateway, GET /v1/models returns the exact set your account can currently use — see Models endpoint.

Azure OpenAI, Azure AI Foundry & AWS Bedrock

These are configured slightly differently from a plain API key, since they're cloud-hosted deployments rather than a single global endpoint:

• Azure OpenAI — you provide your resource endpoint, deployment name, and API key (or Entra ID credentials, where supported).
• Azure AI Foundry — you provide your Foundry resource endpoint, API key, and the model id(s) you've deployed (for the non-OpenAI part of the catalog — Phi, Llama, Mistral, and others; GPT models on the same resource still go through Azure OpenAI above).
• AWS Bedrock — you provide an IAM access key/secret (or role) scoped to Bedrock model invocation in your chosen region.