Answers for humans, agents, platforms, and teams checking ECZ-ID.

ECZ-ID is resolver-first identity, authority, state, custody, evidence, and accountability infrastructure for businesses, agents, MCP surfaces, APIs, products, platforms, insurers, regulators, and counterparties.

It helps relying parties understand who is accountable, what authority exists, what state is current, what evidence can be referenced, and where public proof should be checked before reliance.

No. ECZ-ID is not a score, rating, guarantee, approval mark, recommendation, or certification of business quality.

It is a resolver-first infrastructure layer. Badges, QR codes, pages, marketplace listings, agent profiles, and documents may route attention, but current public proof belongs in Resolver.

Use TrustOps. TrustOps is the acquisition, activation, setup, lifecycle, customer access, and payment surface for ECZ-ID.

Start in TrustOps

Use Resolver. Resolver is the public read-only verification surface for current public proof.

Humans, agents, platforms, procurement teams, insurers, regulators, reviewers, and automated systems should check Resolver before reliance.

Open Resolver

Developer Gateway is for schemas, route indexes, manifests, verifier guidance, integration patterns, and machine-readable developer material.

It helps developers, agents, platforms, marketplaces, app reviewers, and technical teams understand how ECZ-ID should be routed and integrated. It does not issue ECZ-IDs, write truth, process payment, or replace Resolver.

Open Developer Gateway

Ecocitizenz.org is the public governance and specification surface for ECZ-ID.

It publishes governance overview, issuance policy, revocation policy, authority model, system rationale, ECZ-ID specification, and passport specification. It does not issue ECZ-IDs, activate capability, process payment, or act as the authoritative verification surface.

Open governance and specifications

Agents, MCP servers, APIs, tools, repositories, packages, and software surfaces increasingly act across organisational boundaries. Before another system connects, grants access, routes work, or relies on a tool, it needs a clearer way to check the accountable operator, current state, and proof route.

ECZ-ID gives agentic and machine-operated surfaces a resolver-verifiable accountability layer: resolve the server, resolve the agent, and re-check before reliance.

ECZ-ID public surfaces are designed for humans and machines. Resolver-facing proof, route labels, public references, Developer Gateway materials, and machine-readable guidance help agents, automated workflows, platforms, and review systems understand where to check state and where not to infer authority.

Machine-readable does not mean autonomous truth writing. Backend truth remains deterministic. Resolver projects public proof. Developer Gateway explains safe integration patterns.

The ECZ-ID Business Passport™ is the parent identity spine. It anchors the organisation and creates the base from which passports, packages, bindings, proof surfaces, and lifecycle state can be attached.

Customers start with the parent identity spine in TrustOps, then add the capabilities that match their business, agent, API, product, supply-chain, platform, or institutional use case.

Child passports describe scoped accountability surfaces beneath the parent ECZ-ID. They may relate to agents, APIs, products, cyber posture, software supply chain, robotics, mobility, custody transfer, datasets, IoT, risk policy, or other defined operating surfaces.

Child passports do not create a second identity root. They remain attached to the parent ECZ-ID and must respect backend-owned state, lifecycle, eligibility, and Resolver projection rules.

Bindings connect ECZ-ID to real operating surfaces such as domains, manifests, APIs, stores, repositories, platforms, tools, or external references.

Binding truth remains backend-owned. Resolver may project safe public proof. TrustOps guides setup and lifecycle.

No. Treat them as explanation or routing surfaces only.

Website text, screenshots, badges, QR codes, marketplace listings, directory entries, social profiles, and documents can help route attention, but they should not be treated as the authority for current state. Check Resolver before reliance.

No. ECZ-ID does not replace regulators, auditors, insurers, courts, procurement teams, compliance teams, or institutional decision-makers.

ECZ-ID provides a clearer resolver-verifiable reference layer that those parties may use as part of their own review, gating, escalation, underwriting, audit, procurement, or reliance processes.

No. ECZ-ID does not guarantee safety, compliance, performance, business quality, suitability, or commercial outcomes.

It helps structure identity, authority, state, custody, evidence, and proof routing so relying parties have a better place to check before acting.