The fastest and best local API proxy service! Convert Antigravity's top AI models to OpenAI/Anthropic compatible API

中文说明 | Features | Quick Start | Architecture

Disclaimer: This project is based on reverse engineering of Antigravity. Future compatibility is not guaranteed. For long-term use, avoid updating Antigravity.

• Grok provider support - Added xAI Grok via the Grok CLI reverse proxy (cli-chat-proxy.grok.com, OpenAI Responses API), with account import, model routing, and quota-store integration alongside existing providers
• Two Grok models exposed - The standard ModelName grok-build (shown as Xbuild; this maps to the actual Grok 4.3 model, as visible inside the Grok CLI) and grok-composer-2.5-fast (Composer 2.5 Fast)
• Credential reuse - Grok credentials are imported from the local Grok CLI session (~/.grok/auth.json) and auto-refreshed; chosen to reduce account-ban risk and because community needs are still undefined (no standalone login flow is added)

• Flow + Account Routing - Custom flows for non-official models, account chains for official models
• Five Providers - Antigravity, Codex, GitHub Copilot, Zed hosted models, and Kiro
• Remote Access - ngrok/cloudflared/localtunnel with one-click setup
• Full Dashboard - Quota monitoring, routing config, settings panel
• Auto-Rotation - Account switching on 429 errors
• Dual Format - OpenAI and Anthropic API compatible
• Tool Calling - Function calling for Claude Code and CLI tools

• Import model - Anti-API reads the currently signed-in Zed.app account from macOS Keychain when you click Add Account -> Zed
• Why it differs from Codex/Copilot - Zed does not expose multiple local auth files that can be scanned in bulk; the local desktop state is effectively a single current login
• What multi-account means for Zed here - You can switch accounts inside Zed and import them one at a time into Anti-API; imported Zed accounts remain stored in Anti-API afterwards
• What is not supported - Automatic bulk discovery of many Zed accounts from one machine is not available in the same way as Codex/Copilot
• Quota monitor behavior - Zed hosted models share one monthly spend pool across the account. Anti-API currently shows hosted access status and billing period, not exact remaining dollar credits
• Credit note - Zed plan credit depends on the plan type. For example, Zed Student is documented by Zed as including $10/month in AI token credits, while standard Pro pages may show different included credit values

Two free methods to get one year of Gemini Pro:

Method 1: Telegram Bot (Quick and stable, one-time free) https://t.me/sheeridverifier_bot

Method 2: @pastking's Public Service (Unlimited, requires learning) https://batch.1key.me

# Install dependencies
bun install

# Start server (default port: 8964)
bun run src/main.ts start

Double-click start.bat to launch.

WinGet packaging is prepared in this repository. After the winget-pkgs submission is merged, the install path will be:

winget install anti-api
anti-api

After installation, anti-api starts the service directly in any terminal.

Double-click start.command to launch.

Multi-arch images (linux/amd64, linux/arm64) are published to GHCR, so most users never build locally.

docker run -d --name anti-api \
  -p 8964:8964 -p 1455-1465:1455-1465 -p 51121-51131:51121-51131 \
  -v anti-api-data:/app/data \
  ghcr.io/ink1ing/anti-api:latest

Or with Compose (pulls the prebuilt image, then runs in the background):

docker compose pull
docker compose up -d

On Windows, run the exact same commands in PowerShell. The named volume anti-api-data is managed by Docker, so there is no $HOME/path setup to get wrong.

The container can't read your local IDE credentials, so sign in via OAuth:

1. Open the dashboard: http://localhost:8964/quota
2. Click Login for a provider:
   • GitHub Copilot — easiest in Docker: enter the shown device code at https://github.com/login/device.
   • Antigravity / Codex — the panel (and docker logs anti-api) prints an Open this URL to login: ... link. Open it in your browser; the callback returns to localhost and is captured by the mapped ports.
3. When the account appears on the dashboard, point your client at http://localhost:8964 (token can be any value).

