
Argent with Infisical
Keep your AI provider keys in Infisical, in its cloud or on your own instance. Argent reads each secret at the moment a request needs it and attaches it at the gateway, so by default the agents that work through Argent never hold it.
What Argent does with Infisical
Your AI provider keys stay in Infisical, where your security team already manages them. Argent keeps a reference to each key, not a copy, and reads the value at the moment a request needs it.
- Agents hold their own Argent key, not yours. By default, the agents that work through Argent never hold the provider's key. Each agent gets its own Argent key, and the gateway attaches the real key from Infisical on the way out. See keyless agents.
- Why it matters. GitGuardian counted 1,275,105 leaked AI-service secrets in 2025, up 81% in a year. A key that lives only in your vault is not sitting in every agent's settings file.
- One place to change a key. Rotate it in Infisical or from the Argent console. No agent needs a new setting, because by default no agent holds it.
- More than AI keys. Argent stores the other credentials it uses the same way, as vault references and never as values: MCP server credentials, ticketing tokens and directory sign-ins.
- Cloud or self-hosted. Point Argent at Infisical's cloud or at your own instance, and pin a private certificate authority if you run one. Verification stays on.
How a request gets its key from Infisical
The agent points its AI client at the Argent gateway and sends its own Argent key. The rest happens at the gateway, on every AI model call.
- Argent checks who is calling. The Argent key must belong to an active agent. The Argent key stops at the gateway: the AI provider never receives it.
- Argent checks the agent may use the credential. A credential can require a permission, and an agent without it is refused.
- Argent finds the vault that serves the reference. Each credential points at a reference, and each reference belongs to one connected vault.
- Argent reads the secret from Infisical. It signs in with Universal Auth, receives a short-lived access token, and reads the secret the reference names from the project, environment and folder you set. Argent renews the token before it expires.
- Argent swaps the keys. It removes any provider key the agent sent and attaches the key from Infisical on the way out to the provider.
- Argent signs a record. It names the agent, the provider and the vault reference. It never contains the key.
Argent holds the value only briefly, in a cache kept separate for each tenant and vault, and overwrites it when it is dropped. If anything fails, the request is refused with a named reason, such as credbroker.vault_unavailable. A customer vault never falls back to another vault, and a failed vault never falls back to the agent's own key.
What you enter in the Argent console
An admin connects Infisical under Integrations > Vault in the Argent console. The form asks for:
| Field | What it is |
|---|---|
| Host URL | Infisical's base URL: https://app.infisical.com or your own instance. |
| Client ID | The Universal Auth machine identity Argent signs in as. |
| Workspace ID | The Infisical project the secrets live in. |
| Environment | The environment slug, for example prod, staging or dev. |
| Secret path | Optional folder the secrets are read from. Defaults to the root, /. |
| Canary secret | Optional. A secret the connection test reads to prove access. With none, the test signs in only. It never returns the value. |
| CA certificate (PEM) | Optional. Your instance's certificate authority, for a private or self-signed certificate. Verification stays on. |
| Client secret reference | Where the Universal Auth client secret is kept, never the secret itself. |
The credential Argent signs in with is itself a reference. The Universal Auth client secret is kept in Argent's built-in vault, resolved only when the connector connects, and never stored in Argent's database, logged or shown back.
- Test. Tick the live check on the form and Test signs in and, with a canary secret set, reads it, then reports reachable or unreachable without returning the value. Without the live check, Test checks the settings only.
- Connect, see impact, disconnect. The same page connects the vault, shows what depends on it, and disconnects it.
- Pick, do not type. Reference fields across the console offer a picker of the references the deployment already holds, so nobody mistypes a path.
What you set up on the Infisical side
A few things on your side, once. Your team keeps managing the keys exactly where it does today.
- A machine identity with Universal Auth. Infisical's Universal Auth signs a machine in with a client ID and client secret and returns a short-lived access token (Infisical).
- Access to the project and environment Argent reads from, and the folder path if the keys are not at the root.
- The client secret, saved as a reference in Argent's built-in vault.
- Your instance's CA certificate if a self-hosted instance uses a private certificate.
- A network path from Argent. Argent dials every connector through a guarded client that refuses private, loopback and link-local addresses unless told otherwise. If your vault sits on a private network, an operator lists its address range in the
ARGENT_TENANT_EGRESS_PRIVATE_CIDRSsetting (Helm valuecontrolPlane.tenantEgressPrivateCidrs). Cloud metadata addresses are refused whatever is listed. - Writing is a separate choice. To rotate keys from the Argent console, an admin turns on writing for this vault, with its own sign-in for writes. Until then Argent only reads.
Guardrails around your vault
Connecting a vault to an AI gateway should not widen who can reach its keys. These rules hold for Infisical:
| Guardrail | What happens |
|---|---|
| Fails closed | A vault that cannot be reached, a missing credential or an empty secret refuses the request with a named reason. Nothing is sent without the right key. |
| Tenant fence | A tenant admin can only name references inside its own tenant's area. Another tenant's path is refused and signed. |
| Read-only until you say so | Writing is off by default. Turning it on takes a fresh passkey confirmation and is recorded. |
| A second vault, by path | A tenant can connect a second vault that owns a path prefix. Each reference goes to the vault whose path matches it most closely; anything else goes to the default vault. If that vault is down, its requests are refused, never sent elsewhere. |
| Signed changes | Changing which paths a vault serves is a signed change. If the signed record cannot be written, the change is refused. |
| Signed use | Every request's record names the agent, the provider and the vault reference, never the key. |
Rotating a key. From the Credential Broker page, Argent writes the new value to Infisical, then the admin keeps it or rolls it back. After rotating a key directly in Infisical, run argentctl secrets rotated so every gateway drops its cached copy. Revoking a credential in Argent drops Argent's reference; the value stays in Infisical.
What the operator sees. The Credential Broker page lists every connected vault and reference, which agents used each secret, their human owners and the last five calls. When an auditor asks which agents used the company's AI key, the record answers. See one-click audit evidence.
Where it fits, and how you start
A vault integration is where keyless agents start.
- Capabilities: keyless agents, identity tethering, owner offboarding, agent reach control and watch before you enforce. All capabilities.
- Goals: agent identity and ownership, threat defense, audit and accountability, compliance evidence and sovereign AI.
- Use cases: AI coding agents, customer-facing assistants, enterprise copilots, agent tool access and regulated and air-gapped AI.
- Related integrations: Docker Compose and Kubernetes and Helm, for running Argent on the same network as a self-hosted Infisical. Keys for OpenAI, Anthropic and the other AI model providers, and credentials for MCP servers, can all live in this vault.
- Other vaults: HashiCorp Vault and OpenBao, AWS Secrets Manager, CyberArk Conjur, or the vault built into Argent. Run Argent on premises, in a private cloud or in your public cloud VPC.
- Industries: financial services, insurance, healthcare, the public sector and retail. All industries.
- Watch. In Watch mode an agent's own key passes untouched, and Argent records what it would have stripped or refused.
- Connect Infisical. Fill in the form under Integrations > Vault and run Test.
- Point credentials at it. Add each AI provider credential as a reference to the secret already in Infisical. Argent records the reference; it never copies the value.
- Enforce and prove. Switch on Enforce, give each agent its own Argent key, and retire the old copies. Every request's record shows which agent used which key.
Want this running on your own use cases?
Book a demo