ECZ-ID BUSINESS PASSPORT

Start with the parent identity spine of ECZ-ID.

Every ECZ-ID route starts with the ECZ-ID Business Passport™. It gives the accountable organisation a stable resolver presence, a TrustOps operating context, and a parent identity spine that child passports, packages, badges and proof routes can attach to.

The Business Passport answers the first question before reliance: who is the accountable organisation, what tier is current, and where should people, agents, platforms, insurers, procurement teams and machines re-check public proof?

Start in TrustOps View corridors Open Resolver
Organisation Parent ECZ-ID Tier Authority Child passports Resolver proof

INSTANT VALUE

The ECZ-ID foundation route in one glance.

Start with the Business Passport, choose the tier that matches the reliance problem, attach child passports or packages where needed, let backend-controlled state determine current proof, then re-check Resolver before reliance.

01

Business Passport is created

The organisation gets a parent ECZ-ID identity spine and a public route for human and machine-readable resolver checks.

02

Tier context is selected

Declared establishes a starting identity route. Verified and Assured unlock stronger operating routes, child passports and package access.

03

Authority becomes accountable

ECZ-ID is designed to make accountability clearer over time: who is responsible, what authority exists, and what state is current.

04

Child passports attach

Agents, APIs, robots, products, software supply chains, custody routes and other risk objects attach to the parent Business Passport.

05

Backend-controlled state activates

The ECZ-ID backend controls entitlement, binding, activation, downgrade, suspension, revocation and public Resolver output.

06

Resolver can be re-checked

People, agents, counterparties, platforms, insurers and procurement teams can re-check the public Resolver answer before relying on the organisation or its attached routes.

Business Passport route: establish the parent identity spine, choose the right tier, attach child passports where risk lives, and re-check Resolver before reliance.

WHY THE PARENT PASSPORT MATTERS

ECZ-ID needs a root identity before it can prove object-level accountability.

A business may operate agents, APIs, products, robots, datasets, software, supply-chain routes, custody flows, infrastructure sites and financial authority surfaces. Those objects should not float without a parent accountability context.

The ECZ-ID Business Passport gives the organisation a stable identity and continuity spine. Child passports then attach to the parent so each object or operating surface can carry its own lifecycle, evidence route and Resolver-verifiable state.

CHOOSE THE PARENT TIER

Start with the Business Passport tier that matches your reliance level.

Entry identity 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.
Start Declared route

Child-passport access

Verified Business Passport™

£19.99/mo

For businesses that need child passport activation, badge provisioning, integration access and stronger operating continuity.

  • Everything in Declared.
  • Child passport activation route.
  • Badge provisioning route.
  • Authority delegation context.
Start Verified route

Higher-reliance operations

Assured Business Passport™

£49.99/mo

For regulated, insurer-facing, high-reliance or enterprise operations that need stronger evidence and lifecycle posture.

  • Everything in Verified.
  • Assured-tier passport routes.
  • Advanced custody context.
  • Priority operating route.
Start Assured route

WHAT THE BUSINESS PASSPORT ENABLES

The parent passport connects the organisation to every ECZ-ID reliance route.

Agents and KYA

Agent Credential and KYA routes connect agent identity, operator accountability and principal context back to the organisation.

Open Agent / KYA page

MCP resolver posture

MCP servers, tools, APIs and provider surfaces can become easier to review when they attach to an accountable ECZ-ID context.

Open MCP page

Corridor packages

Packages and outcome routes sit on top of the parent identity spine and the child passports needed for each reliance problem.

Open corridors

Child passports

The parent anchors child passports for APIs, products, robots, software supply chains, drones, custody flows, infrastructure and other accountable objects.

Start in TrustOps

Resolver proof

The Resolver gives counterparties and machines a public read-only surface to check current state before relying on the organisation or an attached route.

Open Resolver

Machine-readable routing

Developer Gateway gives schemas, examples and integration guidance for systems that need to understand ECZ-ID routes programmatically.

Open Developer Gateway

PUBLIC PROOF BOUNDARY

The Business Passport proves the parent identity route. Child passports prove specific operating surfaces.

This website explains and routes. TrustOps handles acquisition, setup, payment and lifecycle. The ECZ-ID backend controls entitlement, binding and current state. Resolver is the public proof surface for read-only re-checks.

The Business Passport is not a blanket safety claim, KYB replacement, insurance guarantee or proof that every object the organisation operates is acceptable. It is the parent identity and continuity context that the rest of ECZ-ID attaches to.

Website explains TrustOps operates Backend controls state Resolver proves Child passports add scope

HOW IT WORKS

From parent identity to resolver-verifiable operating routes.

01

Start with the organisation

The Business Passport gives the organisation a parent ECZ-ID identity route and a public resolver presence.

02

Choose the correct tier

Declared starts the identity route. Verified and Assured support stronger operating routes, child passports and package access.

03

Attach child passports

Agents, APIs, products, robots, software supply chains, custody routes and other risk objects attach to the parent context.

04

Add packages where needed

Packages combine the right passports and routes around a specific reliance problem, corridor or commercial outcome.

05

Backend-owned state controls proof

Resolver output depends on backend-owned activation and lifecycle state. Checkout, website copy and local files do not become proof by themselves.

06

Re-check before reliance

Humans, agents, insurers, platforms, procurement teams and policy systems can re-check Resolver before access, review, adoption or reliance.

MACHINE-READABLE ROUTE

Built for humans, agents, developers and policy systems.

The parent identity spine must be understandable by people and machines. Counterparties, platforms, insurers, agents, procurement systems and AI governance workflows need a clear way to locate the current Resolver answer.

Use TrustOps to acquire and manage the Business Passport. Use Resolver for public proof checks. Use Developer Gateway for schemas, examples, `.well-known` patterns, OpenAPI guidance and safe integration routes.

NEXT STEP

Start with the ECZ-ID Business Passport.

Open TrustOps to choose the right parent tier. Then add the child passports, packages or corridor routes needed for your reliance problem.

Start in TrustOps View corridors Open Resolver