Catalog

The ECZ-ID commercial estate, organised for discovery

Browse parent passport tiers, child passports, packages, and add-ons. Developer Gateway documents and routes; TrustOps handles acquisition, setup, payment, and lifecycle; Resolver is the sole public proof surface.

ECZ-ID is designed to work across developer, repository, browser, verification, and AI infrastructure environments.

Parent Passport Tiers

3 entries

Declared, Verified, Assured. The parent identity spine every child passport, package, and add-on attaches to.

Open hub →

Child Passports

33 entries

Resolver-verifiable identity for the discrete objects an organisation needs to make legible (agents, APIs, models, datasets, products, robots, vehicles, drones, infrastructure, control overlays).

Open hub →

Packages

33 entries

Bundled adoption packs that close real commercial gates by composing the relevant passports.

Open hub →

Add-ons

9 entries

Companion products and derived readiness signals. Insurability Readiness™ is derived, free, and non-sellable.

Open hub →

Recommendation

Find your recommended starting point

Enter your website URL. TrustOps will use it to recommend a starting point. Developer Gateway sends the URL only; TrustOps handles the recommendation, setup, payment, and lifecycle controls.

Why this product may apply: recommendations come from TrustOps URL analysis. This page documents the model.
Learn more: browse the catalog hubs to read product intelligence on Developer Gateway.
Continue setup in TrustOps: acquisition, activation, payment, and lifecycle happen in TrustOps.

Developer Gateway does not host checkout, change canonical state, issue credentials, or replace Resolver proof. Current proof must be checked in Resolver.

ECZ-ID separates setup, verification state, and public proof. Developer Gateway documents and routes; TrustOps handles setup; Resolver remains the public proof surface. Re-check before reliance.