Skip to content

Agent Trust — local inspection

Find out what the agents on this machine can reach.

ECZ-ID Agent Trust is local-first agent inventory, authority and change inspection, in your editor. It reads what is already on the machine and reports it to you.

It inspects locally and reports to you. It is not a Passport, it issues nothing, and it publishes nothing about you.

What it inspects

Three questions about a machine you already own.

Not three features. Three questions that are individually easy to answer and collectively almost never answered, because answering them by hand is dull and nothing forces it.

Inventory

What agent software is present on this machine at all.

Almost nobody can answer this from memory. Agents arrive one at a time, from different people, for different reasons, and the list nobody wrote down is the list nobody reviews.

Authority

What those agents have been given access to.

Authority is the part that drifts quietest. It gets granted once, usually in a hurry, to get something working — and then it is never re-read, because nothing prompts anyone to re-read it.

Change

What is different since the last time you looked.

A one-off audit answers a question on a Tuesday. Change inspection is what keeps that answer meaning something on the Friday after somebody installed one more thing.

The hub is the authority on scope

The three questions above describe the axis. The edition lists below summarise what each edition covers; exactly what the current build reads, and exactly what it reports, is documented on the public hub — which is also where a version number belongs. None is pinned here, deliberately, because a marketing page that pins one becomes wrong without anyone noticing.

Two editions

Community is free and complete. Pro goes deeper.

Both run locally in your editor and report to you. Community is fully functional without an account; Pro adds capability and withholds nothing from it.

Agent Trust Community

Free £0

No charge · no account · no sign-in · runs locally

  • Per-agent inventory — every agent surface in the workspace, by file and path
  • Declared tool visibility — what each agent says it can call
  • Environment key-name exposure — names only, never values
  • Workspace MCP relationships — which agents talk to which servers
  • Change detection — what moved since you last looked

Runs locally. No account, no sign-in and nothing uploaded — it reads your workspace and reports to you. Free to install and use under the ECZ-ID extension licence. The source is proprietary, so it is not open source and cannot be redistributed or modified.

Agent Trust Community on the Developer Gateway(opens in a new tab — developers.ecocitizenz.com)

Agent Trust Pro

Deeper authority analysis — still local, still reported only to you.

  • Everything in Community
  • Local Authority Graph — what every agent can reach, across its declared tools and the MCP servers beside it
  • Action Chains — consequential capability chains surfaced as chains, not as isolated findings
  • Authority Epochs — how an agent's reach changed over time, with exact diffs
  • Reciprocal Agent-to-MCP view — the same relationship read from both ends
  • Operator-applied remediation — preview a change to your own workspace configuration, apply it yourself, roll it back. Nothing changes without your action, and nothing touches a Passport, a record or a running agent.
  • Local evidence reports you can export and keep

The local Authority Graph is built on your machine, from your own workspace configuration. It is not ECZ-ID Graph Intelligence, which connects published relationships between public ECZ-ID records.

Pro features of the ECZ-ID developer inspection tooling. A software subscription: no Passport is required and none is created. Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

Covering MCP servers too? The Developer Trust Pro Bundle puts Agent Trust Pro and MCP Trust Pro on one licence key.

The boundary that matters

It reports to you. It does not report you.

Every other product in this estate ends with something published. This one does not, and the difference is the point rather than a limitation.

Local-first, and the operator is the audience

It reads what is already present on the machine and shows it to the person sitting at it. The output is a reading for you to act on, in your editor, on your terms.

It issues nothing

No ECZ-ID, no Passport, no Credential, no badge and no record comes out of it. Running it creates no identity, and never has.

It publishes nothing about you

Nothing it reads becomes a public record, a score, a rating or a directory entry. There is no resolver page for a machine, and inspecting one produces nothing that anybody else can look up.

It is not a verdict either

An inventory tells you what is there. What an agent should have access to, and what to do about it, is a question about your environment. ECZ-ID tells you what is published and by whom. What that is worth in your context is your policy's decision, not ours.

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. Agent Trust does not control an agent either. It reads configuration and reports; the one Pro capability that changes anything changes your own workspace configuration, and only when you apply it.

Three axes, not one ladder

Where this sits next to the Passport and the Authority Kit.

These are the three most confusable offers on the property, because all three are about agents. They move different things and produce different artefacts, and none of them is a step towards another.
The Agent Passport, Agent Trust and the Agent Authority & Enterprise Assurance Kit compared by axis, the question each answers and what each produces
OfferAxisThe question it answersWhat comes out of it
Free Agent PassportIdentityWho is this agent, and who operates it?A permanent ECZ-ID and a public record anyone can resolve without an account.
Agent Trust — this pageLocal inspectionWhat do the agents on this machine actually have access to?A reading of what is already on the machine, reported to the operator at the keyboard. Nothing is issued and nothing is published.
Agent Authority & Enterprise Assurance KitAuthority evidenceWhat authority has the operator delegated to this agent, and can a reviewer re-check it?A buyer-ready record of operator, authority and delegation evidence, built on the agent's Passport and pointing back to its live Resolver record. It documents authority; it never grants or approves it.

An Agent Passport is identity, not a credential. It holds no key, issues no token and grants no access: it publishes who the agent is, who operates it and what is declared about it. Evidence about the agent's authority is a separate, optional layer with its own scope. Agent Trust is neither of those: it is a reading of a machine, not a statement about an agent, and it never becomes one.

From a local finding to a buyer-ready record

What Agent Trust shows you — which tools and MCP servers the agents in your workspace declare they can reach, and how that changed — is often the first draft of the authority map an enterprise reviewer asks for. Authority findings from Agent Trust can inform the Agent Authority & Enterprise Assurance Kit, which organises the operator’s delegation evidence around the agent’s ECZ-ID. You decide what, if anything, to carry across; nothing moves from your workspace into the Kit on its own.

Where it lives

The public hub is the front door.

One address, maintained by the people who ship it, rather than a description here that ages.

ECZ-ID Agent Trust on GitHub

The official public hub. Current scope, how to get it, and what it does today are documented there and nowhere else.

EcoCitizenz-Ltd/eczid-agent-trust(opens in a new tab — github.com)

What this page will not tell you

No version number and no install command. Those are properties of a shipping build, and this is not the surface that ships it. The install links in the editions section go to the marketplace listings themselves, so they stay correct as the product ships; the hub carries the scope of the current build.

Developers

The technical reference is on the Developer Gateway.

Detectors, what each edition reads and reports, the Free and Pro comparison, and licence activation are documented there, by the people who ship it.

Questions

Is Agent Trust Community a trial?
No. Community is free, with no account and no sign-in, and is complete on its own. Pro adds capability and withholds nothing from it; if a Pro subscription lapses, only the Pro features stop.
Does it create a Passport or publish anything?
No. It reads what is already on the machine and reports to you. Agent Trust Pro is a software subscription: no Passport is required and none is created, and it writes no Passport, Resolver or entitlement truth.
Does any of my code or configuration leave the machine?
No. It runs locally and reports to the person at the keyboard. Environment variables are inventoried by name only, never by value.
I bought Pro. How do I turn it on?
Activate the licence as the Developer Gateway's Agent Trust page describes. A Developer Trust Pro Bundle key turns on both Agent Trust Pro and MCP Trust Pro.

Inspecting a machine and publishing an identity are different jobs.

Agent Trust tells you what is on your side of the line. A Passport is what someone on the other side of it can resolve. Doing either one never obliges you to do the other.

Your ECZ-ID does not change. Nothing on this page moves an identifier, a record or a resolver page.