> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.usepassport.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.usepassport.ai/_mcp/server.

# Request lifecycle

A consumer calls an API through Passport using a secret reference instead of a real secret. The Passport Proxy, running inside your cloud, resolves that reference to the real secret at request time and forwards the call to the destination API. The consumer never handles the real secret.

The following happens on each call:

1. The consumer sends the request containing a secret reference.

   * **Passport CLI** — The request routes to the proxy running inside your cloud.
   * **External clients (curl, scripts, SDKs)** — A locally running daemon intercepts the outbound request and routes it to the proxy running inside your cloud.

2. The proxy receives the request.

3. The proxy authenticates the caller's identity using a cryptographic certificate.

4. The proxy checks the caller's API permissions. This confirms they're authorized to use the secret reference before contacting your secret store.

5. The proxy resolves the secret from your secret store and injects it into the request.

6. The proxy forwards the request to the destination API and returns the response.

The resolved secret never passes through Passport Cloud. It also doesn't appear in logs or audit records.