BYOAIK (Bring Your Own AI Key) is 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.
- Category:
- Developer Infrastructure
- Maintenance:
- Actively developed (last commit yesterday)
- 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:
- 78/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).
Why this trust score (78/100)
Trust measures how the tool treats your API key and how much of that has been verified. It contains no popularity signal.
- Key Safety 23/25: The key is held on your own device.
- Request Routing 17/20: Requests go straight from you to the AI provider.
- Transparency 20/20: Source is public under AGPL-3.0 (client); MIT (warpui_core/warpui UI crates); cloud backend proprietary, so anyone can check how the key is handled.
- Privacy 7/15: Nothing specific is known about its data handling beyond the key itself.
- Maintenance 10/10: Actively developed: commits within the last three months.
- Verification Confidence 1/10: Compiled from public documentation by an AI-assisted pass, not independently confirmed.
What was checked
Verification tier RESEARCH_ASSISTED, derived from the evidence below and not set by hand.
- [REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
- [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-15, about 0 month(s) ago. source
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.