You can also log in from a terminal: docker compose exec anti-api bun run src/main.ts add-account.

Copilot uses a device-code flow and needs no callback port.

OAuth callbacks redirect to localhost, which won't reach a remote box from your laptop's browser. Either:

• set ANTI_API_OAUTH_REDIRECT_URL=http://YOUR_HOST:51121/oauth-callback and open the printed URL, or
• use Copilot (device flow, no callback), or
• SSH-forward the ports: ssh -L 8964:localhost:8964 -L 51121:localhost:51121 user@host.

The server has no authentication — do not expose these ports to the public internet. Keep them on a private network or behind your own auth/tunnel.

Accounts and routing config live in the anti-api-data named volume. To reuse data from a native install, mount your host folder instead of the named volume in docker-compose.yml:

    volumes:
      - ${HOME}/.anti-api:/app/data         # macOS / Linux
      # - ${USERPROFILE}/.anti-api:/app/data  # Windows

To import host provider credentials (Codex/AWS/Kiro/etc.) read-only, uncomment the example mounts in docker-compose.yml.

docker compose -f docker-compose.yml -f docker-compose.dev.yml up --build

• Build locally instead of pulling: docker compose up -d --build (the image already ships the toolchain for the native better-sqlite3 module).
• In-panel self-update is disabled in Docker; upgrade with docker compose pull && docker compose up -d.
• Restricted networks: ANTI_API_COPILOT_INSECURE_TLS=1 / ANTI_API_CODEX_INSECURE_TLS=1 bypass TLS verification (not recommended generally).
• ANTI_API_CODEX_REASONING_EFFORT=low|medium|high sets Codex default effort (default medium).
• Override the base image if a registry is slow: BUN_IMAGE=oven/bun:1.3.5 docker compose build.
• ngrok is bundled for Linux amd64/arm64.

• Formatting: follow .editorconfig (4-space indent, LF).
• Tests: bun test
• Contributing: see docs/CONTRIBUTING.md

Add to ~/.claude/settings.json:

{
  "env": {
    "ANTHROPIC_BASE_URL": "http://localhost:8964",
    "ANTHROPIC_AUTH_TOKEN": "any-value"
  }
}

Access the tunnel control panel at http://localhost:8964/remote-panel

Supported tunnels:

• ngrok - Requires authtoken from ngrok.com
• cloudflared - Cloudflare Tunnel, no account required, high network requirements
• localtunnel - Open source, no account required, less stable

┌─────────────────────────────────────────────────────────────┐
│                      Anti-API (Port 8964)                   │
├─────────────────────────────────────────────────────────────┤
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐      │
│  │  Dashboard   │  │   Routing    │  │   Settings   │      │
│  │   /quota     │  │   /routing   │  │   /settings  │      │
│  └──────────────┘  └──────────────┘  └──────────────┘      │
│                                                              │
│  ┌──────────────────────────────────────────────────────┐  │
│  │              Smart Routing System                     │  │
│  │  • Flow Routing (custom model IDs)                    │  │
│  │  • Account Routing (official model IDs)               │  │
│  │  • Auto-rotation on 429 errors                        │  │
│  │  • Multi-provider support                             │  │
│  └──────────────────────────────────────────────────────┘  │
│                           ▼                                  │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐      │
│  │ Antigravity  │  │    Codex     │  │   Copilot    │      │
│  │   Provider   │  │   Provider   │  │   Provider   │      │
│  └──────────────┘  └──────────────┘  └──────────────┘      │
│  ┌──────────────┐                                        │
│  │     Zed      │                                        │
│  │   Provider   │                                        │
│  └──────────────┘                                        │
└─────────────────────────────────────────────────────────────┘
                           ▼
              ┌──────────────────────────┐
              │   Upstream Cloud APIs    │
              │ (Google, OpenAI, GitHub, Zed) │
              └──────────────────────────┘

Beta Feature: Routing is experimental. Configuration may change in future versions.

The routing system is split into two modes:

