Proof

Verify an ECZ-ID

Anyone can resolve an ECZ-ID to its public record, free, with no account and no API key. This page explains what that record is, what it is not, and how to read it without over-reading it.

The two routes

Every record answers to a person and to a machine

Public reads are free, unmetered and need no account and no API key. They never consume any capacity belonging to the operator of the record.

Human record

https://resolver.ecocitizenz.org/p/{ecz_id}

The published state of one identity, written to be read by a person, with the time it was read.

Machine record

https://api.ecocitizenz.com/api/p/{ecz_id}.json

The same record as JSON, for policy engines, gateways and agents.

Open the Resolver A record that resolves today The same record as JSON

The two record links go to EcoCitizenz Ltd’s own ECZ-ID. That record is proof about the company operating this site — never about you, your organisation or anything described here.

How to read one

A record publishes what is declared, not what is true

The Resolver is public, read-only proof of what is currently declared and verified, with the time it was read. A record is not a verdict, and the record itself says so and asks to be re-checked. Re-check before reliance.

No public ECZ-ID found is not a finding. It means the identifier resolves to no published record — nothing more.

An ECZ-ID does not make anything safe, certified, approved or compliant, and holding one does not make you compliant with anything.

Read the dates first

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.

Last verified: When ECZ-ID last checked the proof behind a binding. What the record shows about that binding is as of that time, not now.
Freshness: How recent that check is, shown on the record itself, so an old check is never mistaken for a current one.
Re-check due: When the binding's freshness window ends. After that date, treat the last result as history: ECZ-ID does not renew a bound binding, and a new binding is the fresh proof.
Re-check before reliance: What the record asks of every reader: open the current record again before relying on it.

A badge is a pointer to a record, not a verdict about it. Follow the badge to the record, read the record, and re-check it before you rely on it — the record itself says it is not a verdict and asks to be re-checked.

Where next

Keep going with ECZ-ID Plugin.

Get a FREE Plugin Passport