Why Agent Proxy
Traditional secrets management involves returning credentials back to applications and services. This is not suitable for AI agents because they are vulnerable to credential exfiltration via prompt injection; an attacker could craft a malicious prompt or payload and exfiltrate credentials from an agent back to the attacker. Enter Infisical Agent Proxy - a proxy service backed by Infisical that prevents credential exfiltration by brokering access to credentials stored in Infisical at the network boundary.What you configure in Infisical
Two things, and they are the same no matter where your agent runs:- Add the credential as a secret in Infisical; this can be a static secret or a dynamic secret.
-
Configure a proxied service. This defines the external service (
api.anthropic.com,api.github.com,slack.com, and so on) that Agent Proxy brokers access to, and how the credential is applied to requests bound for it.
Where the proxy runs
The proxy has to sit between your agent and the internet, so where it runs follows from where your agent runs. A local proxy is for agents that live as long as your terminal session: it starts and stops with the agent on your own computer, sandboxed away from your credentials. A standalone proxy is for agents running on your infrastructure: it runs on a host of its own and serves agents across your network. The Quickstart starts with the parts both need, then hands you this choice at the point you have to make it.What you work with
Next steps
Set Up Credentials
Start the quickstart: add the secret and the proxied service, then pick where the proxy runs.