Stop building agent platforms. Start building agent passports.

The market has too many agent platforms and too few agent passports. The platforms compete on orchestration, prompt management, and connector breadth. The passports — portable, cryptographic, identity-bound — barely exist. The platforms will commoditize; the passports will compound.

The crowded side

The agent platform market today is operating like the JavaScript framework market of a decade ago. New entrant every quarter, similar feature sets, faster cycles, all subsidized by venture money. The eventual winners will be a handful of survivors built on commoditized model APIs, distinguished by integrations and developer experience. None of them are durable in the ways category-creating infrastructure becomes durable.

The empty side

The agent passport — a portable, cryptographic identity that an agent carries from platform to platform, gathering attested actions, building reputation, surviving the platform — barely exists. Microsoft Entra Agent ID is platform-specific. AWS IAM Roles for Anywhere is cloud-specific. SpruceID and Privado are SSI-pure but not optimized for agents. The category is real, the demand is rising, the supply is thin.

Why passports compound

The longer an agent operates with a passport, the more attested history it accumulates. The history is not platform-specific; it follows the agent across the next platform, the next host, the next year of operation. The passport, in other words, has the property the platforms wanted but cannot have: it gets more valuable to its owner over time, regardless of which vendor the agent runs through this week.

What a passport actually is

A small, signed object: an agent DID, the human who issued it, the active and historical scopes, the magnitude history, the witnessed work attestations, the dispute history (if any). Presentable selectively. Verifiable independently. Issuable by the human, never the platform. The passport is the agent's identity in the same sense that a human's Manav DID is the human's identity.

What's blocking adoption

Two things. The platforms have an incentive to keep agent identities inside their boundary; portable passports reduce switching costs. And the buyer side has not yet articulated the demand sharply enough to force the supply side. The first is a tactical problem; the second is a category-creation problem, and we are working on it loudly.

Where this matters fastest

Marketplaces of agents (think Toptal but for agent freelancers), enterprise procurement of third-party agents, and any setting where an agent has to prove its history before being trusted. In each case the passport is the unblock; the platform is interchangeable.

Common objections

The strongest counter-arguments we have heard. The incumbent will catch up — possibly inside their boundary; the cross-platform shape is architecturally hard for them. The category is too narrow — we believe it broadens as agent autonomy compounds; we may be wrong; the data over the next year will tell.

Frequently asked questions

What are the strongest counter-arguments? The two we hear most: (1) the incumbent will eventually ship this, and (2) the category is too narrow to support a category-defining company. We address both head-on; we believe the incumbent's architecture cannot ship this without a rebuild, and we believe the category broadens as agent autonomy compounds.

Are we ignoring legitimate criticism? We try not to. The honest criticisms — slow adoption, immature SDKs in some languages, unclear regulator response — are documented openly. We answer with progress, not with marketing.

What would make us change our mind? Three signals. A major incumbent shipping a comparable cross-platform delegation primitive. A regulator explicitly preempting the category with a different spec. A customer cohort showing they prefer the platform-bound alternative even when the audit trail is broken. None of those have appeared.

Where to start

For the steel-manned counter-position, read agent identity is a category. For the alternative we agree could win, see cross platform agent identity. We do not need to be right for the category to be real.

Why platform-bound identity is already dying

A platform-bound identity is rented infrastructure. It works until the platform changes terms, gets acquired, or shuts down. Every prior decade of identity has produced a graveyard of platform-bound credentials whose holders discovered, mid-career, that they did not own what they had built. The lesson is so well-established that the next generation of identity protocols cannot afford to repeat it, and the regulators have noticed. The portability requirements quietly being added to identity-related regulations across major jurisdictions all point in the same direction: the user, not the platform, owns the credential. Platforms that resist this trajectory will spend the next several years lobbying against it and losing. Platforms that adopt it early will earn the durable trust the platforms before them lost. The choice is no longer whether to make identity portable. The choice is who builds the portable substrate the platforms will eventually consume. We are betting the substrate is built once.

Build the artifact the agent carries forever, not the platform the agent rents this week.