Documentation Index
Fetch the complete documentation index at: https://docs.agent-vault.dev/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A running Agent Vault instance (see installation guide)
- An agent or script that can make HTTP requests
Quick start
Wrap your agent process withvault run. It sets AGENT_VAULT_ADDR, AGENT_VAULT_SESSION_TOKEN, and AGENT_VAULT_VAULT, then pre-configures HTTPS_PROXY and the CA trust chain so standard HTTP clients transparently route through the broker:
Target a specific vault
Try it out
Your agent calls real API URLs directly.HTTPS_PROXY routes the request through Agent Vault, which matches the host against the vault’s services and injects the stored credential into the auth header for that service.
proposal_hint. Your agent can use this to create a proposal requesting access.
Your agent never sees or handles credentials. Agent Vault strips whatever the client sends and injects the real API key at the proxy boundary.
Other connection flows
- Agent invites — for cloud-hosted agents or CI pipelines that can’t be wrapped with
vault run. See Connect a custom agent. - Manual HTTPS_PROXY setup — for containerized agents and sandboxes that need to configure the proxy themselves. See Set HTTPS_PROXY manually.
- Explicit
/proxyendpoint — for clients that can’t honorHTTPS_PROXY(HTTP/2-only runtimes, no CA-mounting). See Explicit proxy endpoint.
Discover available services
Call/discover to check which hosts have credentials configured:
Response
services go direct, not through the proxy.
Next steps
Connect a custom agent
Full guide with manual HTTPS_PROXY setup, error handling, and proposals.
Agent protocol
HTTP reference for sessions, discovery, and proposals.