Eyeban

Bring your own key

Cursor-shaped proxy BYOK — your provider key, Eyeban’s Agent stack.

Bring your own key lets power users pay OpenAI, Anthropic, Google, or an OpenAI-compatible gateway directly while keeping Eyeban’s Connect Agent, tools, and prompt assembly.

How it works

1. Open Settings → Agents in the desktop app.
2. Enable OpenAI, Anthropic, and/or Google and paste the API key (keys use the OS secure store).
3. Optionally set Override OpenAI base URL for OpenAI-compatible endpoints.
4. Pick a catalog model that matches that provider.
5. Agent requests still go to api.eyeban.ir; the server calls your provider with the key for that request only and does not store the key.

What is billed where

  • Your provider bills model usage.
  • Eyeban does not debit plan or wallet credits for successful BYOK turns (usage may still be recorded at zero credits for audit).
  • You still need a signed-in Eyeban account and a plan that includes the selected model.

What BYOK does not cover

  • Cursor-pool / Composer models (Eyeban account pool)
  • Tab completions and local LSP features
  • Direct client→provider Agent mode (removed; always proxied)

Privacy

Eyeban Zero Data Retention preferences do not replace your provider’s retention policy on BYOK traffic. Prefer cloud-held keys when you need Eyeban-only key custody.

Practical tips

  • Keep Override OpenAI base URL off unless you need a gateway; it is global for OpenAI-family BYOK traffic on that profile.
  • Invalid keys fail only for that provider’s models.
  • Prefer https base URLs; http is limited to localhost.