• Flow Routing: Custom model IDs (e.g. route:fast) use your flow entries.
• Account Routing: Official model IDs (e.g. claude-sonnet-4-5) use per-model account chains.

This enables fine-grained control over model-to-account mapping, allowing you to:

• Load Balance: Distribute requests across multiple accounts
• Model Specialization: Route specific models to dedicated accounts
• Provider Mixing: Combine Antigravity, Codex, GitHub Copilot, and Zed in custom flows
• Fallback Chains: Automatic failover when primary accounts hit rate limits

Request
  ├─ Official model → Account Routing → Account chain → Provider → Upstream API
  └─ Custom model/route:flow → Flow Routing → Flow entries → Provider → Upstream API

No match → 400 error

1. Access Panel: http://localhost:8964/routing
2. Flow Routing: Create a flow (e.g., "fast", "opus"), add Provider → Account → Model entries
3. Account Routing: Choose an official model, set account order, optionally enable Smart Switch
4. Use Flow: Set model to route:<flow-name> or the flow name directly
5. Use Official Model: Request the official model ID directly (e.g., claude-sonnet-4-5)

Example Request:

{
  "model": "route:fast",
  "messages": [{"role": "user", "content": "Hello"}]
}

Flow Priority: Entries are tried in order. If an account hits 429, the next entry is used. Account Routing: If Smart Switch is on and no explicit entries exist, it expands to all supporting accounts in creation order.

Expose your local Anti-API to the internet for cross-device access. Useful for:

• Mobile Development: Test AI integrations on iOS/Android
• Team Sharing: Share your quota with teammates
• External Tools: Connect AI tools that require public URLs

1. Access Panel: http://localhost:8964/remote-panel
2. Configure (ngrok only): Enter your authtoken from ngrok.com
3. Start Tunnel: Click Start, wait for public URL
4. Use Remote URL: Replace localhost:8964 with the tunnel URL

Security Note: Anyone with your tunnel URL can access your API. Keep it private.

Configure application behavior at http://localhost:8964/settings:

• Auto-open Dashboard: Open quota panel on startup
• Auto-start ngrok: Start tunnel automatically
• Model Preferences: Set default models for background tasks

Codex reasoning effort support:

• Global default: ANTI_API_CODEX_REASONING_EFFORT=low|medium|high (default: medium)
• Per request (/v1/chat/completions): reasoning_effort or reasoning.effort

• Unit Tests - Core logic covered with automated tests
• Formatting Rules - .editorconfig keeps diffs consistent
• Input Validation - Request validation for security
• Response Time Logging - Performance monitoring
• Centralized Constants - No magic numbers
• Comprehensive Docs - API reference, architecture, troubleshooting

See docs/ folder for detailed documentation.

MIT

致力于成为最快最好用的API本地代理服务！将 Antigravity 内模型配额转换为 OpenAI/Anthropic 兼容的 API

免责声明：本项目基于 Antigravity 逆向开发，未来版本兼容性未知，长久使用请尽可能避免更新Antigravity。

• 新增 Grok Provider 支持 - 通过 Grok CLI 的反向代理（cli-chat-proxy.grok.com，OpenAI Responses API）接入 xAI Grok，包含账号导入、模型路由与配额体系集成
• 暴露两个 Grok 模型 - 提供的标准 ModelName 是 grok-build（面板显示为 Xbuild），但其对应的实际模型是 Grok 4.3（可在 Grok CLI 内看到）；以及 grok-composer-2.5-fast（Composer 2.5 Fast）
• 复用本地凭证 - Grok 凭证从本地 Grok CLI 会话（~/.grok/auth.json）导入并自动续期；选择该方式是为了降低账号被封禁的可能性，且社区的具体需求尚不确定（不新增独立登录流程）

