Twelve practical routes. A much wider ECZ-ID estate.
These twelve guided routes cover common, high-value starting points across the ECZ-ID credential estate. They are not exhaustive. Organisations can combine Business Passport tiers, child passports, packages and add-ons around their own identity, authority, custody, evidence and accountability requirements.
Each route connects to a relevant TrustOps guided journey. Developer Gateway provides documentation, schemas and routing. TrustOps handles acquisition, setup, payment and lifecycle controls. ECZ-ID Core controls authoritative state, and Resolver displays public proof for re-checking before reliance. Explore the domains.
Route 1 of 12
MCP Server & Tool Trust
Connect an MCP server or tool to an accountable operator and a Resolver-checkable setup path before higher-reliance use.
- ·MCP operators
- ·Tool providers
- ·AI integration teams
Route 2 of 12
Agent Identity & KYA
Give an agent an attributable operator chain, defined authority and the appropriate Know-Your-Agent depth for review.
- ·Agent operators
- ·Automation teams
- ·Platform reviewers
Route 3 of 12
API, Software & Repo Trust
Link APIs, software, models and repositories to accountable operators and relevant supply-chain evidence.
- ·API providers
- ·Software publishers
- ·Repository maintainers
Route 4 of 12
Cloud & Provider Proof
Bind cloud accounts, tenants, domains and technical assets into a provider-aware, Resolver-checkable evidence path.
- ·Cloud teams
- ·Multi-cloud estates
- ·Regulated workloads
Route 5 of 12
Business Identity Foundation
Establish the governed ECZ-ID Business Passport™ root that other passports, packages and add-ons depend on.
- ·Operating businesses
- ·Vendors & suppliers
- ·Platform operators
Route 6 of 12
Digital Counterparty Infrastructure
Make a website, portal, wallet or API easier for human and machine counterparties to identify and re-check.
- ·Digital businesses
- ·Platforms & marketplaces
- ·API & wallet operators
Route 7 of 12
DORA & SBOM Vendor Credentialing
Structure resilience and software supply-chain evidence for repeat vendor, buyer and regulated-sector review. Posture and evidence support — not regulatory certification.
- ·ICT vendors
- ·Software suppliers
- ·Governance teams
Route 8 of 12
Critical Infrastructure, Cyber & Operational Resilience
Organise authority, cyber posture and operational evidence for high-reliance systems and infrastructure.
- ·Critical operators
- ·Utilities & infrastructure
- ·Cyber-exposed services
Route 9 of 12
Trade Finance & Construction Outcomes
Use outcome-focused credential compositions for trade-finance readiness or construction dispute defensibility.
- ·Trade-finance teams
- ·Project owners & contractors
- ·Claims & review teams
Route 10 of 12
Humanoid Robots & Robotics Insurability
Connect robot operators, operating roles and current-state evidence for industrial, public-space and domestic robotics.
- ·Robot manufacturers
- ·Integrators
- ·Robot operators
Route 11 of 12
Robotaxis, Autonomous Freight & Drone Insurability
Structure operator, authority and dependency evidence for autonomous road, freight and aerial systems.
- ·Mobility operators
- ·Autonomous freight teams
- ·Drone fleets
Route 12 of 12
Global Trade, Containers & Marine Insurability
Connect identity, custody and risk evidence across cargo, containers, vessels and global-trade infrastructure.
- ·Shippers & carriers
- ·Port & terminal operators
- ·Cargo & marine reviewers
Boundary of claim
Choosing a route does not create proof. The guided flows produce advisory recommendations you can review and adjust; exact products and prices are confirmed in TrustOps. Payment starts provisioning — it is not proof by itself. Public proof appears only after ECZ-ID backend activation, and counterparties re-check it at the Resolver before reliance.