Universal platform · Scale

AEC — Active Entity Capacity

Operate more agents in production without turning capacity into identity.

AEC is the operating-capacity layer for ECZ-ID. Passports stay free; AEC is what expands the number of entities you can actively manage with live bindings, state and operational services.

Open in TrustOps Talk to us

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

For agent operators

Why it matters when the subject is an AI agent.

Your first agents need nothing bought. AEC matters when the number of agents you actively manage in production grows. It counts agents, not their copies: every version, replica, region and deployment of the same logical agent stays one entity, and one Passport.

The questions it helps answer

What counts as one actively managed agent?
Do replicas, versions or deployments use up capacity?
What happens when we reach the limit?

Fit

Who it is for, and what changes.

Best for

Teams moving from a handful of agents to a production estate.
Organisations that want one predictable capacity model across Agent, MCP, Plugin, API, IoT, SDK and Service & Workload.
Operators that need headroom without creating another identity tier.

Outcomes

More actively managed agents under one organisation.
A single capacity model instead of seven family-specific meters.
Clear separation between identity, assurance and operating scale.

Inside

What is included, and how it works.

What is included

Capacity applied to the organisation's actively managed ECZ-ID estate.
A clear used-versus-available capacity view in your ECZ-ID console.
Compatibility with all seven free Passport families.
A TrustOps path for adding capacity when required.

How it works

Issue FREE Passports for the agents you need to identify.
Use the included baseline capacity first.
Add AEC when the actively managed estate grows beyond that baseline.
The extra capacity changes scale only; it never changes verification or assurance.

The model

How AEC is counted for agents.

One AEC is one actively managed production entity with live bindings and current state. For Agent, that is an agent you actively manage in production, with live bindings and current state.

What counts

One logical agent you actively manage in production is one entity. Bindings, versions, replicas, endpoints and deployments never consume AEC and never become a second Passport.

One pool

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. Individual IoT device instances are counted separately, in IoT Fleet Capacity.

At the limit

At the limit your identities and everything you already manage keep working. Only new actively managed entities wait for room. Your ECZ-ID does not change.

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.

A free Passport exists and resolves whether or not you use any AEC. Public Resolver reads and public machine-readable records are never metered, never authenticated and never counted against any allowance.

Boundaries

What the FREE Passport already gives you, and what this never does.

Already included free

A Passport exists and resolves whether or not you use any AEC, and an included baseline comes first. TrustOps shows how much your organisation holds.

£0 · No card required · Permanent, not a trial.

What it never does

AEC is capacity, not verification, certification or trust status.
A Passport remains free whether or not the agent is inside paid operating capacity.
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.

Monitor state
PulseGuard
PulseGuard evaluates current observable state and helps an operator see which ECZ-ID entities need attention, without turning an observation into a safety or certification claim.
Boundary: PulseGuard reports observed state; it is not a safety verdict or certification.
See details Open in TrustOps(opens in a new tab — trustops.ecocitizenz.com)
Evidence/history
LedgerCore
LedgerCore is the evidence layer for ECZ-ID: lifecycle events, eligible receipts and tamper-evident anchors that help a reviewer understand what was recorded and when.
Boundary: An anchor shows that a recorded item has not changed since anchoring; it does not make the statement true.
See details Open in TrustOps(opens in a new tab — trustops.ecocitizenz.com)
Relationships
ECZ-ID Graph Intelligence
Graph Intelligence helps an organisation understand how ECZ-ID entities, operators, bindings and dependencies connect, while keeping public-safe graph facts separate from private operating context.
Boundary: A Graph relationship is a published relationship, not an endorsement and not a permission.
See details Open in TrustOps(opens in a new tab — trustops.ecocitizenz.com)
Changes
ECZ-ID Watch
Watch turns a one-time Resolver check into continuing awareness. Free Watch supports a small local follow list; paid Watch adds cloud monitoring, verified-recipient delivery, retained history, Graph Watch and bounded machine access.
Boundary: A Watch notification is a change signal, not certification, approval or a safety assessment.
See details Open in TrustOps(opens in a new tab — trustops.ecocitizenz.com)

Every Agent product

Start with the identity. Add AEC — Active Entity Capacity when it earns its place.