Agent ↔ MCP
Free Agent and MCP identity first, then KYA Authority or MCP Assurance where reliance demands it.
Open route →ECZ-ID RELIANCE ROUTES
START WHERE RELIANCE BREAKS. ROUTE TO THE CURRENT ECZ-ID SURFACE.
Different buyers encounter the same accountability problem in different forms: agent access, supplier onboarding, platform integration, operational resilience, software supply chain, physical autonomy, evidence or managed service. These routes explain the problem and send the visitor to the current ECZ-ID capability—not to a legacy catalogue of specialised Passports.
CURRENT SPECIALIST ROUTES
One accountability architecture. Different reliance problems.
Digital counterparties
Make websites, suppliers, platforms, APIs and other digital surfaces easier to review before reliance.
Open route →Procurement
Accountable organisation, machine scope, current state and public proof before onboarding or renewal.
Open route →DORA
Operational-resilience and ICT vendor review using current active DORA products.
Open route →SBOM / software supply chain
Publisher and software accountability using current active SBOM products and re-checkable proof.
Open route →Cloud / platforms
Provider-neutral accountability around provider-native IAM, workload identity and platform controls.
Open route →Robotics / autonomy
Map physical systems onto the canonical IoT, Workload, Agent, API or MCP surface that actually operates.
Open route →Audit / insurance / evidence
Trace what was proposed, decided, done and recorded without confusing integrity with underlying truth.
Open route →MSP / MSSP
Turn machine trust into a repeatable managed-client service through the dedicated MSP estate.
Open MSP estate ↗ROUTING RULE
The specialist route explains. The current catalogue decides what is available.
Historic corridor concepts, specialised Passport variants and named outcome packs remain preserved as product-development IP. A website route does not make a DRAFT product live. Current acquisition belongs in TrustOps; public proof belongs in Resolver.