Warp adds BYOK to Warp Agent with OpenAI-compatible endpoints

• Warp says Warp Agent now accepts user-supplied API keys and inference endpoints, and that using your own key no longer requires a paid plan, according to warpdotdev's launch post.
• warpdotdev's setup demo says BYOK currently supports OpenAI, Anthropic, and Gemini keys, with configuration exposed in Warp settings.
• warpdotdev's endpoint thread adds support for endpoints that implement the OpenAI Chat Completions API, including OpenRouter, LiteLLM, Z.ai, and DeepSeek.
• The linked Warp BYOK docs and custom endpoint docs put the change in writing, while OpenRouter's reply shows at least one provider promoting day-one support.

You can jump straight to Warp's BYOK documentation, check the custom endpoint page, and watch Warp's settings walkthrough plus its OpenRouter and DeepSeek demo to see how the routing works in practice.

Warp's core change is simple: inference access for Warp Agent no longer has to flow through Warp's own paid plan if the user brings their own credentials. warpdotdev's launch post states that directly, and the companion setup clip shows the keys being added from Warp settings.

The provider list is narrow but practical on day one:

• OpenAI, per warpdotdev's BYOK thread
• Anthropic, per warpdotdev's BYOK thread
• Gemini, per warpdotdev's BYOK thread

That makes this a pricing and control update as much as a feature update. Users can keep the Warp Agent UI while pointing it at accounts they already manage.

Warp did not stop at first-party keys. According to warpdotdev's endpoint thread, Warp Agent can also connect to inference endpoints that follow the OpenAI Chat Completions API.

The examples Warp named in the launch thread were:

• OpenRouter, per warpdotdev's endpoint thread
• LiteLLM, per warpdotdev's endpoint thread
• Z.ai, per warpdotdev's endpoint thread
• DeepSeek, per warpdotdev's endpoint thread

That matters because it turns Warp Agent into more of a routing surface than a single-vendor assistant. The demo in Warp's second clip specifically walks through connecting DeepSeek and OpenRouter, while the linked custom endpoint docs document the endpoint path.

The fastest ecosystem response came from OpenRouter's post, which immediately advertised that it was now supported inside Warp.

User reaction also started showing up outside English-language launch chatter. dingyi's post simply called out that Warp finally supports BYOK, which is a small signal that the feature request had been hanging around long enough to make the ship itself notable.