Direct

A request to a provider marked Direct goes from your browser straight to the provider, and never reaches our server.

Your browser talks directly to the provider, using your own API key. Our server is not part of that exchange — it doesn't relay your message, doesn't log it, and cannot read it. This isn't a policy promise: the request never reaches us, so there is nothing to trust us about. Currently, the providers that go directly are OpenAI, Anthropic, Google, DeepSeek and xAI.

What goes where

• Your messages and attachments go from your browser straight to the provider's API over HTTPS. Every request to it — chat, image generation, voice transcription, even testing a new key — is made the same way.
• Your API key is sent from your browser to its provider and to no one else. Our server never receives it.

Check it yourself — two minutes

1. Open your browser's developer tools (F12, or right-click → Inspect) and select the Network tab.
2. Filter by Fetch/XHR, then send a message to a Direct provider.
3. Look at the request that carries your message: its destination is the provider's own domain — api.openai.com, api.anthropic.com, generativelanguage.googleapis.com, api.x.ai or api.deepseek.com — not ours.

Some providers can't be called from a browser. They go through our proxy instead.