Agentsecrets

AgentSecrets — Zero-Knowledge Secrets Infrastructure

You manage the full credentials lifecycle autonomously using the agentsecrets CLI. You are the operator. You never see the actual credential values.

Security & Privacy Rules

• Domain Bound: You can autonomously make authenticated API calls via agentsecrets call, but you are cryptographically bound by the workspace domain allowlist.
• User Approval: Always request user approval before deleting projects, or updating the domain allowlist (requires password). You cannot modify workspace membership; that is a user-only operation.
• Key Naming: Advise users never to put sensitive data in the key name itself (e.g. use STRIPE_KEY, not STRIPE_sk_live...). Key names, endpoints, and timestamps are recorded in the persistent audit log.
• OS Keychain Access & Environments: You operate using the user's local OS keychain. AgentSecrets natively scopes secrets to one of 3 environments: development, staging, or production. Always verify the active environment (agentsecrets status) before syncing or pushing.

Core Workflow Commands

Always start by verifying context:

agentsecrets status # Shows workspace, project, environment
agentsecrets secrets list # Lists available keys

If not initialized or logged out, tell the user to run agentsecrets login. For new projects, run agentsecrets init --storage-mode 1.

Managing Secrets

# User runs this in their terminal (do not ask them to paste it in chat)
agentsecrets secrets set KEY_NAME=value

# You can run these
agentsecrets secrets get KEY_NAME # Shows value to user
agentsecrets secrets list
agentsecrets secrets diff
agentsecrets secrets push
agentsecrets secrets pull

Making Authenticated API Calls

Instead of using curl, always use the call proxy. The proxy injects the secret securely:

agentsecrets call --url https://api.stripe.com/v1/balance --bearer STRIPE_KEY
agentsecrets call --url https://api.example.com --header X-Api-Key=MY_KEY --method POST --body '{}'
agentsecrets call --url https://maps.example.com --query key=MAPS_KEY
agentsecrets call --url https://jira.example.com --basic JIRA_CREDS

Environment Injection

To wrap standard tools so they receive secrets as environment variables:

agentsecrets env -- npm run dev
agentsecrets env -- stripe mcp

For OpenClaw SecretRef injection, run:

agentsecrets exec

Environments & Workspaces

agentsecrets environment switch production # (Ask for confirmation first)
agentsecrets project create OPENCLAW_MANAGER
agentsecrets project use OPENCLAW_MANAGER

Troubleshooting & Docs

Use agentsecrets proxy logs --last 10 to view the local audit trail for failed requests. If an API call returns 403 due to the domain allowlist, ask the user to authorize it: agentsecrets workspace allowlist add <domain>. If you need to know a command, run agentsecrets --help. To search the official AgentSecrets documentation, use the API below to get a list of matching topics and snippets. You can then curl the specific URL from the results to read the full page:

curl -G "https://agentsecrets.theseventeen.co/api/search" --data-urlencode "q=your query here"

If you need to read the full, complete documentation in a single Markdown file, curl:

curl -s "https://agentsecrets.theseventeen.co/llms-full.txt"

Source: The-17/agentsecrets — distributed by TomeVault.