What is AgentSecrets?
The Zero-Knowledge Difference
How AgentSecrets Works
Installation
Quick Start
Migrating from .env Files
Migrating from Vault / AWS
Migrating from dotenv-vault
Production Checklist
Credential Exposure
What Zero-Knowledge Means
The Proxy Model
The Three-Layer Model
Environments
Agent Identity
Storage Modes
The No get() Principle
Secret-Level Policies
Cloud Overview & Architecture
The Dual-Engine Model
Cloud Resolver Data Plane
Workload & Agent Tokens
Egress Allowlists & Audit Streams
Cloud REST API Reference
Account (init / login)
Server & Self-Hosting (server)
Docs
Shell Autocompletion
Keychain Auth
Secrets
Environments
Credential Proxy
env Injection
Workspaces & Teams
Projects
Agent Identity
Audit & Governance
Integrations Overview
Claude Desktop
Cursor
OpenClaw
HTTP Proxy (Any)
LangChain (Soon)
CrewAI (Soon)
CI/CD Pipeline
SDK Overview
Python SDK
Python API Reference
Python SDK Manual Testing
JavaScript SDK (Soon)
Ecosystem Overview
Zero-Knowledge MCP Server
Server Overview
5-Layer Architecture
Self-Hosting Guide
Authentication & Keys
Workspaces & Teams
Projects & Scope
Environments
Secrets & Sync Protocol
Agent Identity Resolution
Telemetry & Metrics Engine
Audit Log Sync
API Endpoint Reference
Security Overview
Anti-Impersonation & Process Verification
Encryption Model
Zero-Knowledge Sync
Proxy Security Layers
Threat Model
OWASP Top 10 Mitigation
Security FAQ
Third-Party Audit
Reporting Vulnerabilities
Guides Overview
Building on the SDK
Stripe Integration
OpenAI Integration
Multi-Agent Setup
Onboarding Team
CI/CD Pipeline
Publishing ZK MCP
Rotating Credentials
Auditing Team Activity
Dev to Production
Kubernetes Deployment
Monorepo Setup
Production Proxy Hardening
vs .env Files
vs HashiCorp Vault
vs AWS Secrets Manager
vs dotenv-vault
vs Infisical
When Not to Use
Proxy Not Starting
Proxy Not Resolving
Domain Blocked
Sync Conflicts
MCP Not Connecting
Session Token Errors
Proxy Session Authorization
Keychain Storage & Backends
SSRF & Destination Rules
Installation Issues
Error Codes Reference
Frequently Asked Questions
v3.1.x
v3.0.0
v2.1.0
v2.0.0
v1.4.0
v1.3.x
v1.2.0
v1.1.x
v1.0.x
SecuritySecurity Overview

Security Overview

AgentSecrets is built from the ground up on the principle of Least Privilege for Artificial Intelligence. Traditional security architectures assume that the runtime environment executing code is trusted. AI agents break this assumption because they are dynamic, interpret untrusted inputs, and are vulnerable to context leakage and prompt injection.

The Security Model in One Page

The core guarantee of AgentSecrets is simple: The actual value of your API credential never enters the memory, context, or logs of the AI agent.

To achieve this, the architecture isolates credentials into three distinct layers:

  1. The AI Agent (Untrusted): Only holds the key name (e.g., OPENAI_API_KEY). The agent has no programmatic method to read the actual value.
  2. The Local Proxy (Trusted): A lightweight daemon running locally (on localhost:8765). It has access to your local OS Keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service). It intercepts outbound requests from the agent, resolves the key name, injects the real credential into the HTTP headers at the transport layer, and forwards the request.
  3. The Synchronization Server (Zero-Knowledge): Stores credentials in end-to-end encrypted (E2EE) ciphertext blobs. The cloud backend never sees your plaintext secrets or your master encryption keys.
Loading diagram...

Security Deep Dives

To understand specific parts of our security implementation, explore the dedicated pages below:

Was this helpful?
Thanks for your feedback!
Your feedback helps us improve the platform.