Skip to content
ECZ-IDAPI

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.

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.

Be precise about this

No API record resolves yet

Resolver projection for this family is not live. That is a fact about the estate today, and it is not a judgement about anything.

Until projection is live there is no API identity to look up, so this page offers no lookup field for one. When the family opens, its records resolve on exactly the two routes above — the same routes, the same format, the same boundaries.

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

How to read one

A record publishes what is declared, not what is true

A Resolver record is not proof. It publishes what is currently declared and what evidence exists, with the time it was read — is_proof is false and recheck_before_reliance is true. Re-check before you rely on it.

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.

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 two guard fields on every record, is_proof and recheck_before_reliance, say so in the document itself.