Documentation
Every page is also served as Markdown at the same address with .md. The index for language models is /llms.txt.
For agents
- Using aquaman from an AI agent: aquaman is a credential proxy for AI agents: secrets stay in the user's own vault and are injected when a command or request needs them.
- Your agent asked to use aquaman: Your coding agent needs an API key or token for the task you gave it.
Hosts
- Keep API keys out of Claude Code: Claude Code can read your .env files and anything in its shell environment.
- Give Codex a token without a .env file: Codex runs shell commands with whatever is in the environment and can read .env files in the workspace.
- Keep an API key out of the app a coding agent builds: By default aquaman sets a key as an environment variable for each command a coding agent runs, so the command, and the app it starts, hold the key while they run.
- Keep API keys out of the OpenClaw gateway process: OpenClaw runs your agents, plugins and channels in one gateway process, so a key in its config or environment is readable by anything that runs there.
- Keep provider keys out of the Hermes agent process: Hermes reads provider keys from its environment. With aquaman, Hermes is pointed at a local proxy and given a placeholder; the proxy injects the real key from your vault, so the key is never in the Hermes process.
- Docker Sandboxes secrets from 1Password, Bitwarden or your keychain: Docker Sandboxes (sbx) already keeps credentials out of the sandbox: a proxy on your machine injects them, and the agent in the VM sees a placeholder. By default the values come from your OS keychain.
- Use your own vault as the NVIDIA OpenShell credential driver: NVIDIA OpenShell keeps provider credentials out of its sandboxes: the sandbox sees a placeholder and the supervisor injects the real value on the way out.
Reference
- aquaman compared with other ways to keep credentials from AI agents: Most agent hosts now ship some form of credential protection, and several dedicated tools exist. This page says where aquaman fits and where something else is the better choice.
- Security Policy: This is the security policy for aquaman, a credential proxy for AI agents: how to report a vulnerability, what is in scope, and which versions get fixes. Security reports get priority over everything else.
- MITRE ATLAS Mapping: Aquaman maps to MITRE ATLAS v5.4.0 (Adversarial Threat Landscape for Artificial-Intelligence Systems) — a stable, machine-readable catalog of adversary techniques widely cited in audit reports.
- NIST SP 800-53 Rev 5 Mapping: Aquaman maps to NIST SP 800-53 Rev 5 control families that govern authentication, access enforcement, key management, and audit.
- Agentic AI Security Guidance: Aquaman aligns with multiple 2026 industry guidances on agentic AI security. These are documentary frameworks (no conformance programs), so claim alignment with specific recommendations, not certification.