Store your API keys in Botpasses and approve which agents can use them. Botpasses makes the API calls and removes secrets from the responses before returning them to the agent.
Use the hosted service or run Botpasses yourself.
botpassesINTERACTIVE EXAMPLEReview the request and approve one API call.
Connect through MCP
How it works
Ask your agent to check a balance, open an issue, or update a record. Botpasses checks its approval before sending the API request with your key.
Add a credential and the API hosts it can reach. Enter the value in Botpasses, never in chat.
Store a credentialReview the agent and its request. Approve one call, or set a standing approval for work you trust.
Set up approvalsBotpasses attaches the key to the approved API call and returns a redacted result. The model does not get the key.
Follow a requestAccess controls
Review requests, check the activity log, and revoke access from the console.
Key attached to requestThe agent asks for an API call. The vault handles authentication. There is no get_secret tool returning your stored value.
Revoke an agent or an approval from the console. Its next call loses access. The agent cannot undo your decision.
Revoke an agent or approvalSee which agent used which credential, when, and the outcome. Activity records actions and names, without storing secret values.
Every agent belongs to an environment. A staging agent cannot use a production credential, even when the names match.
Who can decrypt your keys? The hosted process decrypts credentials in memory to make approved calls. Anyone with both the AWS KMS role and the database can also decrypt them. Botpasses is not zero-knowledge. Read the security model
Get started
Choose the hosted service, a local vault, or your own server. Copy the setup prompt into your agent and enter credentials in Botpasses.
Create an account, connect your agent, and approve your first call. Free to use.
Local
Run a local CLI vault without an account. Your credentials stay on your machine.
Self-hosted
Botpasses is open source. Run the console and MCP server on your own infrastructure, with Postgres and your own domain.
Open source, MIT licensed. View the source on GitHub
Botpasses stores API keys and lets your agents use them with your approval. It attaches the key to each approved API call and removes secrets from the response. The model does not get the key. There is no get_secret tool.
No. Password managers hold secrets for people and fill them into browsers. Botpasses holds credentials for agents and attaches them to API calls the agent asks for. Agents cannot retrieve the stored key. Botpasses has no browser autofill or sharing between people.
It cannot read the stored key through MCP, but it can call APIs it has approval to use. Use one-call approvals for sensitive tasks, restrict allowed hosts, and revoke standing approvals when a task is done. The activity log records each call by agent and credential name.
Actions and names: which agent requested or used which credential, when, and the outcome. Tokens are stored as hashes. Values are never written to the audit log, the inbox, emails, error reports, or server logs.
From Agents in the console. Revoke an agent (its tokens stop working on the next call), one approval, or one session. Revoke is operator-only; there is no revoke over MCP, so a model cannot undo it.
Every credential carries an environment tag, and every agent is bound to one environment. An agent bound to staging cannot use production credentials. Separately, staging.botpasses.com is the pre-release copy of the service with its own accounts. You can also run the console and MCP server locally with npm run hosted:dev.
Yes. Run npm run hosted:dev for the console and MCP server on your laptop, or use the local CLI vault without an account. Botpasses is open source and MIT licensed. You can also host it on your own server with Postgres 16; see the Self-hosting guide.
Anyone with both the AWS KMS role and the database can decrypt your keys. The hosted process decrypts them in memory when making approved calls. Staff have no support tool that reveals a key. Botpasses is not zero-knowledge.
A key pasted into a prompt enters the conversation. A key in .env can be exposed if an agent reads the file or prints its environment. Botpasses never returns a value to the model. The agent asks for a call by host; you approve; the vault attaches the key on the way out.
Create a free account, store an API key, and approve your first call.
Create account Read the quickstart