Works with the AI tools your team already uses. One setting each.
Claude Code, Codex, Cursor, Copilot and your own apps reach Tempr by changing a base URL and a key. Bring keys from 34 providers, connect your MCP servers once, sign in through your identity provider, and send logs to the tools you already watch.
Everything Tempr connects to.
Each card opens its setup guide.
Coding tools 11
Point the coding agents and editors your team already runs at Tempr. Requests, costs and guardrails then cover all of them, and most guides also add the Gateway's own MCP server.
AI plans 3
Keep the plans your team already pays for. The plan pays for each request, and Tempr governs it.
Apps and APIs 6
Your own apps keep their SDK. Only the base URL and the key change.
MCP 6
Connect your MCP servers to Tempr once, then use them from any app, under your Tool Packs and guardrails. The Gateway has an MCP server of its own, too.
Models and providers 3
Bring your own keys. Tempr calls each provider directly, on your key.
Identity 2
Sign-in and membership come from the directory you already run.
Logs and alerts 4
Send what happens in Tempr to the tools your team already watches.
Tempr's agents 4
Tempr's own agent installs into the editors your team uses.
Your AI agent, your identity provider, your log tools, your alerts.
Ask an AI agent about your Gateway.
Claude Code, Codex, claude.ai and ChatGPT can read your usage and cost, request logs, keys, plan and provider health through the Gateway's own MCP server. If you allow it, an agent can make changes that only tighten, and propose the rest for you to approve in the Portal.
- Sign in through the app, or use a management key
- Changes that only tighten: a lower budget, fewer models, a revoked key
- Anything that loosens waits for a person's approval
- Gateway Pro, Scale and Enterprise
get_usage_summarytighten_key · propose_key_changeSign in the way you already do.
Members sign in through your identity provider, and directory sync adds and removes them as your directory changes. Owners can require SSO for every account on your domain.
- SAML or OIDC, with Okta, Entra ID or Google Workspace
- Members added and removed with your directory
- Directory groups mirrored, with their own Tool Packs and budgets
Your logs, in the tools you already watch.
On the Enterprise plan, an organization streams its request logs, agent traces and audit log as they happen, to up to five destinations.
- OpenTelemetry over OTLP/HTTP, so any backend that takes it works
- Langfuse and Opik, set up from their own keys
- The audit log as signed webhook batches
Alerts where your team will see them.
Budget alerts, rule warnings and changed MCP tools arrive by email and as webhooks, each signed so you can check it came from Tempr.
- Budget and rule alerts by email and webhook
mcp.tool_changedwhen a server changes a toolx-tempr-webhook-signature, an HMAC-SHA256 of the body
{ "event": "gateway.alert.triggered",
"data": { "name": "Checkout latency",
"valueText": "3,180 ms" } }
Two lines change. The rest of your code doesn't.
Model names carry their provider, so one key reaches every model on your allowlist.
# pip install openai from openai import OpenAI client = OpenAI( base_url="https://api.temprhq.io/v1", api_key="tvk_...", ) response = client.chat.completions.create( model="anthropic/claude-sonnet-5.5", messages=[{"role": "user", "content": "Say hi"}], )
// npm install openai import OpenAI from "openai"; const client = new OpenAI({ baseURL: "https://api.temprhq.io/v1", apiKey: process.env.TEMPR_API_KEY, }); const response = await client.chat.completions.create({ model: "google/gemini-3-flash-preview", messages: [{ role: "user", content: "Say hi" }], });
# any tool that reads OpenAI's environment variables export OPENAI_API_BASE="https://api.temprhq.io/v1" export OPENAI_API_KEY="tvk_..." aider --model openai/anthropic/claude-sonnet-5.5
About integrations.
My tool isn't listed. Will it work?
Most likely. A tool that lets you set an OpenAI-compatible or Anthropic-compatible base URL and an API key can use Tempr: point it at https://api.temprhq.io/v1, or at https://api.temprhq.io for tools that speak the Anthropic API, and give it your Tempr key.
Do I have to change my code?
Only the base URL and the key. Requests and responses keep the shape your SDK expects, and model names carry their provider, like anthropic/claude-sonnet-5.5.
Can an AI agent change our Gateway?
Only if you allow it, with the Changes by AI agents switch. An agent connected to the Gateway's MCP server can then make changes that only tighten, like a lower budget or a revoked key. Anything that loosens, and your account's own settings, it can only propose: you approve or decline each one in the Portal.
Which integrations need a paid plan?
Coding tools, AI plans, SDKs and your own provider keys work on every Gateway plan, Free included. The management API and the Gateway's MCP server come with Pro and up, SSO and directory sync with Teams and Gateway Enterprise, and log streaming with Enterprise.
Point one tool at Tempr today.
Start with the one your team uses most. The others take one setting each.