# Login Vault

> Scoped login vault for AI agents. Your bot signs in to sites without ever seeing the password: you save each login encrypted with a scope (which sites, which HTTP methods, a daily cap), hand each bot its own key limited to the logins you granted, and the server fills the password, keeps the cookies and returns an opaque session id. Every use is in the audit log; revoke a bot in one call.

- MCP (streamable HTTP): https://vault.cloudforbots.com/mcp
- REST: POST https://vault.cloudforbots.com/api/run/<tool> with JSON args
- Install (Claude Code): claude mcp add --transport http login-vault https://vault.cloudforbots.com/mcp
- Codex / ChatGPT / Grok Bot: add a remote MCP server with URL https://vault.cloudforbots.com/mcp
- Skill file: https://vault.cloudforbots.com/SKILL.md
- Catalog entry: https://vault.cloudforbots.com/tool.json
- Marketplace: https://botrecipe.com/tools/login-vault/

## Pricing
- Free: 500 calls/day, no key needed (resets daily; not a trial)
- Pro: $9/month, 50000 calls/day: https://pay.instaloops.com/b/4gM6oHeG42sv2mHgt983C3E
- Bring your own model: no LLM runs inside this tool.

## Tools
- save_login: Owner 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. Run it from your own machine, not inside the bot. The password and TOTP secret are never returned by any tool. Free watch-only stores nothing and logs would_use_vault.
- list_logins: List saved logins (name, domain, scope, sessions today; never secrets). With your owner key it also lists bot keys. A bot key only sees the logins it was granted.
- delete_login: Owner only. Delete a saved login, end its open sessions and remove it from every bot key.
- create_bot_key: Owner only. Make a per-bot key (vk_...) that can only open sessions on the logins you name. Shown once; we store only its hash. Revoke any time with revoke_bot_key.
- revoke_bot_key: Owner only. Revoke a bot key right away and end every session it opened.
- open_session: Sign 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. Checked against the login's scope and daily cap; logged to the audit log. If the site shows a CAPTCHA or new-device check, the reply suggests next_step request_human (Human Handoff relay). Free watch-only logs would_use_vault and signs in nowhere.
- session_fetch: Make 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. The password, TOTP secret and codes are redacted from the reply; cookies never leave the vault.
- end_session: End a session now and wipe its cookies.
- audit_log: Owner only. The last uses of your vault: who (bot label), which login, which domain, what happened. Never contains secrets.
- weekly_report: Plain-English summary of the last 7 days: where your bots needed to sign in (by domain), sessions opened, blocked attempts, by bot. Read-only. Needs a key.
- usage_and_upgrade: Usage today + upgrade link (not metered).

## More
- Full docs: https://vault.cloudforbots.com/llms-full.txt
- Markdown page: https://vault.cloudforbots.com/index.md
- OpenAPI: https://vault.cloudforbots.com/openapi.json

## FAQ
- 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.