Key proxy for third-party keys
Store an API key for a third-party provider (Cloudflare, Tailscale, Stripe, and others) and agents in your chats can use it without ever seeing the real value. Only a placeholder reaches an agent; the real key stays in a separate, dedicated key service and is swapped in only on the way out to the provider.
Figure as text
- The agent in your workspace sends a request. Where the key belongs, it carries a placeholder: a hollow ring.
- The egress broker stamps the request with the user and container it came from.
- At the key service, the destination host picks the provider's profile, and the drawer for that profile opens.
- A request the key's rule does not allow is pushed onto the return belt. The agent gets a 403.
- Payments and unknown operations wait under the lamp until you approve them with the lever. Without an answer they end as a 403. In the demo, the lever pulls itself after a moment.
- For allowed requests, a head swaps the placeholder for the real key. The request goes only to that provider's door.
- The response returns on the second belt. A second head swaps any key value in it for a placeholder before it reaches the agent.
- Three gauges count refused requests, requests that reached the provider, and payments you approved. The readout also counts real keys the agent has seen. It stays at 0.
Diagram as text
- The agent in your workspace sends its request to the egress broker. Where the key belongs, it carries a placeholder.
- The broker hands the request to the key service with a preamble, signed with a shared secret, that names the user and the container. A preamble outside a 30 second window, or with a wrong signature, is refused.
- The key service rejects ambiguous requests: path tricks, method overrides, duplicate headers.
- It picks the provider profile from the destination host, not from anything the caller says.
- The placeholder must belong to you, to this profile and to this container.
- It classifies the operation by method and path and checks it, and the resources in the path and body, against the rule on your key.
- Allowed operations continue. Known but disallowed operations get a 403. Unknown operations, and payments unless the key has full access, wait for your approval, held for 60 seconds by default. Without an answer the caller gets a 403 and a retry asks again.
- A rate brake per risk class is applied.
- The key service inserts the real key and sends the request only to the profile's host. It never follows redirects.
- In the response it redacts your key values (plain, base64, hex, URL-encoded) and swaps any new secret the provider returns for a fresh placeholder, then passes the response back to the agent.
What to know
- You register a passkey before your first key — it's what guarantees that access can only ever be widened with your confirmation, never by the app alone.
- 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. Outside full access, payments and orders always wait for your approval; under full access they go through without asking.
- You can bring your own AI provider key: 25 providers are listed, from OpenAI, Anthropic and Mistral to Swiss ones such as Infomaniak, and some are still marked beta or soon (full list). Requests with it go straight to that provider, so that provider's retention terms apply. ZeroLog does not guarantee zero data retention by third-party providers; Featherless's statement about Developer API content is a provider commitment, not a control ZeroLog can enforce per request.
- Any new secret a provider hands back — a freshly created token, for example — is caught and stored the same way. An agent only ever sees a placeholder for it too.
- Lock a key instantly from the panel. A locked key stops working everywhere at once.
- Containers with their own VPN access do not go through the key service and cannot use keys stored here — this is enforced technically, not just documented: such a workspace never receives key-service trust or secrets in the first place.
- A site hosted elsewhere reads its own code, including anything embedded in it — prefer a key limited to what that site actually needs.
Plain-language overview: API key proxy for AI agents.
Each vault entry can also be set to use only: the AI sees a placeholder with an ID, and the key service inserts the value only for hosts you allow, now also for Postgres and MySQL. See the vault for the three states, the passkey confirmation and the path from box through broker and key service to the target, and blackout for how values are removed from tool output and provider requests.
Finding a provider
Open Settings, then Providers & keys. The page has two tabs: AI providers for your own AI key (see your own API key) and Services & keys, which is this key proxy. Each tab has its own address, ?tab=ki and ?tab=dienste.
- The catalogue holds over a hundred templates for DNS, hosting, mail, payments, databases, monitoring and more. Each template fixes the provider's host and how the key is sent, and sorts its actions into read and write. The exact number shows above the search box.
- Search by name, category or keyword. Press
/to jump to the field, narrow by category, move through results with the arrow keys and use Show more for long lists. If nothing matches, the page offers to suggest the provider. - About sixty services are listed as Soon, each with the reason it cannot yet be mapped to a fixed host and header.
Microsoft 365
The Microsoft 365 (Graph) template covers the directory, mail, calendar, files, SharePoint pages and the list of Teams channels. The app signs in with client credentials: you enter the tenant ID or domain, the client ID and either a certificate (recommended) or a client secret. The key service trades them for short-lived Graph tokens by itself and talks only to graph.microsoft.com. The agent sees neither the secret nor the token.
- 25 actions. A new key starts read-only. The write template adds calendar entries, drafts, file contents and folders. Sending and replying to mail, and deleting mail, events or files, wait for your approval unless the key has full access.
- Only the global Microsoft cloud works; national clouds do not. Application permissions cover the whole tenant and need admin consent in Entra, so limit mailboxes and use Sites.Selected. Sending Teams messages and device-code sign-in are not available. The form lists the permissions each action group needs.
What a hidden key does not prove
A placeholder prevents the supported agent route from returning the credential itself. Destination, method and path policies decide which operations are allowed. An allowed operation can still have harmful effects; narrow the provider permissions as well as the proxy policy. This is not protection against every compromise of the application or host. See the request boundary and the separate vault.
Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Security · Status · X · Legal & privacy · Home