ECZ-ID public routing
Resolve before reliance.GETTING STARTED
ECZ-ID begins with the parent ECZ-ID Business Passport™. That parent identity spine anchors the organisation, jurisdiction, tier, operating context, and downstream proof surfaces that make a business, agent, API, product, platform, robot, supplier, or counterparty easier to resolve.
From there, TrustOps lets you add the passports, packages, bindings, and operating surfaces your organisation needs. Resolver gives relying parties a public place to check current proof before they act.
THE SIMPLE PATH
The fastest way to begin is to start in TrustOps, choose the parent ECZ-ID Business Passport™ tier that matches your required posture, then add the passports, packages, and proof surfaces that fit the operating surfaces other parties need to rely on.
You do not need to understand every passport on day one. Start with the outcome: agent identity, MCP proof posture, API authority, vendor onboarding, DORA/SBOM vendor credentialing, Digital Counterparty Infrastructure, trade finance release, construction dispute defensibility, robotics, product custody, platform reliance, or broader institutional review.
START HERE
Parent identity spine
Start with the parent identity spine. This anchors the customer, operating context, tier, jurisdiction, and downstream proof surfaces that can attach to the ECZ-ID.
Start with Business PassportAgent / MCP / API
Use ECZ-ID for agent identity, MCP server posture, API authority, manifests, repositories, tools, software supply chains, and operator-linked proof surfaces.
Start Agent / MCP pathDigital counterparty
Use Digital Counterparty Infrastructure where websites, portals, APIs, platforms, fintech surfaces, or digital operators need machine-readable, resolver-verifiable proof.
Start DCI pathDORA / SBOM
Use DORA and SBOM packages where ICT vendor posture, software liability, supplier evidence, operational resilience, and procurement review need a cleaner proof surface.
Start DORA / SBOM pathFull catalogue
ECZ-ID covers more than one wedge. Use the full catalogue for businesses, agents, APIs, cyber, products, custody, robotics, mobility, drones, infrastructure operators, DORA, SBOM, DCI, trade finance, construction disputes, platforms, insurers, and regulated counterparties.
Browse full catalogueTHE OPERATING SEQUENCE
ECZ-ID keeps each surface in its correct role. The website explains. TrustOps operates. Backend truth decides. LedgerCore™ records decisive events. PulseGuard™ checks present state. Resolver projects safe public proof for humans and machines.
WHAT TO CHOOSE FIRST
If others need to know who you are
Use the parent ECZ-ID Business Passport™ where customers, buyers, platforms, insurers, banks, or counterparties need a stable identity spine before reliance.
If software or agents act for you
Use Agent Credential, KYA, MCP, API, model, dataset, manifest, repository, and software supply-chain proof surfaces where systems act, connect, call tools, or trigger workflows.
If buyers keep asking for evidence
Use vendor onboarding, KYB-style packs, DORA, SBOM, cyber, risk, software supply-chain, and procurement evidence paths where repeated review slows revenue.
If value moves through chains
Use Product Passport, Custody Transfer, Risk Policy, trade finance, construction dispute, SBOM/DPP, IoT, robotics, mobility, drones, and high-value goods paths where state and evidence must survive later review.
WHAT HAPPENS AFTER STARTING
After acquisition, the operating lifecycle continues in TrustOps. Setup guidance, customer access, passport state, package state, binding tasks, resolver-linked assets, renewal, downgrade, suspension, revocation, and operational readiness remain controlled through the correct operating surface.
Public proof still routes to Resolver. Backend-owned truth still controls what can be projected. That boundary protects customers, relying parties, platforms, insurers, and machines from treating a marketing page as the authority.
FOR HUMANS AND AGENT-ASSISTED FLOWS
Review the parent tier, packages, add-ons, billing period, and selected proof surfaces before acquisition.
Manage passports, setup tasks, lifecycle state, binding guidance, resolver-linked assets, customer access, and operational readiness.
Route review, onboarding, procurement, insurance, risk, marketplace, and counterparty checks back to Resolver instead of relying on static claims.
Use resolver-verifiable, machine-readable proof surfaces where software needs to check state, identity, or accountability before acting.
NEXT STEP
Start with the parent ECZ-ID Business Passport™, add the capabilities your operation needs, and make the relevant proof surfaces easier to resolve before another party relies on them.
