Passport Everywhere
Your identity should travel with the entity.
An ECZ-ID is only worth having where someone will meet it. Some of these places we serve for you, at an address that answers today. The rest are shapes you put into artefacts you already own — which is the more useful half, and the half nobody else can do for you.
- Available nowWe serve it.
- An address on the estate that answers today, free to read, with no account and no key.
- Reference patternYou implement it.
- A shape to copy into an artefact you already own. Genuinely useful, and genuinely not something we host.
- PlannedNobody yet.
- Reserved for places with a shipping date we can evidence. It is empty, and an empty column is the honest one.
Where it already resolves
Available nowWe serve it.The share page
The human record on the public Resolver: the page a person lands on when they follow the identifier. Free to read, with no account and no key.
https://resolver.ecocitizenz.org/p/{ecz_id}
Open EcoCitizenz Ltd's record(opens in a new tab — resolver.ecocitizenz.org)
The machine record
The same record as JSON, for policy engines, gateways and agents. Public reads are never metered and never authenticated.
https://api.ecocitizenz.com/api/p/{ecz_id}.json
Open the same record as JSON(opens in a new tab — api.ecocitizenz.com)
A badge plate, drawn by Core
Core renders the Business Passport plate for an organisation from the record's current state, and the plate links back to the Resolver. A site never draws badge artwork or badge states itself — the plate at the foot of this page is this address, loaded live.
https://api.ecocitizenz.com/api/badge/{parent_ecz_id}/BP.svg
A QR code and a share link
Included with every free Passport, alongside the badge, and reached from your ECZ-ID console. A QR code is what carries an identity onto a label, a carton, a rack card or a slide.
Bindings on the record itself
The record can name the public places your AI agent already appears, and basic bindings are included with every free Passport. That is the record pointing outwards; everything in the next group is the artefact pointing back.
Where you can carry it yourself
Reference patternYou implement it.Nothing on the estate crawls, reads or checks these artefacts. A reference pattern is for the person or the system that finds your artefact, and the Resolver record stays the only authority on what is true.
A README or a documentation page
One line in the repository or the docs that already describe it, linking the identifier to the record anyone can re-check.
Illustrative
[ECZ-ID {ecz_id}](https://resolver.ecocitizenz.org/p/{ecz_id})Markdown in your own README. A text link, not a rendered badge: the plate above is drawn for an organisation, not for this identifier.
A well-known file on a surface you already serve
A static file declaring the identifier, at the path this deployment publishes. No library, no dependency, and nothing new in the execution path.
/.well-known/ecz-agent.json
A field in the descriptor it already publishes
Whatever your AI agent already hands out to the systems around it can carry the identifier as one more field.
Illustrative
"ecz_id": "{ecz_id}"Your artefact, your field name. Nothing on the estate reads it, and adding it changes no behaviour.
A deployment or release annotation
A label, an annotation or a release tag on what you already ship, so the identifier travels with the artefact into whatever runs it.
A procurement or inventory record
A supplier questionnaire, an asset register or an inventory row. The identifier gives a reviewer somewhere to look, instead of a name to take on faith.
For Agent Passports, that usually means
- An agent card or manifest you publish
- A repository that contains the agent
- A marketplace or registry listing
- A documentation page that describes it
The same places the record can bind to, approached from the other side: the record can name them, and they can name the record.
Illustrative. These are shapes to copy into your own files with your own identifier — not artefacts we host, publish, check or keep in step with you.
What is coming next
PlannedNobody yet.Nothing is listed here. We publish no roadmap of places an ECZ-ID will one day travel to, because a place that has not been built is not a place. When one ships, it moves into Available now with an address you can open.
What travelling never changes
- Versions, deployments, replicas, regions and platforms of that agent are not separate Passports.
- A binding records a public place the subject already appears. Adding one never creates a second identity and never consumes AEC.
- A free Passport includes no ongoing monitor. Publishing the identifier in more places never starts one, and monitoring is never implied by a placement.
- Your ECZ-ID does not change. The places it appears in can change as often as you like.
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.