Zerokey

Quick Start ·
  API Docs ·
  llms.txt ·
  Landing Page

ZeroKey

OpenAI-compatible local AI proxy for DeepSeek, Claude, ChatGPT, Qwen, and Inception (Mercury) — use your own browser sessions and your own credentials to connect your own accounts with VS Code (Chat), Terax, or OpenCode. Personal use only. Just paste a fetch() call from DevTools. ZeroKey does not provide shared accounts, API access, or commercial access to third-party services.
Why DeepSeek uses a real browser. DeepSeek's direct HTTP API is aggressively
flagged during their ban waves. In testing, 7 different accounts were tried
across multiple workarounds — each was banned three separate times before
a single account survived. Switching to the browser transport (a real Chromium
profile driven via Playwright, talking to chat.deepseek.com through its own
web UI) has been stable ever since: 2M+ tokens consumed across two
accounts with no bans.
The tradeoff: ZeroKey is no longer a lightweight proxy for DeepSeek. The
browser transport launches a full Chromium instance per user profile
(temp/profiles/deepseek//). This is intentional — the browser is
what makes the session survive.
Is it safe? How do I start? See llms.txt for a short, machine-readable summary, or the landing page.
Heads up: ZeroKey is per-session — one server process is pinned to the session picked at
startup. Switching sessions or opening a new chat window in your IDE does not refresh which
session ZeroKey talks to; restart the server and re-select to pick up a different session.
Using ZeroKey: on first message, model reads the target
project's AGENTS.md (if present) for context. Built-in tools (read, write, replace,
ls, mkdir, glob, grep, cmd, cmd_bg, cmd_poll, cmd_kill, fetch, errors,
todos_add, todos_set, ask) and any MCP tools registered…