save_loginFrom your own machine, save the login with a scope: which sites, which methods, how many sessions a day.
Cloud for Botsinfrastructure for your bots
Let your bot sign in. Never hand it the password.
Save each login once, encrypted, with a scope: which sites, which methods, how many sessions a day. Give every bot its own key for only the logins it needs. The server fills the password and keeps the cookies; your bot gets an opaque session id. Every use is logged, and one call revokes a bot.
500 calls/day free · Pro $9/mo · AES-256-GCM at rest · secrets never returned
invoice-bot · vk_…9Qe
- open_session("github-bot")
- scope: github.com · GET/POST
- fill {{username}} {{password}} {{totp}}
- POST github.com/session
open_session → checking scope
audit: invoice-bot · github-bot
Sample: Watch-only: logged that your bot needed a sign-in on github.com. Nothing was stored or sent. Pro signs in with a scoped login and returns an opaque session id.
Works with the agents you already run
- AClaude
- {}Codex
- CChatGPT
- GGrok Bot
How it works
Save once. Scope it. Your bot signs in blind.
create_bot_keyGive one bot a vk_ key that can use only the logins you name. Revoke it any time.
open_sessionYour bot asks for a session. The server fills the password, keeps the cookies and returns an opaque id. Every use is logged.
Pricing
Watch free. Pay when it acts.
Free resets daily and is not a trial. Pro is $9 a month.
Free · watch-only
$0
Watch-only mode. 500 calls a day: every time your bot needs to sign in, we log a would_use_vault for that site, and weekly_report shows where your bots needed logins. Nothing is stored and nothing is sent.
- would_use_vault logged for every sign-in
- Weekly report: where bots needed logins
- Works with no key, or a free key
- Stores nothing, sends nothing
Pro
$9/month
Acting: logins stored encrypted (AES-256-GCM) with per-login scopes (allowed sites, methods, daily cap, session TTL), per-bot keys limited to the logins you grant, an audit log of every use, sessions opened server-side with secrets redacted from replies, instant revocation, 50,000 calls a day.
- Logins encrypted at rest (AES-256-GCM)
- Per-login scopes: sites, methods, daily cap
- Per-bot keys, revoke in one call
- Audit log of every use, 50,000 calls a day
Worked example
Your invoice bot downloads statements from 3 supplier portals every morning. On free, open_session logs 3 would_use_vault entries and Monday's weekly_report says your bots needed sign-ins on 3 sites. With Pro at $9/month, you save the 3 logins once from your laptop, scope each to its portal (GET and POST only, 5 sessions a day), and give the invoice bot a vk_ key for just those 3. It signs in, downloads the PDFs and never sees a password. If the bot misbehaves, revoke_bot_key cuts it off in one call.
For agents
Tools your agent gets
Each result includes understood, job and a one-line outcome your agent can report back in plain words.
save_loginOwner only (your Pro key, never a bot key). Store one login sealed with AES-256-GCM, with a scope: allowed hosts, allowed methods, a daily session cap and session TTL.
list_loginsList saved logins (name, domain, scope, sessions today; never secrets). With your owner key it also lists bot keys.
delete_loginOwner only. Delete a saved login, end its open sessions and remove it from every bot key.
create_bot_keyOwner only. Make a per-bot key (vk_...) that can only open sessions on the logins you name.
revoke_bot_keyOwner only. Revoke a bot key right away and end every session it opened.
open_sessionSign in with a saved login without seeing it. The server fills {{username}}, {{password}} and {{totp}} into your form, posts it to url (https, inside the login's allowed hosts), keeps the cookies encrypted, and returns an opaque session id.
session_fetchMake one request inside an open session. url must be https inside the login's allowed hosts and the method must be in its allowed methods.
end_sessionEnd a session now and wipe its cookies.
audit_logOwner only. The last uses of your vault: who (bot label), which login, which domain, what happened.
weekly_reportPlain-English summary of the last 7 days: where your bots needed to sign in (by domain), sessions opened, blocked attempts, by bot. Read-only.
usage_and_upgradeUsage today + upgrade link (not metered).
Connect
One line to install
claude mcp add --transport http login-vault https://vault.cloudforbots.com/mcp
MCP URL https://vault.cloudforbots.com/mcp
REST POST https://vault.cloudforbots.com/api/run/<tool>
Auth optional Authorization: Bearer <key>
Codex, ChatGPT, Grok Bot: add a remote MCP server with the URL above. Skill file: SKILL.md · catalog entry: tool.json
FAQ
Questions
What problem does this solve?
Agents need to act inside logged-in accounts, but pasting a password into a prompt or an env file means every bot, log and transcript can leak it. Login Vault keeps the password on our side: your bot asks for a session, the server signs in, and the bot only ever holds an opaque session id.
Does my bot ever see the password?
No. No tool returns a password or TOTP secret, ever. open_session fills them on the server, and session_fetch redacts them from every reply. Cookies stay in the vault too.
How are logins stored?
Encrypted with AES-256-GCM before they reach the database, bound to your account and the login name. Bot keys and session ids are stored only as hashes. Secret values are never written to logs.
What is a scope?
Each login has allowed hosts (the login's domain plus any you add), allowed HTTP methods, a daily session cap and a session lifetime. A request outside the scope is blocked and logged.
What are bot keys?
create_bot_key makes a vk_ key for one bot, limited to the logins you name. It is shown once. revoke_bot_key stops it immediately and ends its sessions.
What if the site shows a CAPTCHA or a new-device check?
open_session returns needs_human with next_step request_human. Hand that step to your person with Human Handoff relay, then open the session again. We never solve CAPTCHAs.
What is watch-only mode?
The free plan logs every time your bot would have used the vault (by site) and builds a weekly report. Nothing is stored and nothing is sent. It is not a trial.
What does Pro do?
Stores logins encrypted with scopes, issues per-bot keys, opens sessions, keeps an audit log, and allows 50,000 calls a day.
Which sites work?
Sites that sign in with an HTTPS form or JSON post, including TOTP 2FA codes. Browser-only sign-ins are not supported in v1.
What does it cost?
Free: watch-only, 500 calls a day. Pro is $9 a month, or $90 for a year. It is also included in the Cloud for Bots All Access bundle.