QL Vault

The first password manager built for agents. Your QL Agents, the Slack bot and QL Intelligence can sign in and get work done on your sites — without ever seeing your passwords. The vault signs each request server-side and hands the agent a redacted response.

SealedSecrets are AES-256-GCM encrypted, bound to your account, and never returned to anyone — not to you, not to a model, not to a log. Only your own agent's requests can use them.
AllowlistedCredentials travel only over HTTPS to hosts you name. Redirects are reported, never followed. Writes stay off until you switch them on per site.
Approved & auditedRequire your Approve tap before each use, or trust an item outright. Every sign-in and request is logged with surface, host and status.

Sites your agent may use

Loading your vault…

How your agent uses it

Ask any agent surface in plain language — “Sign in to Carta and pull my latest cap table export”, “using my vendor-portal login, check whether invoice 4471 is paid”. The agent calls the vault's credential_vault tool (MCP: vault_list_items / vault_request); the vault signs in, performs the request on an allowed host and returns a response with every secret value redacted. The agent never holds a password, a cookie or a 2FA code, and cannot ask you for one — the tool has no field for it.
QL AgentsSlack bot (DMs only)QL IntelligenceMCP (OAuth connector)

Audit log

WhenSurfaceActionHostResultDetail
Loading…