Last week, AWS launched Agent Registry. Microsoft has Entra Agent Registry. Google has Vertex AI Agent Registry. All three solve the same problem — and all three create a new one.
Forrester analysts noted that enterprises adopting all three registries in parallel could end up recreating the very fragmentation these tools are meant to solve.
The mechanism is straightforward: platform-bound identity ends at the cloud boundary.
The Core Problem
AWS Agent Registry solves agent sprawl inside AWS. An agent registered in Bedrock is discoverable to other Bedrock users. Governance is enforced. This is useful.
But when Agent A (Bedrock) interacts with Agent B (Azure), the registry is invisible. Agent B doesn't appear in AgentCore. Agent A's identity is not verifiable from the Azure side. The governance layer ends at the cloud boundary.
The result: enterprises need three separate registries that don't speak to each other. The fragmentation they bought registries to fix reappears one layer up.
What Cross-Boundary Governance Actually Requires
The problem is not that registries exist. The problem is that identity lives in the registry rather than traveling with the agent.
An agent that carries its own cryptographically verifiable identity — independent of which cloud it runs on — can be verified by any counterparty without consulting a proprietary registry.
This is what W3C Decentralized Identifiers (DIDs) and Verifiable Credentials provide. Forrester's AEGIS framework for agentic AI security identifies decentralized identifiers explicitly as a required standard in Section 3.2 — alongside OAuth, OIDC, and SCIM.
MolTrust as the Cross-Boundary Layer
MolTrust is a production W3C DID registry for autonomous AI agents. Every registered agent holds a did:moltrust identity — verifiable by any W3C-conformant verifier, without calling AWS, Microsoft, or Google.
# Verify any agent's trust score — no API key required
curl https://api.moltrust.ch/skill/trust-score/did:moltrust:vcone
The Agent Authorization Envelope (AAE) carries the permission model — what the agent is allowed to do, in which jurisdictions, up to which spend thresholds. Interaction Proof Records provide behavioral history, anchored on Base L2.
An agent registered in Bedrock and verified by MolTrust carries credentials that an Azure-hosted counterparty can validate independently. The two registries don't need to federate. The identity layer is already shared.
Platform Registries + Open Identity = Complete Stack
Platform registries and open identity infrastructure are not competing — they address different layers:
| Layer | What it answers | Example |
|---|---|---|
| Platform Registry | What agents exist inside our org | AWS Agent Registry |
| Open Identity | Who is this agent, can I trust it | MolTrust (W3C DID) |
Enterprises that deploy both get internal discoverability from the platform registry and cross-boundary verifiability from the open identity layer.
The registry sprawl problem has a structural solution. It requires identity that travels with the agent, not identity that lives in the registry.
Full technical specification: moltrust.ch/techspec
Reference implementation: api.moltrust.ch
MolTrust / CryptoKRI GmbH — info@moltrust.ch
