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 enables trusted interactions, auditable decisions, regulatory compliance, and participation in custody chains and marketplace transactions.
What agent platforms do you support?
ECZ-ID provides starter kits for Anthropic Claude, MCP (Model Context Protocol), OpenClaw/Abacus Claw, and generic Python agents. The SDK can integrate with any agent framework.
How quickly can I deploy a verified agent?
With a starter kit, most developers go from zero to a verified agent in under an hour. The Generic Python Starter takes about 20 minutes for a minimal integration.
Verification
How does verification work?
Any party can verify an entity's ECZ-ID through Resolver. Resolver returns current identity status, resolver state, active evidence records, and operational validity in real time.
What is resolver state?
Resolver state is the current read-only verification output for an ECZ-ID record. It reflects canonical Backend/Core state and evidence-record status, not self-declared claims.
What is Resolver?
Resolver is the verification service for ECZ-ID. It provides real-time identity verification, resolver-state lookups, and evidence-record checks. 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 categories: 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™ — the active winner 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 Backend/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—developer sandbox and production—are provisioned through TrustOps. This Developer Gateway is for discovery and learning; TrustOps is for doing.
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?
Yes. TrustOps provides a sandbox environment with test credentials. You can develop, test, and validate your integration before moving to production.
Technical
What programming languages are supported?
The ECZ-ID SDK is currently available for Python 3.10+. TypeScript/Node.js support is in development. The API is REST-based and accessible from any language.
Does ECZ-ID require changes to my existing systems?
ECZ-ID is additive, not replacement. It integrates into existing systems through SDK hooks and API calls. 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 ECZ-ID SDK and starter kits are available through TrustOps. 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.