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.
Included allowance
5
managed Agent bindings
A binding is an active deployment or platform you put under management. It is not the agent itself, and replicas and versions of one deployment do not each consume a binding.
Public Resolver reads and public machine-readable records are never metered, never authenticated and never counted against any allowance.
What is included
Everything below is in the free Passport.
A permanent ECZ-ID
One persistent identifier for the agent. It does not change when you upgrade, downgrade, lapse or cancel anything.
An operator relationship
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 at /p/{ecz-id} that anyone can open without an account, an API key or a login.
A machine-readable record
The same record as JSON at /api/p/{ecz-id}.json, with a stable schema, for policy engines, gateways and other agents.
Current public state
Lifecycle state and the time it was read, published on the record rather than asserted in a badge image.
A badge and a QR code
Drawn by the badge service from the record's current state, so a stale copy cannot be pinned to a README.
The Publish Kit
The share link, the machine URL, the badge and the embed for your repository or manifest, in one place.
Five managed Agent bindings
Five managed Agent bindings are included. A binding is an active deployment or platform you put under management — not the agent itself, and not a replica or a version of one.
Re-check on demand
Current state is evaluated when someone actually asks — opening the record, re-checking from the Publish Kit — rather than by a schedule you did not ask for.
Adjacent Passport discovery
If your agent also exposes an MCP server, an API, an SDK or a workload, the flow tells you those can have identities too. 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.
How it works
Four 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.
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.
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 on a stable schema, for gateways, policy engines and other agents.
What the record carries
Example values
- ecz_id
ECZ-GB-XXXXXX::AGENT_PASSPORT-YYYYYY
The agent's permanent identifier. The type is inside the identifier.
- record_type
AGENT_PASSPORT
One of seven record types, derived from the identifier itself.
- parent
{ ecz_id, parent_tier, independently_verified, tier_meaning }
The operator, and whether the ORGANISATION has been independently verified. Never the agent.
- lifecycle_state
ACTIVE
Current published state, with as_of alongside it.
- public_bindings
[ { locator_class, locator, provenance } ]
Where this agent is declared to run, and how that was established.
- is_proof
false
The Resolver says so itself. The record is evidence to weigh, not a verdict.
- recheck_before_reliance
true
Always present. State can change after you read it.
- do_not_infer
[ … ]
The things this record explicitly does not establish. Read it.
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.
It is not an Agent Credential
The Credential is a separate specialist product with its own evidence. The Passport is the identity layer underneath 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.
Adjacent identities
Your agent is probably not the only thing you operate.
MCP
Free — available nowOne Passport is one logical MCP server.
API
Free — not open yetOne Passport is one authorised API surface.
SDK
Free — not open yetOne Passport is one logical library or SDK across languages and registries.
Service & Workload
Free — not open yetOne Passport is one enduring logical service or workload.
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
Resolve it before you wire it in. If it publishes an ECZ-ID you can see who operates it and what state the record is in. 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 five managed endpoints included, on its own allowance.
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.