API Estate & Ownership (monthly)
£49.99 per monthExcludes VAT
- API identities
- 50 API identities
Not yet on sale online. The price is set; the purchase route is not open yet.
View details(opens in a new tab — trustops.ecocitizenz.com)ECZ-ID API Passport™
An identity for your API that survives a new base URL.
For organisations that publish, sell or operate HTTP APIs — for people and for agents. Callers, increasingly agents, infer an API's identity from a hostname. One public ECZ-ID names the API and the organisation operating it, across versions and environments.
£0 · No card required · Permanent, not a trial.
One API Passport
- Identity
- ECZ-XX-XXXXXX::
API_PASSPORT-XXXXXX - Operator
- Your organisation, on the record as its Parent
- Public proof
- A Resolver record anyone can open, and its JSON
- Price
- £0 — no card required
Identifier shown as a pattern, not a real record. DECLARED information is self-declared; re-check the live record before you rely on it.
Four reasons to be here. Pick yours.
I operate thisYou run a API and want it to have an identity anyone can check.
I need to check thisSomeone gave you an ECZ-ID, or did not, and you have to decide whether to rely on it.
The Resolver is the only authority on an ECZ-ID’s public state, and no answer it gives is a judgement about safety. Re-check before you rely on it.
I build with thisYou want the machine surface: the record, the schema, and how to publish an identity from code.
Every public record has a machine form at https://api.ecocitizenz.com/api/p/{ecz_id}.json — no account, no key, no rate card for reading it.
I operate a platformYou have an estate, a marketplace or a fleet, and you are deciding whether this belongs in it.
Large estates, procurement evidence, OEM and distribution are a conversation, not a checkout.
Identity Beyond the Endpoint
The base URL is not the API.
Callers infer an API's identity from a hostname, which is the one thing about an API that reliably changes. The Passport identifies the API itself, and everything that depends on it keeps pointing at the same identity.
The API, its operator, and what depends on it
API Passport
One API Passport is one logical API operated by your organisation.
operated by
Your organisation
One ECZ-ID Business Passport, created free the first time you acquire any Passport. Every Passport below hangs from it, and it never changes.
is wrapped by
SDK Passport
Client SDKs wrap your API. Each SDK is a separate published subject that can name the same operator.
is served by
Service & Workload Passport
APIs are served by workloads. The service behind an API is a different enduring subject from the API it serves.
is called by
Agent Passport
Agents are becoming an API's most frequent callers, and each calling agent can present its own identity.
(opens in a new tab — agents.ecocitizenz.com)
Being called is not being authorised. Who may call your API, and with what scope, stays where you enforce it today.
The full graph, and what a line never means
Included free: Basic Graph participation and a current one-hop view.
Stays native. Nothing is replaced.
Your description, your gateway and your authorisation server all stay as they are.
- OpenAPI
- OAuth 2.x and OpenID Connect
- API gateways and API marketplaces
- Model Context Protocol (MCP)
New version, new gateway, new cloud, new hostname — the ECZ-ID stays the same.
Illustrative identifier shape
ECZ-XX-XXXXXX::API_PASSPORT-XXXXXX
Versions, environments, base URLs and gateways of that API are not separate Passports.
Bindings, versions, replicas, endpoints and deployments never consume AEC and never become a second Passport.
Illustrative. This is the shape a record of this kind can take, not a live estate — a new Passport starts with no bindings and no relationships, and shows only what its operator chooses to publish.
Reading a record is on demand, with no account and no key. Nothing here watches an entity for you; ongoing monitoring is a separate, optional capability.
The next agent to call your API will take the hostname at face value. Publish something it can resolve instead.
Free API Passport
What your free API Passport establishes.
One API Passport is one logical API operated by your organisation. Versions, environments, base URLs and gateways of that API are not separate Passports.
Included, at £0
- A persistent ECZ-ID for the API.
- Your organisation on the record as its operator — a free DECLARED Parent is created if you do not already have one.
- A public Resolver record anyone can open, and the same record as machine-readable JSON.
- A badge, a QR code and a share link.
- Basic bindings to the public places your API already appears.
- Lifecycle and current public state, evaluated on demand.
- Claim and recovery.
- Basic participation in the Digital Entity Graph.
- Essential lifecycle evidence, kept in LedgerCore.
Publishing the record is your decision. Nothing becomes public until you consent, and you can withdraw publication later.
What the record never blurs
- DECLARED ≠ VERIFIED
- A DECLARED record states what your organisation says about itself, with the date it said it. It is not the outcome of an independent check.
- Identity ≠ Binding
- The Passport identifies the API. A binding records a public place it already appears. Adding a binding never creates a second identity.
- Binding ≠ Authority
- A binding shows that a relationship has been declared. It does not grant, prove or imply authority to act.
- Parent verification ≠ API verification
- A VERIFIED or ASSURED Parent verifies your organisation. It does not verify the API.
How it works
From identity to proof, in five steps.
Create or claim the identity
Start in TrustOps with one sign-in. Your organisation's free DECLARED Parent is reused or created, and the API gets its ECZ-ID.
Configure and bind
Add the public places your API already appears — your published API documentation or an OpenAPI description you host. Each binding records where it was learned.
Prove it on the Resolver
Anyone can open the public record and its JSON, with no account and no API key — and re-check it before relying on it.
Operate
Publish the ECZ-ID where people and machines already look, and manage it from your ECZ-ID console.
Strengthen, only if useful
Parent verification, monitoring, evidence and authority are optional. None is needed to hold a Passport.
Interoperability
Works alongside what you already run.
An API Passport complements how your API is described and protected. OpenAPI describes it and OAuth protects it; the Passport publishes which API it is and who operates it.
Native where you operate. ECZ-ID where you interoperate.Keep the identities your platforms need. Add the identity everyone else can resolve.
Binds naturally with
OpenAPI
What it does: Describes an HTTP API's operations and schemas.
What ECZ-ID adds beside it: A stable identity for the API the description belongs to, across versions and base URLs.
OAuth 2.x and OpenID Connect
What it does: Delegate authorisation and authenticate a principal for a session.
What ECZ-ID adds beside it: A durable public record of the subject and its operator that outlives any token and needs none to read.
API gateways and API marketplaces
What it does: Route, meter and publish access to your API.
What ECZ-ID adds beside it: One identity for the API behind every gateway and listing it appears in.
Model Context Protocol (MCP)
What it does: Connects AI applications to tools and data through a defined client–server protocol.
What ECZ-ID adds beside it: A resolvable identity for the agent and, separately, for each MCP server it uses — each with a named operator.
ECZ-ID complements your frameworks, protocols, OAuth, cloud IAM and workload identity. It replaces none of them and stays outside the execution path.
Digital Entity Graph
API Passports, and what they connect to.
One identity, the representations it is bound to, and the other identities it legitimately relates to. Each is a separate ECZ-ID with its own operator — never a copy of this one.
Operator
Your organisation
One ECZ-ID Business Passport, created free the first time you acquire any Passport. Every Passport below hangs from it, and it never changes.
Identity
API Passport
One API Passport is one logical API operated by your organisation.
Bound representations
your published API documentation
A representation of the same subject. It never becomes a second Passport.
an OpenAPI description you host
A representation of the same subject. It never becomes a second Passport.
an API marketplace or gateway listing
A representation of the same subject. It never becomes a second Passport.
the repository the API is built from
A representation of the same subject. It never becomes a second Passport.
Relates to — separate identities, separately operated
SDK Passport
Client SDKs wrap your API. Each SDK is a separate published subject that can name the same operator.
Service & Workload Passport
APIs are served by workloads. The service behind an API is a different enduring subject from the API it serves.
Agent Passport
Agents are becoming an API's most frequent callers, and each calling agent can present its own identity.
(opens in a new tab — agents.ecocitizenz.com)
Illustrative. This is the shape a record of this kind can take, not a live estate — a new Passport starts with no bindings and no relationships, and shows only what its operator chooses to publish.
A relationship is not permission
Every line above says two things are connected. None of them says one is allowed to act for the other. Authority is granted in your own systems, and ECZ-ID does not grant it, infer it or enforce it.
What the record does establish
- Which organisation operates this entity, named on the public record.
- The organisation's own tier, and exactly what that tier covers.
- Which representations the operator has bound to this one identity.
- What the record said at the moment you resolved it.
What it never establishes
- That the entity is safe, correct, approved or certified.
- That a connected entity may act on this one's behalf.
- That any permission, scope or credential has been delegated.
- That a relationship shown here is currently active in production.
Live proof
Don't take our word for it. Resolve us.
EcoCitizenz Ltd runs this site and holds its own ECZ-ID. Everything below is read from the public record, by anyone, with no account and no key — including the parts that are empty.
ECZ-ID
activeEcoCitizenz
ECZ-GB-RBS1NW
- Operated by
- ECOCITIZENZ LTD
- Organisation tier
- VERIFIED
- Bound representations
- None published
- Public relationships
- None published
The parent organisation's identity is verified. This machine is not.
Evidence available
- Not revoked
- Ledger-anchored
- No live PulseGuard monitor
- No receipts in 30 days
Resolve(opens in a new tab — resolver.ecocitizenz.org)JSON(opens in a new tab — api.ecocitizenz.com)View Graph
Check it yourself
The same record answers for humans and machines. One is a page, the other is JSON with no authentication in front of it.
curl -s https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json | jq .resolver_v2.stateWhat it does not prove
That this company is safe to deal with, that its software is correct, or that anyone has audited it. A record establishes who an entity is and who operates it. Everything else is your decision, and you should re-check before you rely on it.
Scale
AEC — Active Entity Capacity
A free Passport exists and resolves whether or not you use any AEC. AEC is the capacity to actively manage entities in production.
What one AEC is
One AEC is one actively managed production entity with live bindings and current state.
For API Passports: An API you actively manage in production, with live bindings and current state.
One pool across families
AEC is one pool shared across your Agent, MCP, Plugin, API, SDK and logical Service & Workload identities, and your IoT product, model and fleet identities.
What AEC never does
- AEC never makes an identity more verified.
- AEC never replaces a Passport.
- AEC never changes an ECZ-ID. Your ECZ-ID does not change.
- Running out of AEC never deletes, revokes or unpublishes an identity.
Individual IoT device instances are counted separately, in IoT Fleet Capacity, and never consume AEC.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. Your organisation’s included AEC and any additional capacity are configured there.
Products
Built for API Passports
When the free Passport is not enough, these are the API products that extend it. Everything is bought and billed in TrustOps.
API Estate & Ownership Business (monthly)
£149.99 per monthExcludes VAT
- API identities
- 250 API identities
Not yet on sale online. The price is set; the purchase route is not open yet.
View details(opens in a new tab — trustops.ecocitizenz.com)Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. What you see here is what it published on .
Strengthen
Strengthen only when it is useful.
Nothing here is needed to hold a Passport, and not taking it never downgrades an identity you already hold.
Parent VERIFIED and ASSURED
Independent verification of the organisation behind your Passports. VERIFIED suits production use; ASSURED is the higher-assurance posture for larger or more sensitive estates.
Boundary: It verifies your organisation. It never verifies an agent, a server or any other child identity, and it never changes an ECZ-ID.
Included free: Every Passport starts with a free DECLARED Parent — created for you if your organisation has none.
API Estate & Ownership
Ownership and identity across your whole API estate, rather than one API at a time.
Boundary: It records ownership. It is not a security test of any API and it never implies domain control.
Also relevant to API Passports
PulseGuard
Current-state evaluation for the entities you operate. Paid tiers extend evaluation across more entities and more evaluations each month.
Included free: On-demand and event-driven evaluation of your own entities.
EvidenceCorePart of the ECZ-ID V2 build
The evidence behind each claim on a record: what supports it, where it came from, when it was checked and who may see it.
Included free: Essential evidence references are part of every free Passport.
LedgerCore
Tamper-evident retention of decisive lifecycle evidence — issuance, activation, material bindings, authority changes, suspension and revocation — with eligible evidence anchored to a permissioned, append-only ledger.
Included free: Essential LedgerCore evidence is kept for every identity, free ones included.
Digital Entity Graph and Graph Intelligence
The public-safe relationships between your organisation, its Passports and their bindings. Graph Pro, Graph Business and Enterprise Graph Intelligence add scale, history and custom analysis above the free view.
Included free: Basic Graph participation and a current one-hop view.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
Build and operate
The tools you use once it exists.
Publish the API's identity, wire it into what you already run, and check any ECZ-ID from anywhere.
Developer Gateway
Integration reference, schemas and machine-readable documentation for ECZ-ID.
Open the Developer Gateway
(opens in a new tab — developers.ecocitizenz.com)Resolver
Resolve any ECZ-ID to its public record — free, with no account and no API key.
Verify an ECZ-ID
Machine-readable record
Every record as JSON at /api/p/{ecz_id}.json, for policy engines, gateways and agents. Shown here on EcoCitizenz's own record.
Open a live machine record
(opens in a new tab — api.ecocitizenz.com)ECZ-ID console
Sign in to TrustOps to reach the Passports your organisation holds. It is where current commercial configuration lives, too.
Open your ECZ-ID console
(opens in a new tab — trustops.ecocitizenz.com)
One identity layer
Seven kinds of machine-economy entity.
Each is a separate subject with its own Passport, its own operator and its own public record. They are the same identity layer, not seven products.
Agent
AI agent
(opens in a new tab — agents.ecocitizenz.com)MCP
MCP server
Plugin
plugin
Not open yet
APIYou are here
API
Not open yet
IoT
connected device
Not open yet
SDK
SDK or library
Not open yet
Service & Workload
service or workload
Not open yet
When to give something its own Passport
When it is a different logical subject with its own operator and its own lifecycle. Something operated by someone else is a second subject. The same thing in three regions, versions or listings is still one.
Never mint a second Passport for another representation of the same thing — a version, a replica, an endpoint or a listing. Those are bindings, and they cost no capacity.
From here, the ones that most often turn out to be separate subjects are SDK, Service & Workload and Agent.
Start with the identity. Everything else is optional.
£0 · No card required · Permanent, not a trial.
Current availability
The API door is not open yet.
The API Passport is free — £0, permanently, and never sold. That is the price, and it is not what is missing. What is not ready is the door: ECZ-ID Core is not issuing API Passports yet, and the Resolver is not projecting API records yet.
So this site publishes no start link, no waiting list and no date. When both are live, the family is opened through one configuration value in the Website Factory and the control appears on every page here at once. No page on this site is rewritten to do it.
Nothing on this site can be bought in the meantime. Paid capabilities are described here and configured in TrustOps, which owns every purchase.