Start with the parent
The ECZ-ID Business Passport anchors the accountable organisation and creates the parent identity spine.
THE PASSPORT SYSTEM
One parent identity spine. Thirty-three attachable accountability routes.
ECZ-ID does not collapse modern operations into one vague company credential. It starts with the ECZ-ID Business Passport™ as the parent identity spine, then attaches child passports and packages where accountability actually lives: agents, APIs, software, products, robots, suppliers, custody routes, infrastructure and regulated operating surfaces.
The result is simple: resolve the accountable parent, understand the attached scope, let backend-controlled state decide current proof, and re-check Resolver before reliance.
Parent identity
Child passports
Packages
Backend state
Resolver proof
Machine-readable
INSTANT VALUE
The passport route in one glance.
Start with the Business Passport, choose the parent tier, attach the correct child passport or package, let backend-controlled state activate, then re-check Resolver before access, onboarding, procurement, insurance review, platform reliance or operational use.
Select the tier
Declared starts the route. Verified and Assured support stronger operating routes, activation and package access.
Attach the scope
Agents, APIs, products, robots, software, infrastructure and custody routes attach to the parent context.
Use packages
Packages group the right passports and add-ons around a specific reliance problem or commercial outcome.
Backend state activates
Entitlement, activation, downgrade, suspension, revocation and Resolver output remain backend-controlled.
Resolver can be checked
Humans, agents, platforms, insurers and procurement teams can re-check current public proof before reliance.
Passport route:
parent identity first, attached scope second, backend-owned state always, Resolver re-check
before reliance.
WHY THE SYSTEM EXISTS
A single company credential is too vague for modern operations.
A business may operate agents, APIs, platforms, software packages, robots, products, suppliers, fleet routes, infrastructure sites, custody flows and financial authority surfaces. One generic profile cannot tell a relying party which surface is in scope, what authority exists, or whether the current state should still be relied on.
ECZ-ID separates the parent organisation from the specific operating surfaces attached to it. The parent creates continuity. Child passports create scope. Packages create useful acquisition routes. Resolver gives a public place to re-check current proof.
THE MODEL
Parent, child, package, proof.
01
Parent Business Passport
The root organisation context: stable ECZ-ID, tier, public Resolver route and TrustOps operating context.
View Business Passport →02
Child passports
Specific accountability scopes for the surfaces the organisation operates: agents, APIs, products, robots, software, custody, infrastructure and more.
Browse child routes →03
Packages
Buyer-friendly routes that combine the right parent tier, child passports and add-ons around a reliance problem.
View packages →04
Resolver proof
The public read-only surface where humans and machines can check the current answer before reliance.
Open Resolver →PARENT TIERS
Choose the parent tier before attaching the operating scope.
Starting route
Declared Business Passport™
Free
For organisations that need a starting ECZ-ID identity route and public Resolver presence before deeper activation.
- Parent identity spine.
- Public Resolver route.
- TrustOps starting context.
- No child passport activation.
Child-passport access
Verified Business Passport™
£19.99/mo
For businesses that need child passport activation, badge provisioning, package access and stronger operating continuity.
- Everything in Declared.
- Child passport activation route.
- Badge provisioning route.
- Authority delegation context.
Higher-reliance operations
Assured Business Passport™
£49.99/mo
For regulated, insurer-facing, enterprise or high-reliance operations needing stronger evidence and lifecycle posture.
- Everything in Verified.
- Assured-tier passport routes.
- Advanced custody context.
- Priority operating route.
CHILD PASSPORTS
Thirty-three child passports across seven operating categories.
7 passports
Core digital & operational
Agent Credential, Cyber Resilience, API, AI Model, Dataset, IoT Device and Software Supply Chain.
3 passports
Product, risk & transfer
Product Passport, Custody Transfer and Risk Policy routes for object-level accountability.
3 passports
Robotics
Industrial Robot, Public-Space Robot and Domestic Robot routes for machine-operated surfaces.
5 passports
Road & freight mobility
Robotaxi, Autonomous Car, Autonomous Haulage, Cross-Border Haulage and High-Value Cargo routes.
4 passports
Aerial mobility — drones
D1, D2, D3 and D4 Drone Passport routes by operating class and weight band.
8 passports
Infrastructure-grade
Intermodal Transfer, Industrial Site, Critical Infrastructure, Financial Authority, Marine Vessel, Cargo Container, Aircraft and Aviation Component.
3 passports
Control & trust overlays
Platform Safe-Harbour, Identity Continuity and Licensed Infrastructure Operator routes.
Start route
Need the correct passport?
Use TrustOps or the Corridors page to choose the right route without manually assembling every passport.
View corridors →PUBLIC PROOF BOUNDARY
Websites explain. TrustOps operates. Backend truth decides. Resolver proves.
This website explains the passport system and routes visitors to the right surface. TrustOps handles acquisition, setup, payment, lifecycle and customer actions. Backend/Core controls entitlement, binding and current state. Resolver provides public read-only proof.
A passport route is not a blanket safety claim, compliance guarantee, audit opinion, insurance decision or universal allow/block result. It is a structured route for accountable review before reliance.
Website explains
TrustOps operates
Backend controls state
Resolver proves
Reviewer decides
PACKAGES
Packages turn passport scope into a buyer-friendly route.
Start from the problem
Buyers usually start with a reliance problem: agent review, supplier onboarding, DORA, SBOM, payout release, custody evidence or infrastructure review.
Group the right scope
Packages group the right parent, child passports, add-ons and setup path around the problem.
Route through TrustOps
TrustOps handles acquisition, setup, customer access and lifecycle actions.
Keep truth in backend
Website copy, checkout and local files do not become proof by themselves. Backend state controls proof.
Project through Resolver
Resolver gives humans and machines a public read-only place to check the current answer.
Re-check before reliance
Relying parties still apply their own policy. ECZ-ID gives them a clearer route to check.
MACHINE-READABLE BY DESIGN
Built for humans, agents, platforms and policy systems.
The passport system is designed to be understandable by people and machines. A human reviewer can read the route. An agent or policy system can follow stable links, Resolver checks and Developer Gateway guidance.
Use TrustOps for acquisition and lifecycle. Use Resolver for public proof checks. Use Developer Gateway for schemas, examples, route indexes, `.well-known` patterns and safe integration guidance.
NEXT STEP
Start with the parent, then attach the right scope.
Open TrustOps to choose the parent tier, view the Business Passport page to understand the identity spine, or open Corridors to choose the best route for your reliance problem.