API key proxy for AI agents: use keys without exposing them

• A placeholder, never the key

  Only a placeholder reaches the agent. The real key stays in a separate, dedicated key service and is swapped in only on the way out to the provider.

• Handed-back secrets are caught too

  Any new secret a provider hands back, a freshly created token for example, is stored the same way. The agent only ever sees a placeholder for it too.

• Providers

  The docs name Cloudflare, Tailscale and Stripe as examples.

• Read-only first

  New keys start read-only. Pick a template, for example “DNS for one zone”, to grant more, or switch on full access with a passkey confirmation.

• Payments wait for you

  Outside full access, payments and orders always wait for your approval. Under full access they go through without asking.

• A passkey comes first

  You register a passkey before your first key. It guarantees that access can only be widened with your confirmation, never by the app alone.

• Lock a key at once

  Lock a key from the panel. A locked key stops working everywhere at once.

• What it stores

  The vault holds credentials the AI needs, such as a deploy token or a database password, and you attach them to a chat. Values are encrypted at rest and never returned to the browser after saving.

• What it does not control

  When a chat uses a saved credential, that information may be included in the content sent to the selected AI provider. Review the provider’s data-handling terms before attaching sensitive credentials.

• Only on a confirmed route

  A chat with an attached credential runs only on a route whose zero-data-retention commitment is confirmed. For Featherless that is the provider’s written commitment of 28 September 2026, which ZeroLog cannot enforce technically. On any other route the request is refused and nothing is sent.

• Your own provider key

  With your own AI provider key, requests go straight to that provider and its retention terms apply. ZeroLog does not guarantee zero data retention by third-party providers.

• Containers with their own VPN

  They do not go through the key service and cannot use keys stored here. This is enforced technically: such a workspace never receives key-service trust or secrets.

• Sites hosted elsewhere

  A site hosted elsewhere reads its own code, including anything embedded in it. Prefer a key limited to what that site actually needs.

Details: Key proxy, Secrets vault, Isolation, Bring your own key.

• Can an AI agent read my API key?

  Not with the key proxy. The agent only sees a placeholder, and the real key stays in a separate key service until the request leaves for the provider. You can lock a key from the panel at any moment, and it then stops working everywhere at once, for every agent.

• Which providers does the key proxy support?

  The docs name Cloudflare, Tailscale and Stripe as examples. A new secret a provider hands back, such as a freshly created token, is caught and stored the same way, so the agent only ever sees a placeholder for it too. The docs promise no complete list, so check them for a provider that is not named.

• Is the secrets vault safe with AI providers?

  The vault encrypts values at rest and never returns them to the browser after saving. It does not control what a provider does with content a chat sends. When a chat uses a saved credential, that content can reach the selected AI provider, so check the provider’s terms first.

• What can an agent do with a new key?

  Less than you might expect. A new key starts read-only. You choose a template, such as DNS for one zone, to grant more, or confirm full access with a passkey. Outside full access, payments and orders wait for your approval, and you can lock the key at any moment.

• Swiss AI workspace

  Chat with many models and a Linux container in one account.

• /goal and /ultracode

  Agents that keep working on the server, and what stops their spending.

• AI coding agent with a persistent workspace

  Files, snapshots, jobs and schedules that outlast a chat.

• Cloud development environment in Switzerland

  Where your files, your container and the model calls live.