Frequently Asked Questions
Common questions about ECZ-ID, verification, provisioning, and the machine economy. Can’t find your answer? Contact us through TrustOps.
General
What is ECZ-ID?
ECZ-ID is trust infrastructure for the machine economy. It provides resolver-verifiable identity for AI agents, IoT devices, autonomous vehicles, products, drones, critical infrastructure, and every entity that needs to prove who it is.
What is EcoCitizenz?
EcoCitizenz is the infrastructure company behind ECZ-ID. We build the trust layer that the machine economy needs to function safely, transparently, and at scale.
Is ECZ-ID a blockchain product?
ECZ-ID is infrastructure-agnostic. It focuses on resolver-verifiable identity, attestation, and provenance. The underlying storage and verification mechanisms are designed for performance, auditability, and standards alignment—not tied to any specific technology stack.
What domains does ECZ-ID cover?
Nine domains: APIs, AI, Data & Software; IoT & Connected Systems; Products, Custody & Risk; Robotics & Humanoids; Vehicles & Mobility; Drones & Aerial Systems; Trade, Shipping & Infrastructure; Platforms, Marketplaces & Control Overlays; and Passport Families & Packages.
Agents
Why should I give my AI agent an identity?
Without resolver-verifiable identity, your agent is an anonymous actor in critical systems. Resolver-verifiable identity gives counterparties something to check: the accountable operator, declared authority, and current public state. It supports review, audit, and due-diligence processes — local policy decides whether that evidence is sufficient.
What agent platforms do you support?
The Developer Gateway publishes documented integration patterns for Anthropic Claude, MCP (Model Context Protocol), OpenClaw/Abacus Claw, and generic Python agents. Integration uses public manifests, JSON Schemas, TrustOps endpoints, and Resolver checks — REST-style surfaces that are accessible from any language. There is no public ECZ-ID SDK at this time.
How quickly can I deploy a verified agent?
Setup time depends on your stack and on TrustOps review and activation. The documented patterns are designed to keep your integration work small, but verification state is controlled by ECZ-ID core systems and appears at the Resolver only after backend activation — no fixed time is promised.
Verification
How does verification work?
Any party can verify an entity's ECZ-ID through Resolver. Resolver returns the identity status, resolver state, active evidence records, and operational validity that are current at the time of the request. Re-check before reliance.
What is resolver state?
Resolver state is the current read-only verification output for an ECZ-ID record. It reflects canonical ECZ-ID Core state and evidence-record status, not self-declared claims.
What is Resolver?
Resolver is the public proof surface for ECZ-ID. It provides current-state identity lookups, resolver-state projection, and evidence-record checks — read-only, with no checkout and no setup. Resolver is the verify side of the ECZ-ID model.
Packages, Passports & Add-Ons
How many passport families are there?
There are exactly 7 canonical passport families: Digital & Operational; Product, Risk & Transfer; Robotics; Road & Freight Mobility; Aerial Mobility; Infrastructure-Grade; and Control & Trust Overlays. These contain 33 child passports total.
How many packages are there?
There are 33 active commercial packages: 18 core bundles (includes KYA Ready Pack™), 8 advanced / accelerator packages (includes ECZ-ID Digital Counterparty Infrastructure Pack™ for the digital-counterparty path), and 7 extension packages (DORA Managed, DORA Enterprise, SBOM Managed, SBOM Enterprise, DORA/SBOM Enterprise Suite, Trade Finance Release Pack™, Construction Dispute Resolution Pack™). There are also 9 add-ons / companion products: Insurability Readiness™ (derived, not purchasable), Procurement Evidence Add-on, PulseGuard Live Trust Add-on, Software & API Trust Add-on, Counterparty Verification API, ECZ-ID LedgerCore Evidence Anchoring Add-on™, ECZ-ID Resolver Reliance Receipts Add-on™, ECZ-ID Authority Delegation Register Add-on™, and ECZ-ID Domain & Origin Binding Add-on™. The packages are the commercial acquisition paths that unlock relevant child passports in TrustOps.
What is ECZ-ID Insurability Readiness™?
ECZ-ID Insurability Readiness™ is a derived add-on on the parent passport. It is NOT a package. It is NOT purchasable or manually editable. It is automatically computed from active passport state, evidence state, and canonical ECZ-ID Core rules—indicating readiness for insurer engagement.
What is the KYA Ready Pack™?
KYA Ready Pack™ is the Know-Your-Agent readiness pack. It is a core bundle counted among the 33 total packages and includes Agent Credential, Identity Continuity, and API Passport for agent-first onboarding.
What is the ECZ-ID Business Passport™?
The ECZ-ID Business Passport™ is the parent passport—the root credential for every organisation. All child passports, packages, and derived add-ons attach to this parent. Every organisation starts here.
TrustOps & Provisioning
What is TrustOps?
TrustOps is the provisioning and operations platform for ECZ-ID. All identity provisioning, credential management, pricing, sales, and production deployment happens through TrustOps.
Where do I get credentials?
All credentials are provisioned through TrustOps after setup and backend activation. This Developer Gateway is for discovery and learning; TrustOps is for doing. There is no self-serve API-key issuance on this site.
Why does the site link to /start instead of the TrustOps homepage?
Every customer acquisition link on this gateway points to trustops.ecocitizenz.com/start—the onboarding entry point. This ensures new users land directly in the acquisition flow rather than a generic homepage. The /start route is the correct entry where package selection, payment, and credentialing happen in TrustOps.
How much does ECZ-ID cost?
Parent tiers are Declared (Free), Verified (£19.99/month), and Assured (£49.99/month). Child passport, package, and enterprise-service pricing is shown in TrustOps and varies by what you activate. Use TrustOps /start for the current commercial path.
Can I try ECZ-ID before committing?
You can explore a great deal before paying anything: the MCP Verifier is free, the TrustOps URL analysis and setup manifest are publicly readable, the Declared parent tier is free, and every schema and integration pattern on this site is public. There is no separate public sandbox environment at this time.
Technical
What programming languages are supported?
Integration is language-agnostic: the public surfaces are REST-style endpoints, JSON manifests, and JSON Schemas, accessible from any language. There is no public ECZ-ID SDK at this time; the documented patterns on this site show direct integration.
Does ECZ-ID require changes to my existing systems?
ECZ-ID is additive, not replacement. It integrates into existing systems through public manifests, API calls, and Resolver checks. No rip-and-replace required.
What standards does ECZ-ID align with?
ECZ-ID is designed to align with EU Digital Product Passport requirements, W3C Decentralised Identifiers (DIDs), ISO identity standards, and emerging machine identity frameworks.
Is ECZ-ID open source?
The integration patterns and schemas on this site are public. The infrastructure is operated by EcoCitizenz as a managed service. Contact TrustOps for licensing details.
Still Have Questions?
Our team is available through TrustOps to answer technical questions, discuss architecture patterns, and help plan your deployment.
Ready to Get Started?
Start with agents, explore domains, or go directly to TrustOps for provisioning.