Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Secure credential proxy for AI agents. Make API calls through AgentKeys — real secrets never leave the vault.
Secure credential proxy for AI agents. Make API calls through AgentKeys — real secrets never leave the vault.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Secure credential proxy for AI agents. Route API calls through AgentKeys so your agent never sees real secrets.
You have two options. Set these in your environment or .env:
AGENTKEYS_API_KEY=ak_ws_... AGENTKEYS_PROXY_URL=https://proxy.agentkeys.io Use your workspace API key to proxy requests to any credential by name. Get your API key from Settings.
AGENTKEYS_PROXY_TOKEN=pxr_... AGENTKEYS_PROXY_URL=https://proxy.agentkeys.io Use a proxy token for one specific credential. Get it by assigning a credential to an agent in the dashboard.
curl -X POST $AGENTKEYS_PROXY_URL/v1/proxy \ -H "Authorization: Bearer $AGENTKEYS_API_KEY" \ -H "X-Credential-Name: resend" \ -H "X-Target-Url: https://api.resend.com/emails" \ -H "Content-Type: application/json" \ -d '{"from": "noreply@example.com", "to": "user@example.com", "subject": "Hello", "text": "Sent via AgentKeys"}'
curl -X POST $AGENTKEYS_PROXY_URL/v1/proxy \ -H "Authorization: Bearer $AGENTKEYS_PROXY_TOKEN" \ -H "X-Target-Url: https://api.resend.com/emails" \ -H "Content-Type: application/json" \ -d '{"from": "noreply@example.com", "to": "user@example.com", "subject": "Hello", "text": "Sent via AgentKeys"}'
HeaderRequiredDescriptionAuthorization✅Bearer $AGENTKEYS_API_KEY or Bearer $AGENTKEYS_PROXY_TOKENX-Target-Url✅Target API URL to forward toX-Credential-Name✅ (API key mode)Name of the credential to use (case-insensitive)Content-Type❌Passed through to target
Agent sends request to AgentKeys proxy with API key + credential name (or proxy token) AgentKeys finds and decrypts the real credential server-side Real credential is injected into headers Request is forwarded to the target API Response is returned to the agent Every request is logged in the audit trail The agent never sees the real API key, OAuth token, or password.
API Key — injected as Authorization: Bearer <key> Basic Auth — injected as Authorization: Basic base64(user:pass) Custom Headers — injected as key-value pairs Query Parameters — appended to URL Cookies — injected as Cookie header OAuth — auto-refreshed tokens
Credentials are AES-256-GCM encrypted at rest Proxy tokens are scoped to one credential + one agent API key mode still respects workspace permissions Tokens can be revoked instantly from the dashboard Full audit trail for every proxied request Agent never has access to plaintext secrets
Dashboard: app.agentkeys.io Docs: agentkeys.io/docs Support: support@agentkeys.io
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.