• Flow + Account 路由 - 自定义流控制非官方模型，官方模型使用账号链
• 五家 Provider - Antigravity、Codex、GitHub Copilot、Zed 托管模型、Kiro
• 远程访问 - ngrok/cloudflared/localtunnel 一键设置
• 完整面板 - 配额监控、路由配置、设置面板
• 自动轮换 - 429 错误时切换账号
• 双格式支持 - OpenAI 和 Anthropic API 兼容
• 工具调用 - 支持 function calling，兼容 Claude Code

• 导入方式 - 点击 Add Account -> Zed 时，Anti-API 会读取当前 Zed.app 在 macOS Keychain 中的登录态
• 为什么和 Codex/Copilot 不同 - Zed 本地没有像 Codex/Copilot 那样可批量扫描的多账号认证文件，桌面端本质上更接近“当前单登录态”
• 这里的多账号含义 - 你可以先在 Zed 内切换账号，再逐个导入到 Anti-API；导入后的 Zed 账号会继续保存在 Anti-API 内
• 当前不支持的能力 - 不能像 Codex/Copilot 一样，直接从一台机器上自动批量发现多个 Zed 本地账号
• 额度监控说明 - Zed 的 hosted models 共用同一个月度消耗池。Anti-API 当前展示的是 hosted access 状态和订阅周期，不是精确的剩余美元额度
• Credit 说明 - Zed 的月度 credit 取决于具体计划类型。例如 Zed Student 官方说明为每月 $10 AI token credits，而普通 Pro 页面可能显示不同额度

双击 start.bat 启动。

仓库内已经补齐 WinGet 打包与 manifest 生成链路。待 winget-pkgs 合并后，可直接使用：

winget install anti-api
anti-api

安装完成后，在任意终端输入 anti-api 会直接启动服务。

# 安装依赖
bun install

# 启动服务（默认端口：8964）
bun run src/main.ts start

双击 start.command 启动。

构建：

docker build -t anti-api .

运行：

docker run --rm -it \\
  -p 8964:8964 \\
  -p 1455-1465:1455-1465 \\
  -p 51121-51131:51121-51131 \\
  -e ANTI_API_DATA_DIR=/app/data \\
  -e ANTI_API_NO_OPEN=1 \\
  -e ANTI_API_OAUTH_NO_OPEN=1 \\
  -e ANTI_API_PACKAGE_MANAGER=docker \\
  -e ANTI_API_NO_SELF_UPDATE=1 \\
  -v $HOME/.anti-api:/app/data \\
  anti-api

Compose：

docker compose up --build

开发覆盖模式（不重建，直接使用本地 src/ 与 public/）：

docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d --no-build

说明：

• OAuth 回调使用 51121-51131（Antigravity）和 1455-1465（Codex 浏览器 OAuth），请确保已映射这些端口。
• 如果运行在远程主机，请将 ANTI_API_OAUTH_REDIRECT_URL 设置为公网地址，例如 http://YOUR_HOST:51121/oauth-callback。
• 挂载 ~/.anti-api 后，Docker 会复用本地账号和路由配置。
• 本地导入类 provider 默认看不到宿主机凭据；如需导入，请按 docker-compose.yml 里的注释示例挂载 .codex、.cli-proxy-api、.aws、Kiro CLI 或 Amazon Q 目录。
• 设置 ANTI_API_NO_OPEN=1 可避免容器内尝试自动打开浏览器。
• Docker 内禁用面板自更新，请使用 docker compose up -d --build 重建或拉取镜像更新。
• 如果受限网络下 Copilot TLS 失败，可设置 ANTI_API_COPILOT_INSECURE_TLS=1（不建议常规使用）。
• 如果受限网络下 Codex TLS 失败，可设置 ANTI_API_CODEX_INSECURE_TLS=1（不建议常规使用）。
• 可通过 ANTI_API_CODEX_REASONING_EFFORT=low|medium|high 设置 Codex 默认推理强度（默认 medium）。
• 如果 Docker Hub 不稳定，默认基础镜像已使用 GHCR；可用 BUN_IMAGE=oven/bun:1.3.5 覆盖。
• 镜像内已为 Linux amd64/arm64 安装 ngrok。

