# Setting up a secret Every value is encrypted in your browser before it is saved. Our server cannot read it. Once every computer on your account runs the updated helper app, names and setups are locked away from our server too. ## Add a secret Go to **Vault → Add a secret**. Start with the one box labelled **What is this key for?** Type a known service and press **Enter**. The form fills in that service's own labels, how the key is sent, and where it may go. You only paste the values. The service list is a shortcut, not a restriction. Everything it fills in can be changed with **Change how it's sent**. Check where the key may go before saving. For an unknown service, type its name and press **Add “”**. Choose what kind of key it is, paste it and save. You don't have to say how it is sent: the first time your agent uses it, it proposes where the key goes and how, and you approve that once. To set it ahead instead, press **Set it now**. ## Choose the kind of key - **One API key or token** — one value supplied by a service. - **ID and secret** — two values that the service needs together. - **Four keys for signed requests** — four values used to sign requests, as X requires. - **Username and password** — a pair sent as a username and password. - **Website or device login** — a username and password, with an authenticator setup key if the site has one. Agents can sign in to a router or app with it once you approve how, or get its authenticator code. They never see the password. - **Authenticator code** — a site's authenticator setup key on its own. Agents get the current code, never the key. - **SSH key** — a private key used to sign in to servers. - **Crypto wallet** — a key for a Base or Solana wallet. - **Signing key** — a key used to sign data. ## How a web key is sent For a service on the list, this is filled in. For any other, your agent proposes it the first time and you approve it, or you set it yourself with **Set it now** (or **Change how it's sent**). Match the example in the service's own instructions. The choices are: - **Authorization: Bearer (most services)** — the key follows `Bearer ` in the Authorization header. - **In a header the service names, like x-api-key: ** — use the header name the service gives you. - **After ? in the web address, like ?api_key=** — the key goes in a named part after the question mark. - **Inside the web address, like /bot/sendMessage** — the key goes between the pieces of address the service specifies. - **As a username and password** — the two values are sent together as a login. - **Signed requests** — the key signs each request rather than being pasted into it. For **ID and secret**, each part gets its own row. Set where it goes, its header name if needed, and any text around it. There are at most two rows. A key in the web address may not contain spaces, `?`, `#`, or `%`. It may not start or end with `/`. ## A service that isn't on the list, field by field Have the service's own instructions open. They show an example request; copy its shape. - **Name:** what you'll call it. Your agents see this name. - **Kind:** see the list above. Most services give **One API key or token**. - **How it's sent (optional):** leave it, and approve your agent's proposal the first time; or press **Set it now** and pick the choice whose example looks like the service's. - A header with its own name: type the header name exactly, for example `X-Access`. If the service wants text before the key, put it in **Text before**, for example `Token ` (with the space) for `X-Access: Token `. - After `?` in the address: type the parameter name, for example `api_key`. - Inside the address: type the address path with `{secret}` where the key goes, for example `/bot{secret}`. Your agent adds the rest of the path. - Username and password: type the username; the key is the password. - **ID and secret:** one row per part. Each row has **Where**, **Name**, **Text before**, **Which part** and **Text after**. Two headers is the usual case. - **Where it may go:** for a service on the list, its addresses are filled in. For any other service, the first time an agent uses the key at a new address you are told about it (**Runs without asking**) or asked first (**Asks me first**). ## Signed requests Some services never take the key itself: each request carries a code made from it instead. Choose **Signed requests** for those. Supported today: - **OAuth 1.0a**, for X. Use the **Four keys for signed requests** kind. - **AWS Signature Version 4**, for AWS. Use **ID and secret** (the access key ID and the secret access key), then under **Change how it's sent** choose **Signed requests (AWS, exchanges)**. - **HMAC signing**, which many exchanges use. Use **ID and secret** the same way, or **One API key or token** with **Signed requests** if the service gives you only a secret. Your agent describes how the service wants each request signed, and you approve each new way once. Keys that sign tokens (JWT) are not supported yet. A service that needs one can't be set up yet. ## Authenticator codes For a sign-in that asks for the 6-digit code from an authenticator app. When you turn on the authenticator at the site, it shows a QR code; choose the option to see it as text (often **Can't scan it?**). That text, or an `otpauth://` link, is the setup key. Add it as **Authenticator code**, or in the **Authenticator setup key** box of a **Website or device login**. Your agent gets the current code, never the key. Set it to **Asks me first** and every code waits for you. Codes sent by text message or email, and passkeys, are not covered. ## Signing in to routers and apps For things with a sign-in of their own, like a home router's admin page. Add the username and password as **Website or device login** (or **Username and password**). The first time, your agent proposes how to sign in, and you approve a card that says where your password goes. The helper app signs in and keeps the session; your agent sees neither. A device with its own certificate can be trusted by its fingerprint, and a changed certificate is refused. ## SSH keys, git and servers Add an SSH key and save: you don't list servers. The first time an agent signs in somewhere new, you approve that server and its identity is remembered. A different machine at the same address is refused. Each secret's page lists its approved servers; you can add or remove them there. The same key works for `git push`, `pull`, `fetch` and `clone` over SSH, to the servers you approved. On Linux and Mac; the helper app on Windows doesn't do SSH yet. ## Admin (sudo) work Agents never get your sudo password. On the computer where the helper app runs (Linux or Mac), run this once: `sudo sh /opt/wundervault/current/app/packaging/admin-key.sh` It makes an admin key that only works from that computer and shows it once. Add it as an **SSH key** and save. The first time an agent uses it, you approve that computer as its server. Choose **Asks me first** to approve every admin command. To take it away: run the same command with `--remove` at the end. ## Choose approval Choose **Runs without asking** or **Asks me first**. **Asks me first** needs a passkey. Agents on a computer whose helper app has not been updated cannot receive keys with several parts. The vault says **Update first**. Update that computer's helper app before using the key there. ## Services that fill in the form Each line says what to paste, how it is sent, and where to find the service's instructions. - **Airtable** — paste Personal access token; sent as a Bearer token. [Help](https://airtable.com/developers/web/api/authentication) - **Alpaca** — paste Key ID and Secret key; sent in the apca-api-key-id header and in the apca-api-secret-key header. [Help](https://docs.alpaca.markets/docs/authentication) - **Anthropic** — paste API key; sent in the x-api-key header. [Help](https://docs.anthropic.com/en/api/overview) - **Brave Search** — paste API key; sent in the x-subscription-token header. [Help](https://api-dashboard.search.brave.com/app/documentation/web-search/get-started) - **Cloudflare (API token)** — paste API token; sent as a Bearer token. [Help](https://developers.cloudflare.com/fundamentals/api/how-to/make-api-calls/) - **Cloudflare (global API key)** — paste Account email and Global API key; sent in the x-auth-email header and in the x-auth-key header. [Help](https://developers.cloudflare.com/fundamentals/api/how-to/make-api-calls/) - **Discord webhook** — paste Webhook ID and token (after /api/webhooks/); sent in the web address. [Help](https://discord.com/developers/docs/resources/webhook) - **ElevenLabs** — paste API key; sent in the xi-api-key header. [Help](https://elevenlabs.io/docs/api-reference/authentication) - **GitHub** — paste Personal access token; sent as a Bearer token. [Help](https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api) - **GitLab** — paste Personal access token; sent in the private-token header. [Help](https://docs.gitlab.com/api/rest/authentication/) - **Google Gemini** — paste API key; sent in the x-goog-api-key header. [Help](https://ai.google.dev/gemini-api/docs/api-key) - **Groq** — paste API key; sent as a Bearer token. [Help](https://console.groq.com/docs/api-reference) - **Linear** — paste Personal API key; sent in the authorization header. [Help](https://linear.app/developers/graphql) - **Listmonk** — paste API user and Token; sent as a username and password. [Help](https://listmonk.app/docs/apis/apis/) - **Mistral** — paste API key; sent as a Bearer token. [Help](https://docs.mistral.ai/api/) - **Notion** — paste Integration secret; sent as a Bearer token. [Help](https://developers.notion.com/reference/authentication) - **OpenAI** — paste API key; sent as a Bearer token. [Help](https://platform.openai.com/docs/api-reference/authentication) - **OpenRouter** — paste API key; sent as a Bearer token. [Help](https://openrouter.ai/docs/api-reference/authentication) - **Postmark** — paste Server token; sent in the x-postmark-server-token header. [Help](https://postmarkapp.com/developer/api/overview) - **Resend** — paste API key; sent as a Bearer token. [Help](https://resend.com/docs/api-reference/introduction) - **SendGrid** — paste API key; sent as a Bearer token. [Help](https://www.twilio.com/docs/sendgrid/api-reference/how-to-use-the-sendgrid-v3-api/authentication) - **Slack webhook** — paste Webhook path (after /services/); sent in the web address. [Help](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks) - **Stripe** — paste Secret key; sent as a Bearer token. [Help](https://docs.stripe.com/api/authentication) - **Tavily** — paste API key; sent as a Bearer token. [Help](https://docs.tavily.com/documentation/api-reference/introduction) - **Telegram bot** — paste Bot token; sent in the web address. [Help](https://core.telegram.org/bots/api) - **Twilio** — paste Account SID and Auth token; sent as a username and password. [Help](https://www.twilio.com/docs/usage/requests-to-twilio) - **TypeSafe** — paste API key; sent as a Bearer token. [Help](https://docs.typesafe.ai/api) - **X (Twitter)** — paste API key and API key secret and Access token and Access token secret; sent as signed requests (OAuth 1.0a). [Help](https://docs.x.com/fundamentals/authentication/oauth-1-0a/api-key-and-secret) ## Worked examples - **OpenAI:** Type OpenAI and press Enter. Paste the one API key. It is sent as a Bearer token. - **Alpaca:** Type Alpaca and press Enter. Paste **Key ID** and **Secret key** into their own boxes. They are sent in two headers: `apca-api-key-id` and `apca-api-secret-key`. - **X:** Type X and press Enter. Paste all four values: **API key**, **API key secret**, **Access token**, and **Access token secret**. They are used for signed requests with OAuth 1.0a. - **An SSH key:** Make a key without a passphrase. Put the `.pub` half on the server. Choose **SSH key**, paste the private half and save. Approve the server the first time an agent signs in. - **A crypto wallet:** Choose **Crypto wallet** for Base or Solana. Set the daily limit and trusted payees on the wallet in your vault. ## Common mistakes - Pasting a whole Slack or Discord webhook URL. Paste only the part after `/services/` for Slack or `/api/webhooks/` for Discord. - Putting `Bearer ` into the value. Paste only the key; the setup adds the text around it. - Using an SSH key with a passphrase. Make a key without a passphrase for this setup. - Choosing **One API key or token** for a service that gives two values. Choose **ID and secret** and keep the values in separate boxes. ## If an agent is asked how to set up a key Answer from this page. Never ask for the key's value. Point the owner to **Vault → Add a secret**.