Postman ships Passport GA so AI agents can call APIs without holding real secrets

Postman announced general availability of Passport by Postman, a standalone API-security product that lets developers, machines, and AI agents discover and call approved APIs without ever holding the real API keys or tokens. Credentials stay self-hosted in the customer environment; callers get cryptographic secret references checked at a customer-deployed proxy (company).

SAFETY desk — same-day company primary that a major API platform put secretless, agent-native API access into GA, aiming at credential sprawl as agents multiply API calls.

Product, as the same wire has it: a standalone API-security product, and the company’s expansion from API tooling into API security. Passport is meant to give organizations a secure way to consume APIs as human and non-human identities — people, machines, and AI agents — work side by side. Secretless here means the caller never holds the real API key or token. File that standalone / secretless / humans-and-agents picture as Postman’s. This desk did not call an API through Passport. Do not confuse this with DigiCert’s already-filed AI Passport — that is a different company and a different product.

Design, still company: real API credentials stay inside the customer’s own environment and secret store. Callers receive a secret reference — a cryptographic pointer that does nothing without the customer-deployed proxy, and is bound to the identity that requested it. Cryptographic here means a math-backed token, not a shared password copied into a file. The company contrasts that with traditional API-key management and gateway approaches that focus on distributing and protecting secrets. File that self-hosted-vault / inert-reference / customer-proxy picture as Postman’s. This desk did not stand up a proxy.

Controls named on the same wire, company: grant permission down to the exact action, host, and path; every request is checked against those rules before it reaches the vault; revoke access in seconds; full attribution for every call. File that grant / check-before-vault / revoke-in-seconds / attribution list as Postman’s. This desk did not revoke a grant or audit a call log.

Agents, still company: developers and agents are treated identically. Agents receive ephemeral, task-scoped identities minted from a durable parent, so a fleet of agents can run without distributing long-lived secrets. Ephemeral means short-lived and thrown away after the job. A durable parent is the longer-lived identity those short-lived ones are minted from. Sub-agents inherit only a subset of the parent’s permissions. File that identical-treatment / task-scoped / subset-inherit picture as Postman’s. This desk did not mint an agent identity.

Problem framing, as Postman tells it: developers and AI agents need to call APIs constantly, but the keys and tokens that authenticate those calls are hard to control once they land on a machine. A real credential can spread across .env files, repositories, chat tools, IDE configurations, and CI logs, making it difficult to audit. A single leaked credential can be used thousands of times before anyone catches it, and the company says AI agents may call APIs at about 1,000 times the rate humans do. File that copy-paste sprawl / 1,000x / leaked-key picture as Postman’s. This desk did not count agent call rates or audit a leaked key. Do not read those lines as an independent breach statistic.

Named voice on the release: Abhinav Asthana, co-founder and CEO of Postman. He says AI agents get their abilities through APIs, and that as developers and agents multiply the number of calls, the number of credentials in circulation grows just as quickly. File the name, title, and that agents-get-abilities-through-APIs line as his, via Postman. His other quotes are color only and stay in Sources.

Availability, company: Passport is available now. The wire points readers to http://usepassport.ai/. File that available-now / usepassport.ai line as Postman’s. This desk did not open an account. The release does not print a price. This desk is not inventing one. An earlier June 2026 Postman blog introduced Passport and asked readers to register for access — use that post for architecture, not as the GA date. Today’s Business Wire is the GA record.

Architecture color from that earlier company blog — HOW, not today’s dateline: consumers get credential references instead of real keys; API calls route through a Secure Access Proxy the customer deploys in their own network or VPC; the proxy resolves the reference and injects the real key inside that boundary; the company says the resolved secret never reaches Postman, logs, or audit records. A VPC is a virtual private cloud — a private slice of a public cloud. File that reference-plus-proxy picture as Postman’s earlier architecture write-up. This desk did not inspect the proxy.

About-box context, optional and company-attributed: Postman says it is trusted by more than 40 million developers and 500,000 organizations, including 98% of the Fortune 500. Headquartered in San Francisco, with offices in Bangalore, Boston, New York City, and Tokyo. Privately held. File those scale and location lines as Postman’s. This desk did not recount developers or audit a Fortune 500 list.

Plain English for the rest of the card: secretless = the agent never sees the real API key. proxy = a component in the customer’s own cloud that swaps a safe reference for the real key only at call time. GA = generally available, offered for production use. secret reference = a cryptographic pointer that is useless without the proxy. ephemeral identity = a short-lived agent identity minted for one task. durable parent = the longer-lived identity those short-lived ones come from. VPC = virtual private cloud, a private slice of a public cloud. agent sprawl = agents multiplying faster than anyone can see, govern, or shut down. API = application programming interface, the machine-to-machine doors an app exposes.

PRIMARY here: Postman’s 15 Sep 2026 Business Wire company release — Tier A PRIMARY company source, the original record. The usepassport.ai product site is product-home context, not a second originating newsroom. The June 2026 Postman blog is earlier introduce / register-for-access architecture, not the GA date. The Passport GA, the standalone API-security expansion, secretless access for humans, machines, and AI agents, credentials staying self-hosted in the customer environment, the secret-reference / customer-proxy design, grant-to-action-host-path / check-before-vault / revoke-in-seconds / full-attribution controls, identical treatment of developers and agents, ephemeral task-scoped identities minted from a durable parent, sub-agent subset inheritance, the .env / repo / chat / IDE / CI-log sprawl framing, the company 1,000x agent-call-rate line, the Asthana title, the available-now / usepassport.ai line, and the 40-million / 500,000 / 98%-of-Fortune-500 about-box are company-attributed. The 1,000x line and about-box counts stay company-attributed — not independently verified here. NOT claimed: named enterprise customers, pricing, ARR, independent breach statistics, that this desk tested Passport, a stock tip, or investment advice. Distinct from the already-filed digicert-ai-trust-manager (do not confuse Postman Passport with DigiCert AI Passport), wso2-agent-manager-ga, cloneguard-private-ai, stackhawk-wingman, and salesforce-aiforce.