ECZ-ID IoT Device Passport™
For manufacturers and operators of connected devices, device models and fleets. A device identity has to be recognisable without becoming a way to locate or impersonate the device. The public record names the product and who stands behind it — never a raw serial number, MAC address or location.
£0 · No card required · Permanent, not a trial.
One IoT Passport
Identifier shown as a pattern, not a real record. DECLARED information is self-declared; re-check the live record before you rely on it.
The Resolver is the only authority on an ECZ-ID’s public state, and no answer it gives is a judgement about safety. Re-check before you rely on it.
Every public record has a machine form at https://api.ecocitizenz.com/api/p/{ecz_id}.json — no account, no key, no rate card for reading it.
Large estates, procurement evidence, OEM and distribution are a conversation, not a checkout.
Device-to-Fleet
A fleet is many Passports, never one. Each device identity binds to the instance that is actually running, reports into the services you operate, and resolves back to your organisation.
IoT Passport
One IoT Passport is one physical device, or one device identity module, operated by your organisation. A fleet is many Passports.
is bound as
An active device-instance binding
One running instance of that device identity, bound to the Passport rather than duplicating it.
reports into
Service & Workload Passport
Fleets report into cloud services and workloads, which are separate enduring subjects with their own Passports.
operated by
Your organisation
One ECZ-ID Business Passport, created free the first time you acquire any Passport. Every Passport below hangs from it, and it never changes.
The public record names the product and the organisation behind it. It carries no serial number, no MAC address, no key material and no location, so nothing in this chain helps an outsider reach a unit.
The full graph, and what a line never means
Included free: Basic Graph participation and a current one-hop view.
Provisioning, device certificates and device authentication stay exactly where they already are.
Illustrative identifier shape
ECZ-XX-XXXXXX::IOT_DEVICE-XXXXXX
Firmware versions, MAC and IP addresses, and the gateways and hubs a device registers with are not separate Passports.
Bindings, versions, replicas, endpoints and deployments never consume AEC and never become a second Passport.
IoT Fleet Capacity: Individual device instances are counted in IoT Fleet Capacity, which is separate from AEC and never consumes it.
Illustrative. This is the shape a record of this kind can take, not a live estate — a new Passport starts with no bindings and no relationships, and shows only what its operator chooses to publish.
Reading a record is on demand, with no account and no key. Nothing here watches an entity for you; ongoing monitoring is a separate, optional capability.
Someone holding your device has no way to check who stands behind it. A free Passport is an answer that is safe to print on it.
Free IoT Passport
One IoT Passport is one physical device, or one device identity module, operated by your organisation. A fleet is many Passports. Firmware versions, MAC and IP addresses, and the gateways and hubs a device registers with are not separate Passports.
Publishing the record is your decision. Nothing becomes public until you consent, and you can withdraw publication later.
How it works
Start in TrustOps with one sign-in. Your organisation's free DECLARED Parent is reused or created, and the connected device gets its ECZ-ID.
Add the public places your connected device already appears — a manufacturer product page or published device documentation. Each binding records where it was learned.
Anyone can open the public record and its JSON, with no account and no API key — and re-check it before relying on it.
Publish the ECZ-ID where people and machines already look, and manage it from your ECZ-ID console.
Parent verification, monitoring, evidence and authority are optional. None is needed to hold a Passport.
Interoperability
An IoT Passport complements device platforms and product identifiers. It publishes who operates the device and, where declared, its manufacturer and model, and leaves device authentication where it already lives.
Native where you operate. ECZ-ID where you interoperate.Keep the identities your platforms need. Add the identity everyone else can resolve.
Binds naturally with
What it does: Provision, connect and manage individual devices.
What ECZ-ID adds beside it: A public identity for the product, model or fleet that carries no raw serial number, MAC address or location.
What it does: Authenticate an individual device to your services.
What ECZ-ID adds beside it: A printable public identity for the product or fleet — never a device's key material.
What it does: Identify trade items across supply chains.
What ECZ-ID adds beside it: An operator-linked identity for the connected product that can be resolved alongside its product identifier.
ECZ-ID complements your frameworks, protocols, OAuth, cloud IAM and workload identity. It replaces none of them and stays outside the execution path.
Digital Entity Graph
One identity, the representations it is bound to, and the other identities it legitimately relates to. Each is a separate ECZ-ID with its own operator — never a copy of this one.
Your organisation
One ECZ-ID Business Passport, created free the first time you acquire any Passport. Every Passport below hangs from it, and it never changes.
IoT Passport
One IoT Passport is one physical device, or one device identity module, operated by your organisation. A fleet is many Passports.
a manufacturer product page
A representation of the same subject. It never becomes a second Passport.
published device documentation
A representation of the same subject. It never becomes a second Passport.
a public model or catalogue entry
A representation of the same subject. It never becomes a second Passport.
API Passport
Devices report to, and are managed through, APIs. The API is identified separately from the devices that use it.
Service & Workload Passport
Fleets report into cloud services and workloads, which are separate enduring subjects with their own Passports.
Agent Passport
Where an agent acts on devices, the agent is a separate subject with its own Passport — never part of the device's.
(opens in a new tab — agents.ecocitizenz.com)Illustrative. This is the shape a record of this kind can take, not a live estate — a new Passport starts with no bindings and no relationships, and shows only what its operator chooses to publish.
Every line above says two things are connected. None of them says one is allowed to act for the other. Authority is granted in your own systems, and ECZ-ID does not grant it, infer it or enforce it.
Live proof
EcoCitizenz Ltd runs this site and holds its own ECZ-ID. Everything below is read from the public record, by anyone, with no account and no key — including the parts that are empty.
ECZ-ID
activeEcoCitizenz
ECZ-GB-RBS1NW
The parent organisation's identity is verified. This machine is not.
Evidence available
The same record answers for humans and machines. One is a page, the other is JSON with no authentication in front of it.
curl -s https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json | jq .resolver_v2.stateThat this company is safe to deal with, that its software is correct, or that anyone has audited it. A record establishes who an entity is and who operates it. Everything else is your decision, and you should re-check before you rely on it.
Scale
A free Passport exists and resolves whether or not you use any AEC. AEC is the capacity to actively manage entities in production.
One AEC is one actively managed production entity with live bindings and current state.
For IoT Passports: An IoT product, model or fleet identity you actively manage in production.
AEC is one pool shared across your Agent, MCP, Plugin, API, SDK and logical Service & Workload identities, and your IoT product, model and fleet identities.
IoT Fleet Capacity: Individual device instances are counted in IoT Fleet Capacity, which is separate from AEC and never consumes it.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. Your organisation’s included AEC and any additional capacity are configured there.
Products
When the free Passport is not enough, these are the IoT products that extend it. Everything is bought and billed in TrustOps.
£99.99 per monthExcludes VAT
Not yet on sale online. The price is set; the purchase route is not open yet.
View details(opens in a new tab — trustops.ecocitizenz.com)£299.99 per monthExcludes VAT
Not yet on sale online. The price is set; the purchase route is not open yet.
View details(opens in a new tab — trustops.ecocitizenz.com)Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. What you see here is what it published on .
Strengthen
Nothing here is needed to hold a Passport, and not taking it never downgrades an identity you already hold.
Independent verification of the organisation behind your Passports. VERIFIED suits production use; ASSURED is the higher-assurance posture for larger or more sensitive estates.
Boundary: It verifies your organisation. It never verifies an agent, a server or any other child identity, and it never changes an ECZ-ID.
Included free: Every Passport starts with a free DECLARED Parent — created for you if your organisation has none.
Identity and lifecycle for the device relationships across your fleets.
Boundary: It manages identity relationships — not telemetry, firmware updates or device management — and it never publishes a device's raw identifiers.
Current-state evaluation for the entities you operate. Paid tiers extend evaluation across more entities and more evaluations each month.
Included free: On-demand and event-driven evaluation of your own entities.
The evidence behind each claim on a record: what supports it, where it came from, when it was checked and who may see it.
Included free: Essential evidence references are part of every free Passport.
Tamper-evident retention of decisive lifecycle evidence — issuance, activation, material bindings, authority changes, suspension and revocation — with eligible evidence anchored to a permissioned, append-only ledger.
Included free: Essential LedgerCore evidence is kept for every identity, free ones included.
The public-safe relationships between your organisation, its Passports and their bindings. Graph Pro, Graph Business and Enterprise Graph Intelligence add scale, history and custom analysis above the free view.
Included free: Basic Graph participation and a current one-hop view.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
Build and operate
Publish the connected device's identity, wire it into what you already run, and check any ECZ-ID from anywhere.
Integration reference, schemas and machine-readable documentation for ECZ-ID.
Open the Developer Gateway
(opens in a new tab — developers.ecocitizenz.com)Resolve any ECZ-ID to its public record — free, with no account and no API key.
Verify an ECZ-ID
Every record as JSON at /api/p/{ecz_id}.json, for policy engines, gateways and agents. Shown here on EcoCitizenz's own record.
Open a live machine record
(opens in a new tab — api.ecocitizenz.com)Sign in to TrustOps to reach the Passports your organisation holds. It is where current commercial configuration lives, too.
Open your ECZ-ID console
(opens in a new tab — trustops.ecocitizenz.com)One identity layer
Each is a separate subject with its own Passport, its own operator and its own public record. They are the same identity layer, not seven products.
Agent
AI agent
(opens in a new tab — agents.ecocitizenz.com)MCP
MCP server
Plugin
plugin
Not open yet
API
API
Not open yet
IoTYou are here
connected device
Not open yet
SDK
SDK or library
Not open yet
Service & Workload
service or workload
Not open yet
When it is a different logical subject with its own operator and its own lifecycle. Something operated by someone else is a second subject. The same thing in three regions, versions or listings is still one.
Never mint a second Passport for another representation of the same thing — a version, a replica, an endpoint or a listing. Those are bindings, and they cost no capacity.
From here, the ones that most often turn out to be separate subjects are API, Service & Workload and Agent.
£0 · No card required · Permanent, not a trial.
Read this as carefully as the rest
An ECZ-ID IoT Device Passport is a persistent, resolver-verifiable identity for something you operate. It records who operates it, what has been declared and bound, and what the current public state is. It is not a substitute for, and must never be presented as replacing:
An ECZ-ID does not make a device safe, secure or correct, and it is not a certification, approval or test result. Your policy decides what to do with what the record says.
Current availability
The IoT Passport is free — £0, permanently, and never sold. That is the price, and it is not what is missing. What is not ready is the door: ECZ-ID Core is not issuing IoT Passports yet, and the Resolver is not projecting IoT records yet.
So this site publishes no start link, no waiting list and no date. When both are live, the family is opened through one configuration value in the Website Factory and the control appears on every page here at once. No page on this site is rewritten to do it.
Nothing on this site can be bought in the meantime. Paid capabilities are described here and configured in TrustOps, which owns every purchase.