Via our proxy

A request to a provider marked Via our proxy passes through our server, which forwards it unchanged and keeps nothing.

Used for a provider that can't be called from a browser — because its servers refuse browser requests, or for another technical reason. Your browser sends the request to our server instead, which forwards it to the provider as it is and streams the answer back. Currently, the provider that goes through our proxy is Z.ai.

What goes where

• Your messages and attachments go from your browser to our proxy, /api/proxy/<provider>/… on our own address, over HTTPS. The proxy forwards them to the provider unchanged and streams the answer back. Every request to that provider — chat, image generation, voice transcription, even testing a new key — goes this way.
• Your API key travels with the request, through the proxy, to its provider. The proxy uses it for nothing else.
• The proxy doesn't store your key or your messages, and doesn't write them to any log. Before forwarding, it removes your Polymeti login cookies, so the provider never receives your session. Only signed-in users can use it, and it can reach only the providers on a fixed list.
• Each answer that went through the proxy says so in its details, under "Connection".

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 provider marked Via our proxy.
3. The request that carries your message goes to our own address, at /api/proxy/<provider>/…: that is the proxy. Its answer is the provider's, passed back unchanged.

Wherever a provider allows it, your messages go directly instead.