AI agents · OpenClaw · self-hosting · automation

Quick Answer

Credential Vaulting Tools for AI Agent Fleets (2026)

Published:

The short answer

Pick the vault your platform team already runs, then add per-agent identity and automatic expiry on top. For fleets of AI agents, as of November 17, 2026:

ToolHow it vaults for a fleetPrice (Nov 17, 2026)Self-hostBest for
HashiCorp Vault 2.2 + IBM Agent IdentityPer-agent accounts, automatic credential renewal, dynamic credentials; Agent Identity records owner, lifecycle and authority; real-time revocationVault Community free; Enterprise and Agent Identity by quote✅Enterprises with Vault already in place
InfisicalMachine identity per agent, dynamic secrets, rotation; Agent Vault proxy keeps keys out of the agentFree 5 identities · Pro $20/identity/mo annual ($23 monthly) · Advanced $40 ($46) · Agent Vault 5,000 requests free, then $1 per 10,000✅ MIT corePlatform teams that want one tool, cloud or self-hosted
AWS AgentCore IdentityOAuth tokens and API keys issued to agents on behalf of users or themselvesFree via AgentCore Runtime/Gateway; otherwise $0.010 per 1,000 requests❌Fleets running on Bedrock AgentCore
Kong Token VaultAgent authenticates to Kong; Token Vault brokers the downstream credential at runtimePart of Kong Identity (sales)Kong deployment optionsFleets whose traffic already flows through Kong

This page is a spoke of our best secrets managers for AI agents hub, which covers vaults for single agents and small teams.

What a fleet needs that one agent does not

  1. An identity per agent. Shared tokens make every audit log useless and every revocation a fleet-wide outage. Infisical bills per identity; AWS ties identity to AgentCore; IBM’s Agent Identity is a dedicated registry.
  2. A named owner. Gartner, quoted by IBM, expects the average Fortune 500 company to run more than 150,000 agents by 2028. Without an owner field, nobody can say which agents are safe to delete.
  3. Credentials that expire on their own. Dynamic secrets (Vault, Infisical Advanced) mint a database user or cloud key per task and revoke it when the lease ends.
  4. Per-agent revocation mid-task. IBM’s pitch for Agent Identity plus Vault is exactly this: deny an out-of-scope action and revoke that agent’s session in real time.
  5. Brokering for third-party APIs. Some SaaS APIs only accept static keys. Keep those in a broker (Infisical Agent Vault, Kong Token Vault) so the agent never holds them.

HashiCorp Vault 2.2 + IBM Agent Identity — for enterprises on Vault

IBM announced both as generally available on October 27, 2026 at TechXchange. Vault 2.2 “gives agents their own secured accounts, automatically renews their credentials” and adds post-quantum encryption. Agent Identity is the authoritative record for each agent — owner, lifecycle status, granted authority — and shares that context with Vault’s credential controls. watsonx Orchestrate’s discovery of agents built on Amazon Bedrock, Microsoft Foundry and Google Gemini is still a tech preview. Choose this when Vault is already your secrets backbone; the agent layer is an extension, not a migration.

Infisical — best all-in-one for platform teams

Infisical bills Secrets Management per identity, human or machine, which nudges you toward one identity per agent. Free covers 5 identities; Pro is $20 per identity a month on annual billing ($23 monthly); Advanced, $40 ($46 monthly), adds dynamic secrets, gateways to private infrastructure, full rotation and temporary access. Agent Vault, billed separately per brokered request (5,000 a month free, then $1 per 10,000), adds time-limited agent sessions, method and path rules, MCP tool filtering and session logs. The MIT core is free to self-host. Watch the per-identity maths: 200 agents on Pro is $4,000 a month, so group short-lived agents under a pool identity and let Agent Vault sessions carry the per-agent scope.

AWS AgentCore Identity — cheapest on AWS

AgentCore Identity issues OAuth tokens and API keys to agents, on behalf of users or the agent itself, against identity providers such as Cognito, Okta or Microsoft Entra ID. It is free when used through AgentCore Runtime or AgentCore Gateway; otherwise AWS charges $0.010 per 1,000 token or API-key requests — AWS’s own example of 150,000 requests a month costs $1.50. The trade-off is lock-in to AgentCore.

Kong Token Vault — for gateway-first fleets

Kong made Token Vault generally available on November 4, 2026 as part of Kong Identity. Agents authenticate to Kong with their own identity, Kong Identity decides what each may reach, and Token Vault brokers the right downstream credential for APIs, MCP servers, models and data at request time, so the agent never holds it. It fits organisations that already enforce policy in Kong gateways.

How to choose

  • Vault is already your standard: Vault 2.2 + Agent Identity.
  • Mid-size platform team, mixed clouds, want self-hosting: Infisical, with Agent Vault for SaaS keys.
  • All agents on Bedrock AgentCore: AgentCore Identity — it is included.
  • Every agent call already passes Kong: Token Vault.

For the per-workspace side of the same problem, see secret brokers for agent-run cloud workspaces and builds; for runtime proxies, see tools for brokering secrets to AI agents at runtime.

Last verified: November 17, 2026.

Sources