Included free · For software · ECZ-ID IoT

Machine-readable identity

The same record, as JSON any program can read.

Every published IoT Passport has a machine-readable record at a stable URL. Agents, procurement tools and CI pipelines can resolve it without an account or an API key.

Get a FREE IoT Passport Verify an ECZ-ID All IoT products

Type: Included free
Price: £0 — included with every free Passport
Acquired and paid in: TrustOps
Operated in · proved by: Dashboard · Resolver

The problem

Why it matters.

Identity pages built for people are hard for software to use, so automated decisions fall back to scraping or skip the check entirely.

Built for

Cloud IoT platforms and device-management tools that need the organisation behind a device.
Procurement, vendor-risk and retailer onboarding software.
Service platforms that resolve a device before dispatching work on it.

What changes

Automated identity checks without a bespoke integration.
The same facts for people and machines.
Guard fields that tell software not to over-read the record.

What you receive

Concrete deliverables, not a vague trust score.

A stable JSON record for every published Passport.
No authentication in front of public records.
The same binding facts as the page, including when each verified binding was last verified and when a re-check is due.
The guard fields is_proof and recheck_before_reliance.

Fields a program reads

ecz_id: ECZ-XX-XXXXXX::IOT_DEVICE-XXXXXX
state: The current lifecycle state
operator: The organisation on the record
is_proof: false
recheck_before_reliance: true

Illustrative fields with placeholder values. The Developer Gateway documents the schema.

How it works

A short path from need to something usable.

Publish your Passport.
Resolve the ECZ-ID at its machine URL.
Read state, operator and bindings from the JSON.
Re-check before reliance: resolve it again before each decision that relies on it.

How it relates to your Passport

The machine record is the Resolver's JSON projection of the record Core writes. The Developer Gateway documents it; this site only explains it.

Use cases

A device-management platform attaching the current record to an enrolment.
A retailer's onboarding workflow resolving every device a supplier ships.
A service platform checking the current operator before dispatching work.
An asset register reading lifecycle state before a device is re-used or recycled.

Price

Included free, with every Passport.

£0. It is part of the free IoT Passport — permanent, not a trial, and no card is required.

After you take it

TrustOps acquires
Take the free Passport in TrustOps; your organisation's ECZ-ID Business Passport — Declared — FREE is reused or created.
Dashboard operates
Operate it in the Dashboard: publish, bind and copy your proof links.
Resolver proves
Anyone resolves the current record on the Resolver.

Privacy, security and evidence

What is collected, published and kept.

Only published, public-safe fields appear.
Every response is a reading at a time, and says so.

Boundaries

The claims stop here.

The JSON is the same projection as the page — it is not a stronger claim.
is_proof is false. Software must treat the record as current evidence, not a verdict.
A binding is verified as of its Last verified time, and the record shows its Freshness. ECZ-ID does not renew a bound binding: once its proof method's freshness window has passed, the result is history and a new binding is the fresh proof. Re-check before reliance.

Integrations and questions

Works with what you already run.

The Developer Gateway for schemas and client guidance.
The ECZ-ID Trust MCP for agents that resolve identities.

Do I need an API key?: Not for public records. Anyone can resolve them.
Where is the schema documented?: On the Developer Gateway, which documents and supports integration.

Start with a free IoT Passport.

£0 · No card required · Permanent, not a trial.

Get a FREE IoT Passport Verify an ECZ-ID