ECZ-ID Intent: the authorised objective and constraints of what a Passport may do
ECZ-ID Intent defines the authorised objective, constraints and validity of what a Passport may do. An Intent is authorised only by an owner or administrator, and nobody authorises their own request.
In an MSP client estate
Why ECZ-ID Intent matters for a managed estate
Who it is for
The MSP problem it addresses
The client problem it addresses
When to attach it to a client
What the MSP receives
- Authorised Intents for the Passports a plan covers.
What the client receives
- A stated objective, constraints and validity for its machine actors, authorised by its own owner or administrator.
How it fits the recurring Machine Trust service
Options, prices and state
Each option, as TrustOps lists it
Bought in TrustOps per tier (monthly or annual prepaid), sized by covered entities. Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
ECZ-ID Intent
ECZ-ID Intent Essential
Annual prepaid£199 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes covers up to 7 entities.ECZ-ID Intent Pro
Annual prepaid£499 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes covers up to 25 entities.ECZ-ID Intent Business
Annual prepaid£1,490 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes covers up to 100 entities.
States and prices from the TrustOps catalogue snapshot of 2026-10-14; TrustOps shows the current state. Buying a capability changes what you can operate. It never changes what the public record proves, and no paid tier is a verification outcome.
What you get
In TrustOps' own words
ECZ-ID Intent Essential
Defines the authorised objective, constraints and validity of what a Passport may do.
Includes covers up to 7 entities.
How it works
In plain English
- 1An owner or administrator states what a Passport may do, within which constraints, until when.
- 2The Intent is authorised; nobody authorises their own request.
- 3Where an enforcement point mediates the action, it can use the Intent.
Inputs
- The authorised objective, constraints and validity, set by an owner or administrator.
Outputs and evidence
- An authorised Intent for each covered Passport.
With your existing stack
Boundaries
What it does not do
- Payment authorises nothing.
- It does not evaluate a proposed action — that is ECZ-ID Intent Control.
- It is not enforced unless an enforcement point mediates the action.
TrustOps terms for ECZ-ID Intent Essential
- Payment authorises nothing: only an owner or administrator authorises.
- Holding a Passport is never an authorisation.
- A decision is evaluated, not enforced, unless an enforcement point mediates the action.
- Covered and protected places do not use Active Entity Capacity.
- A monthly plan cancels at the end of its period.
- One active plan per service.
What buying it never changes
- the ECZ-ID of any Passport
- the Parent organisation tier
- any Passport assurance (holding a Passport is never an authorisation)
- Active Entity Capacity (covered and protected places never use it)
- any authorisation: payment authorises nothing — only an owner or administrator authorises, and nobody authorises their own request
- any Resolver record, until the owner publishes a proof
Proof and integration
Resolver and Developer Gateway
Resolver relationship
Developer Gateway route
In the MSP journey
What comes before and after
Usually comes before
Usually comes after
Related
Questions
ECZ-ID Intent: questions MSPs ask
How is ECZ-ID Intent different from ECZ-ID Intent Control?
Does holding a Passport authorise anything?
Next step