BYOAIK — Bring Your Own AI Key: a directory of AI tools that run on your own API key.

Warp

Agentic terminal / development environment with an AI agent built into the shell, supporting your own provider API keys.

Website Source code

Category:

Developer Infrastructure

Pricing:

Freemium

Open source:

Yes (AGPL-3.0 (client); MIT (warpui_core/warpui UI crates); cloud backend proprietary)

Self-hostable:

No

Local-first:

No

Platforms:

Desktop, CLI

AI providers (bring your own key):

OpenAI, Anthropic, Google Gemini, OpenRouter, Custom / OpenAI-compatible

API key storage:

Stored locally on device

Key risk level:

LOW

Trust score:

90/100

Warp is a Rust-based, AI-native terminal that has evolved into an "agentic development environment." Its built-in AI agent can run commands, debug, and orchestrate multi-step work directly in the shell, with MCP support. Founded in 2020 by Zach Lloyd (ex-Google). Warp confirms BYOK: in Settings > AI users add their own OpenAI, Anthropic, or Google API key, or configure a custom inference endpoint compatible with the OpenAI Chat Completions API (examples given: OpenRouter, LiteLLM, z.ai, internal gateways, self-hosted). Keys are stored only on the user's device (OS keychain) and used in-flight by Warp's agent backend, never persisted on Warp servers; BYOK requests are billed by the provider directly and do not consume Warp credits. As of May 21, 2026, BYOK is available on every plan including Free, for individuals and orgs with 10 or fewer employees (larger orgs need Business/Enterprise). Note: the candidate's "closed-source" label is outdated. In April 2026 Warp open-sourced its terminal client and Oz cloud-agent orchestration platform (AGPL-3.0, with the warpui_core/warpui UI crates under MIT) at github.com/warpdotdev/warp (~62k stars); however the broader agent harness backend and cloud services like Warp Drive remain proprietary, so it is a hybrid open-core/freemium model. Platforms: macOS (mature), Linux (production), Windows (preview).

How your API key is handled

Your API key is stored locally on your device. Requests are sent directly to the AI provider.

Setup

Open settings, paste your provider API key, choose a model, and start — the key stays on your device.