ECZ-ID contact routing

Contact the right surface before the wrong route costs time.

EcoCitizenz.com explains ECZ-ID and routes humans, agents, platforms, procurement teams, insurers, regulators, developers, and counterparties to the correct operating surface. Use this page for company enquiries. Use TrustOps, Resolver, Developer Gateway, or ecocitizenz.org when those surfaces are the correct route.

Surface rule

Websites explain. TrustOps operates. Backend truth decides. Resolver proves.

Contact messages do not issue ECZ-IDs, activate capability, change state, prove validity, approve reliance, or replace Resolver checks. They help route the right enquiry to the right place.

01

Acquisition, activation, lifecycle, and payment

Use TrustOps to start, activate, manage lifecycle, access customer setup, and handle operational or commercial actions.

Start in TrustOps ↗
02

Public proof and current state checks

Use Resolver when a person, platform, agent, insurer, regulator, buyer, or automated system needs to check current public proof before reliance.

Open Resolver ↗
03

Developer, agent, MCP, API, and platform implementation

Use Developer Gateway for schemas, route indexes, machine-readable guidance, integration patterns, agent-facing material, and implementation support.

Open Developer Gateway ↗
04

Governance, specifications, and formal public reference

Use ecocitizenz.org for the formal governance and specification layer. It publishes rules and reference material, but does not issue ECZ-IDs or serve as Resolver.

Open governance & specifications ↗

Company enquiry

Send a message when contact is the correct route.

Use the form for partnership, media, general company, commercial discussion, website, or routing questions. Do not use the form to request proof, change state, activate capability, submit secrets, upload source code, or rely on private confirmation.

Do not paste secrets or sensitive material. Do not submit private keys, credentials, source code, confidential evidence, payment details, personal documents, or regulated data through this form.

Contact responses are not Resolver proof, backend state changes, approval decisions, certification, or reliance confirmation.

Human and machine routing

Agents and automated systems should route by job, not by page title.

Use TrustOps for acquisition and lifecycle action. Use Resolver for current public proof. Use Developer Gateway for implementation. Use ecocitizenz.org for governance and specifications. Use this contact page only for company enquiries where a message is appropriate.