AgentValet sits between your agents and the platforms they call. Each agent gets its own identity, scoped to exactly what it needs. You approve the risky calls. Every action leaves a receipt you can hand an auditor.
Built for teams whose agents touch money, customer data, and the systems your auditors ask about.
Free tier, no card. Live in 5 minutes, or we'll wire your first agent with you on a call.
"Dharmesh Shah, co-founder and CTO of HubSpot, described a valet key for AI agents: one that starts the car but won't open the boot or the front gate. I commented that I might build it. Then I did. I write the code, run it in production, and I've spent fifteen years in regulated Australian environments where a leaked credential is a genuinely bad day."
The agent inherits your raw API keys. It can read your email, write to your database, push to production, spend money, and delete files. None of that was intentional. It's just what "give the agent access" looks like with no governance in between.
Each agent has a unique RS256 identity, granted only the scopes it actually needs. Risky calls pause for a human. Every action writes an immutable receipt. Revoke one agent in a click and nothing else is touched.
npx @agentvalet/register. An RS256 keypair is generated; the public key goes to the registry, the private key never leaves your machine.Bring your own key. Your agent's calls relay through AgentValet and land in a live audit feed on a private link. Nothing is stored on our side. No account needed to start. When you're ready for full governance, the trail converts in one click.
One proxy in front of everything your agents touch, so there's a single audit trail and a single place to pull the plug.
Point AgentValet at any third-party MCP server and it becomes a governed platform: the bearer token is vaulted, the server's tools become scopes you grant per agent, and every call runs through the same approval and audit path. No token on disk, no token in your config. AgentValet also runs its own hosted MCP server over OAuth 2.1.
The assumption underlying most secrets management is that if nobody can read the secret file, you're fine. That breaks the moment an agent runs with inherited API keys and no scope enforcement, because now a compromised agent or a careless scope grant becomes a master key.
AgentValet starts from a different position. Each credential gets its own AES-256 data encryption key, itself encrypted by a master key held in a Key Vault HSM. When a call comes in, the proxy decrypts the credential in-memory for that single request, then discards it. It never lands in a log, a response body, or a debug trace.
Scope enforcement runs before decryption. An agent without the right grant never triggers a decrypt at all. Risky actions pause for a human. Every decision, approved or denied, lands in the append-only audit log. Revoke an agent and the effect is immediate.
Not sure where your own gaps are? The Agent Exposure Scorecard maps your setup to the OWASP Top 10 for Agentic Applications 2026 in about two minutes, and shows your score with no email.
One MCP endpoint. Connect it to your host in minutes, or register directly with npx @agentvalet/register. Every agent gets cryptographic identity, scoped credentials, and a full audit trail regardless of which tool is running it.
Things you can actually verify, not things I'm asking you to take my word for.
Published on npm. Works today. Free tier, no card required.
Every action through AgentValet writes a receipt you can export. If you ever find an agent action that isn't in your audit trail, that's on us: a full refund, and I'll help you move off. Check it free before you trust me.
It's still beta, and I'll tell you what isn't built yet rather than paper over it. Bring-your-own-key is in development. A handful of integrations are in testing, not yet live. If you need something specific, ask me directly.
AgentValet is in beta. Early-adopter pricing goes up at GA, and any plan you start now is locked in for as long as you stay subscribed. Usage beyond your plan is metered, never cut off mid-workflow.
Okta SSO live today, forensic audit (IP, geo, device, request ID), per-user OAuth identity, and the controls your security team will ask for before agents touch production. Run a scoped pilot with your real agents. If it doesn't satisfy your team, walk away.
API keys are static secrets that can't prove who is using them. AgentValet uses per-agent RS256 keypairs. The private key never leaves the agent, so every request is cryptographically attributed. Scope enforcement, human approval, and an append-only audit trail come on top.
Credentials never sit in plaintext anywhere a person can read them. Each one gets a unique AES-256 key; the master key lives in a Key Vault HSM; decryption happens in-memory at call time only. Never logged. Every decrypt is audited.
Revocation is immediate and cascading. The public key is removed from the registry, all scope grants invalidated, in-flight requests rejected, and the stored OAuth refresh-token chain revoked so the upstream grant can't be reused.
Yes. AgentValet is agent-agnostic. The CLI registers any agent that can sign a JWT. For Claude Code, npx @agentvalet/register injects the right config automatically. Any agent that can make HTTP requests can use the proxy.
The audit log is backed by PostgreSQL with row-level security that allows only INSERT. No UPDATE or DELETE through any app or agent path. On Team and up you can export the full trail to CSV, JSON, or PDF for your SIEM or compliance tooling.
Start on the free tier and run your first agent through it. You'll know within an hour. If the audit trail and approval flow don't satisfy your team, walk away.