• 格式规范：遵循 .editorconfig（4 空格缩进、LF 行尾）
• 测试：运行 bun test
• 贡献指南：参考 docs/CONTRIBUTING.md

┌─────────────────────────────────────────────────────────────┐
│                      Anti-API (端口 8964)                   │
├─────────────────────────────────────────────────────────────┤
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐      │
│  │   配额面板   │  │   路由配置   │  │   设置面板   │      │
│  │   /quota     │  │   /routing   │  │   /settings  │      │
│  └──────────────┘  └──────────────┘  └──────────────┘      │
│                                                              │
│  ┌──────────────────────────────────────────────────────┐  │
│  │              智能路由系统                             │  │
│  │  • Flow 路由（自定义模型 ID）                         │  │
│  │  • Account 路由（官方模型 ID）                        │  │
│  │  • 429 错误自动轮换                                   │  │
│  │  • 多提供商支持                                       │  │
│  └──────────────────────────────────────────────────────┘  │
│                           ▼                                  │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐      │
│  │ Antigravity  │  │    Codex     │  │   Copilot    │      │
│  └──────────────┘  └──────────────┘  └──────────────┘      │
│  ┌──────────────┐                                        │
│  │     Zed      │                                        │
│  └──────────────┘                                        │
└─────────────────────────────────────────────────────────────┘

测试功能：路由系统为实验性功能，配置格式可能在未来版本中变更。

路由系统拆分为两种模式：

• Flow 路由：自定义模型 ID（如 route:fast）使用流配置
• Account 路由：官方模型 ID（如 claude-sonnet-4-5）使用账号链

由此实现模型到账号的精细控制：

• 负载均衡 - 将请求分发到多个账号
• 模型专用 - 指定模型使用专用账号
• 混合提供商 - 组合 Antigravity、Codex、Copilot、Zed
• 自动降级 - 账号触发 429 时自动切换下一个

请求
  ├─ 官方模型 → Account 路由 → 账号链 → 提供商 → 上游 API
  └─ 自定义模型/route:flow → Flow 路由 → 流条目 → 提供商 → 上游 API

无匹配 → 400 错误

1. 访问面板: http://localhost:8964/routing
2. Flow 路由: 创建流（如 "fast", "opus"），添加 提供商 → 账号 → 模型 条目
3. Account 路由: 选择官方模型，配置账号顺序，按需开启 Smart Switch
4. 使用流: 设置 "model": "route:<流名称>" 或直接使用流名
5. 使用官方模型: 直接请求官方模型 ID（如 claude-sonnet-4-5）

Flow 顺序：按配置顺序尝试，429 时切换下一个。 Account 路由：Smart Switch 开启且未配置条目时，按账号创建顺序自动展开。

将本地 Anti-API 暴露到公网，支持跨设备访问：

• 移动开发 - iOS/Android 测试 AI 集成
• 团队共享 - 与队友共享配额
• 外部工具 - 连接需要公网 URL 的 AI 工具

1. 访问面板: http://localhost:8964/remote-panel
2. 配置 (ngrok): 输入 ngrok.com 的 authtoken
3. 启动隧道: 点击启动，等待公网 URL
4. 使用远程 URL: 用隧道 URL 替换 localhost:8964

安全提示: 任何人拥有隧道 URL 即可访问您的 API，请妥善保管。

访问 http://localhost:8964/settings 配置：

• 自动打开面板: 启动时打开配额面板
• 自动启动 ngrok: 自动启动隧道
• 模型偏好: 设置后台任务默认模型

Codex 推理强度支持：

• 全局默认：ANTI_API_CODEX_REASONING_EFFORT=low|medium|high（默认 medium）
• 单次请求（OpenAI /v1/chat/completions）：reasoning_effort 或 reasoning.effort

• 单元测试 - 核心逻辑完整测试
• 输入验证 - 请求验证保障安全
• 响应时间日志 - 性能监控
• 常量集中管理 - 无魔法数字

详细文档见 docs/ 文件夹。

MIT