Introduction

Tempr is three products on one account: Chat, an agent toolset inside Visual Studio and VS Code; CLI, the same agent in your terminal; and Gateway, an OpenAI-compatible API for your own provider keys. All are bring-your-own-key (BYOK) — Tempr never fronts provider tokens or takes a cut of them.

Which one do I want?

If you're not sure where to start, this should make it quick:

You want to…	Use
Chat, complete, and refactor code inside Visual Studio, VS Code, or JetBrains IDEs	Chat
Run the same agent from a terminal — one-shot prompts, a REPL, or piped into scripts	CLI
Point an existing OpenAI SDK at your own provider keys from a script, server, or app	Gateway
Get request logs, analytics, and spend visibility for API traffic outside your IDE	Gateway
Several of the above — one account and login covers them all	Any mix, one login

All three products share one account, one login at the Portal, and one Stripe customer if you're on paid plans for more than one.

How Tempr works

Every request Tempr relays — whether it starts in the IDE chat panel, at the terminal, or hits the Gateway's /v1/chat/completions endpoint — goes out using an API key you supplied for the provider you chose. Tempr never pools keys across customers and never resells tokens at a markup. What you pay for is the product wrapped around your own key: the chat UI and agent tooling for Chat and the CLI, or the virtual keys, logs, and analytics for Gateway.

Privacy

Chat never persists your code content. Gateway's request/response logging is separate, explicit, and per-account toggleable — see content capture for details.

Explore the docs

Quickstart: Chat in your IDE Install the extension, activate a license, add a provider key, and send your first message. Quickstart: Tempr CLI Install the CLI, sign in with your license key, and run your first agent turn from the terminal. CLI command reference Every tempr command, flag, REPL shortcut, and the agent tool set. CLI: Scripts, pipes & CI Headless patterns, the JSON event stream, and pipeline examples. Inline completion Ghost-text suggestions in the editor, with per-scenario model tuning. Gateway: Virtual keys cookbook Recipes for budgets, model allowlists, and instant revocation. Teams & SSO Org setup: billing, seats, SSO, and org-managed virtual keys. Quickstart: Gateway API Get a virtual key and make your first request with the OpenAI SDK in under 5 minutes. Providers & BYOK The full supported-provider allowlist and how key storage and encryption work. Agent modes & personas Interactive, Bypass, and Autopilot modes; named personas; multi-agent delegation. MCP servers Connect Model Context Protocol servers to extend the agent with your own tools. Chat Completions reference Full request/response reference for POST /v1/chat/completions.

Get help

Can't find what you're looking for? Check the general FAQ or the product FAQs (Chat, CLI, Gateway), or contact us directly.

NextQuickstart: Chat in your IDE →