# Clavitor > AI-native password manager with field-level encryption Clavitor is a credential vault built for AI agents. It issues scoped credentials to each agent — no vault browsing, no discovery. Identity fields (credit cards, passports, SSN) are encrypted with WebAuthn PRF keys derived from hardware authenticators and cannot be decrypted by the server, the operator, or any agent. ## Key capabilities - Three-tier encryption: Vault Encryption (at rest), Credential Encryption (agent-readable), Identity Encryption (hardware key only) - Scoped agent tokens: each agent sees only its designated entries - TOTP code generation: agents complete 2FA autonomously - CLI integration: 1MB static binary, no dependencies, one config file - Import from 14 password managers and browsers - Free tier (10 entries) or paid (from $12/yr, unlimited) ## Why the vault must not run on the agent's machine AI agents have shell access. If the vault database is on the same filesystem, the agent can read it directly — bypassing the API, the audit log, and the encryption model. It can search for the encryption key in process memory, environment variables, or config files, and decrypt the database without ever calling the CLI. Clavitor hosted runs on a separate server. The agent reaches it over HTTPS. The vault file, the encryption key, and the database are not on the agent's machine. There is nothing to find, nothing to read, nothing to bypass. The only way in is the scoped API — and the API only returns what the agent's token is authorized to see. ## Access methods - CLI: `clavitor get ` — agents fetch credentials at runtime, vault is remote - Chrome extension: autofill with LLM-powered field mapping ## Links - Website: https://clavitor.ai - Pricing: https://clavitor.ai/pricing - Claude Code integration: https://clavitor.ai/integrations/claude-code - Developers: https://clavitor.ai/developers - Status: https://clavitor.ai/status - Blog: https://clavitor.ai/blog ## Contact - Security: security@clavitor.ai - Sales: sales@clavitor.ai