Free Agent Passport
£0. No card required. Permanent.
Identity is free. A Passport is never metered, and issuing one consults no entitlement. This is not a trial, a freemium tier that expires, or a discount that ends. It is how the identity layer is defined.
One Agent Passport is one logical AI agent operated by your organisation. Versions, deployments, replicas, regions and platforms of that agent are not separate Passports.
Before you start
£0 · No card required · Permanent, not a trial.
Publishing the record is your decision. Nothing about your agent becomes public until you consent to it, and what you publish stays under your control afterwards.
Public Resolver reads and public machine-readable records are never metered, never authenticated and never counted against any allowance.
Free · Permanent · No card
What you get, free.
Free · Permanent · No card
Included free
- A permanent ECZ-ID for this agent
- A live public Resolver page
- A canonical machine-readable record
- A website badge and a QR code
- Publish Kit for your agent card and website
- Manage from your ECZ-ID account
Nothing is published until you confirm it.
One subject
One agent, one Passport
For example, your customer-support agent keeps one Passport whichever version, deployment or platform it runs on.
A new version, deployment, replica, region or platform is not a new Passport.
What is included
Everything below is in the free Passport.
A permanent ECZ-ID
One persistent identifier for one logical agent. It does not change when you redeploy, rename, move region, or strengthen, lapse or cancel anything.
An accountable operator
The agent is published against the organisation that runs it, so the record answers who is accountable and not only what the software is called.
A free DECLARED Parent if you need one
If your organisation has no ECZ-ID yet, a DECLARED Parent is created during the same flow at no charge. If you already have one, it is reused rather than duplicated.
A public Resolver record
A human-readable page that anyone can open without an account, an API key or a login.
A machine-readable record
The same record as JSON; its fields are documented on the Developer Gateway. Readable by other agents, platforms and your own review tooling. Whatever they decide from it is their policy; ECZ-ID takes no part in it.
Current public state, on demand
Lifecycle state and the time it was read, published on the record and evaluated whenever someone opens or re-checks it — not asserted in a badge image.
A live badge, QR code and share link
Drawn from the record's current state, so a stale copy cannot be pinned to a README. The Publish Kit puts the share link, machine URL, badge and embed in one place.
Basic bindings
Record the public places your agent already appears — an agent card or manifest, a repository, a registry listing, a documentation page. Each binding says where it was learned.
Claim and recovery
A route to claim an identity that belongs to your organisation, and to recover access to it, so the record stays with the operator that is accountable for it.
Digital Entity Graph participation
The agent takes part in the Digital Entity Graph, with a current one-hop view of the published relationships around it.
Essential lifecycle evidence
Essential evidence is kept in LedgerCore for every identity, free ones included, as local records; ledger anchoring is not live yet.
Manage from your ECZ-ID account
Your free Agent Passport is managed from your ECZ-ID account on TrustOps, reached with the single sign-in the free flow already asked you for. There is no second account.
Adjacent Passport discovery
If your agent also calls an MCP server or an API, or ships as an SDK or a workload, the flow tells you those can have identities of their own. You choose. Nothing is issued for you.
The operator relationship
An agent identity is only useful if someone stands behind it.
You get a free DECLARED Parent if you need one
A DECLARED Parent is a truthful self-declaration by the organisation. It is free, and one is created for you if you do not already have one.
And we say plainly what that does not mean
DECLARED does not mean independently verified. It records what an organisation says about itself, with the date it said it — not the outcome of a check.
Identity, authority, operator
The Passport identifies the agent and names the organisation accountable for it. Authority is delegated by the operator, inside the operator's own systems — OAuth, IAM, MCP and API configuration. ECZ-ID can publish what the operator declares about that delegation; it never grants, enforces or revokes it.
Identifying an agent is not controlling it. ECZ-ID does not authorise, restrict, supervise, pause or stop what an agent does — its operator and the party relying on it stay responsible for that.
How it works
Five steps, one sign-in.
Sign in once
One authentication. No card, no billing details, and no sales step in between.
Your organisation is identified
If your organisation already has an ECZ-ID it is reused, not duplicated. If it does not, a free DECLARED Parent is created in the same flow.
Describe the agent
One logical agent: what it is called and where it runs. Not one per replica, per version or per region.
The Passport is issued
You get a permanent ECZ-ID, a public resolver page, a machine-readable record and the Publish Kit. Submit the same agent again and you get the same identity back rather than a second one.
Manage from your ECZ-ID account
Sign in to TrustOps with the sign-in you already used to manage what you hold. No second account, and nothing else to set up.
What you get
A public record anyone can resolve, and re-check.
Two addresses, both public, neither requiring an account or an API key. One for people, one for machines.
Resolve before reliance
- The Resolver
- The live public record — the route to current ECZ-ID proof — read at the moment you check it, by anyone, without an account.
- The machine-readable record
- A deterministic, machine-readable projection of that same record, for software and other agents.
- A badge or QR code
- A route back to the live record — never a copy of it, and never proof on its own.
For people
resolver.ecocitizenz.org/p/ECZ-GB-XXXXXX::AGENT_PASSPORT-YYYYYY
A readable page: the agent, its operator, current state, and what the record does not establish.
For machines
api.ecocitizenz.com/api/p/ECZ-GB-XXXXXX::AGENT_PASSPORT-YYYYYY.json
The same record as JSON; its fields are documented on the Developer Gateway. Readable by other agents, platforms and your own review tooling — whatever they decide is their policy; ECZ-ID takes no part in it.
What the record carries
In plain English
- The agent's identifier
ECZ-GB-XXXXXX::AGENT_PASSPORT-YYYYYY
The agent's permanent ECZ-ID. The type is inside the identifier.
- What kind of record it is
An Agent Passport
The record's type, derived from the identifier.
- Who operates it
The organisation behind the agent
The operator, and whether the ORGANISATION has been independently verified. Never the agent.
- Its current state, and when it was read
For example, active — with the time of reading
The state published right now, with the time it was read alongside it.
- Declared bindings, and how each was established
Where the agent is declared to run
Where this agent is declared to run, and how that was established.
- What the record does not establish
Listed on the record itself
The things this record explicitly does not establish. Read it.
- Proof status
A current reading, not proof
The Resolver says so itself. The record is evidence to weigh, not a verdict — and state can change after you read it, so re-check before relying on it.
Field reference on the Developer Gateway(opens in a new tab — developers.ecocitizenz.com)
The record is not proof. It publishes what is currently declared and what evidence exists, with the time it was read. Re-check the live record before you rely on it.
Re-check before reliance. State can change between the moment a badge is drawn and the moment an agent acts.
Example identifiers on this page use the placeholder form ECZ-GB-XXXXXX and are not real records.
Boundaries
What a free Passport is not.
It is not a verification of your agent
The Passport publishes a declared identity and an operator relationship. It does not assess the agent's behaviour, its permissions or its safety, and it gives ECZ-ID no say over what the agent does.
It is not a credential or a permission
It holds no key, issues no token and grants no access. Authority is delegated by the operator inside its own systems; the Passport publishes who the agent is and who is accountable for it.
It is not a certification
There is no scheme, no seal and no approval. An ECZ-ID makes an agent identifiable and re-checkable, not approved.
Parent + seven FREE Passport families
Your agent is probably not the only thing you operate.
The Parent — your organisation
Every Passport is linked to one organisation, its Parent. A DECLARED Parent is free and created for you if you do not have one. VERIFIED and ASSURED independently check the organisation — never the agent.
Agent
FREEECZ-ID Agent Passport™
Free door open
One Passport is one logical AI agent operated by your organisation.
The agent itself. Versions, deployments, replicas, regions and platforms are bindings, never separate Passports.
MCP
FREEECZ-ID MCP Passport™
Free door open
One Passport is one logical MCP server operated by your organisation.
Agents call MCP servers for tools and data. The server is its own subject, with its own operator and its own Passport.
API
FREEECZ-ID API Passport™
Free door open
One Passport is one logical API operated by your organisation.
Agents act through APIs. An API Passport identifies the surface an agent calls, separately from the agent calling it.
Plugin
FREEECZ-ID Plugin Passport™
Free door open
One Passport is one logical plugin, extension, action or store app your organisation publishes.
Agents ship as, or inside, plugins and extensions. The plugin is identified once, across every store it is listed in.
Service & Workload
FREEECZ-ID Service & Workload Passport™
Free door open
One Passport is one logical service or workload your organisation operates.
Agents run as services and workloads. The workload that hosts an agent is a different enduring subject from the agent.
SDK
FREEECZ-ID SDK Passport™
Free door open
One Passport is one logical SDK, library or package your organisation publishes.
Agents are built with SDKs. The library is its own subject, published by its own maintainer, across every registry it ships to.
IoT
FREEECZ-ID IoT Device Passport™
Free door open
One Passport is one physical device, or one device identity module, operated by your organisation.
Agents increasingly act on connected devices. The device is identified in its own right; a fleet is many Passports, never one.
FREE is the price of every one of the seven families. What changes between them is the subject a Passport identifies, never the price.
Agents and MCP
Does your agent use an MCP server?
An agent and the MCP server it calls are two different things, run by two parties who may not be the same. Each can hold its own identity, with its own operator on the record.
You use someone else’s MCP server
Look it up before you wire it in. If it publishes an ECZ-ID you can see who operates it and what state the record is in; what you do with that is your policy. If it does not, that is not a finding against it — most servers have no ECZ-ID yet.
You operate the MCP server yourself
Give it its own FREE MCP Passport. Same organisation, same Parent, a separate identity for a separate thing, with its own operator on the record.
Adjacent Passports are suggested, never issued for you. If your agent also exposes an MCP server or an API, you choose whether to give those an identity too.
When you need more
The Passport stays FREE. These build on it.
A buyer or reviewer asks what authority the agent has been delegated
ECZ-ID Agent Authority & Enterprise Assurance Kit
Turn agent authority, operator and delegation evidence into a buyer-ready assurance record.
Counterparties meet your agent and need a path to the organisation behind it
DCI — Digital Counterparty Infrastructure
Make the agent a counterparty meets easy to identify, inspect and re-check.
You actively manage more agents in production
AEC — Active Entity Capacity
Operate more agents in production without turning capacity into identity.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
£0, permanent, and it takes one sign-in.
No card required. Nothing in it expires, and your ECZ-ID never changes afterwards.
Where next
Where next.
- Agent use casesSerious agent scenarios, and what serves each one.Go
- Every product for agentsEach with its live state, its price and its own TrustOps route.Go
- KYA AuthorityThe Agent family's Know-Your-Agent plan.Go
- Verify an ECZ-IDResolve before reliance: read the live public record.Go
£0 · No card required · Permanent, not a trial.