Passport
Passport gives your developers and AI agents access to the APIs they need without ever handling a real secret. Instead of receiving API keys, they get secret references that the Passport Proxy resolves inside your cloud. Secrets never leave your infrastructure.
Developers browse available APIs in Passport, request access, and can start calling them after a Passport Admin approves. Coding agents call APIs the same way, with secret references scoped to only the APIs they’re approved for. Secret references are bound to the consumer they were issued to, so a leaked reference doesn’t expose a real key. Every request is logged, and Passport Admins can revoke access to a specific API at any time.
The Passport Proxy is deployed in your own environment. Passport Admins manage team access and connect the proxy to a secret store (HashiCorp Vault, AWS Secrets Manager, or Google Cloud Secret Manager). Developers and agents send requests with the Passport CLI or with tools they already use, like curl, scripts, and SDKs, which a local daemon routes through the proxy.
The Passport CLI (passport) is a separate tool from the Postman CLI (postman). The Passport CLI connects your machine to the Passport Proxy and sends requests that use secret references. The Postman CLI runs and manages collections, specifications, and other Postman elements.
Use Passport with coding agents
The Passport plugin adds Passport skills to Claude Code, Codex, Cursor, and other coding agents that support skills. Describe what you want in natural language, and your agent can set up an evaluation Passport Proxy, register the APIs your project calls, and manage their credentials.
Passport covers the API calls your agent makes with secret references. To give your agent access to Postman itself, such as collections, tests, and mock servers, set up the Postman CLI for coding agents with postman init.
Get started
To get started, visit the Passport app and see the Passport documentation for deployment, setup, and usage guides.