Trust infrastructure for the machine economy.
ECZ-ID is resolver-verifiable identity for AI agents, vendors, enterprise platforms, and every digital counterparty operating in serious commercial infrastructure. Start where trust friction is already costing you distribution, approvals, capital access, or counterparty trust.
Start with a parent ECZ-ID Business Passport™, attach the passports, packages, and add-ons your operation needs, then let counterparties verify current state through Resolver.
Resolve the server. Resolve the agent. Re-check before reliance.
ECZ-ID gives developers, platforms, and enterprise teams a resolver-first way to check MCP servers, tools, APIs, packages, and agents before high-risk use.
ECZ-ID separates setup, verification state, and public proof so operators can prepare evidence and relying parties can re-check before they act.
Resolve the Agent Before You Allow It to Act.
ECZ-ID gives autonomous agents, AI tools, MCP servers, API-using workflows, and agent operators a resolver-verifiable identity and accountability layer before they integrate, transact, deploy, or represent a business.
Definition
ECZ-ID Agent Trust is the ECZ-ID layer that lets a business make an AI agent, API-using workflow, MCP server, or autonomous tool resolver-verifiable before another system relies on it.
Thesis
An agent should not be trusted because it says what it is. It should be trusted only when its operator, authority, scope, dependencies, and current state can be resolved.
Agents are starting to act
Calling APIs. Triggering workflows. Representing businesses. Moving data. Interacting with platforms. Acting inside operational and commercial systems.
Most still cannot prove
Who controls them. What authority they have. What systems they depend on. Whether their current state can be relied on. Where a counterparty can verify them.
ECZ-ID gives them
Resolver-verifiable identity, accountable operator linkage, declared authority, dependency visibility, current-state visibility, and machine-readable proof.
Four questions a relying party should be able to resolve
Operator. Authority. Dependencies. Current state. Resolver-verifiable, machine-readable, before action.
Proof question
Who controls this agent?
Bind the agent to an ECZ-ID Business Passport™ so counterparties can resolve the accountable operator behind the system.
Proof question
What is it allowed to do?
Declare and verify the agent’s operating role, delegated authority, scope, and current status before relying on its actions.
Proof question
What does it depend on?
Attach API, AI Model, Dataset, Software Supply Chain, and other relevant passports where the agent depends on external systems.
Proof question
Can it be relied on right now?
Use the public Resolver to check current state before integration, deployment, transaction, or acceptance.
Composition
The Agent Trust Stack
Start with the business. Bind the agent. Attach the systems it uses. Resolve the state before action.
ECZ-ID Business Passport™
Parent identity spine for the operator.
ECZ-ID Agent Credential™
Resolver-verifiable credential for the agent.
ECZ-ID API Passport™
For APIs, MCP tools, webhooks, GPT actions, and external systems used by the agent.
ECZ-ID AI Model Passport™
For model-backed agents where model identity and lineage matter.
ECZ-ID Dataset Passport™
For agents dependent on governed, sensitive, licensed, or operationally important data.
ECZ-ID Software Supply Chain Passport™
For deployed agent runtimes, packages, MCP servers, and automation environments.
Public Resolver Proof
Human-readable and machine-readable state verification.
Boundary of Claim
Accountability, Not AI Safety Theatre
ECZ-ID does not claim:
- · that an agent always reasons correctly
- · that a model cannot hallucinate
- · that private prompts, code, or user data are being monitored
- · that ECZ-ID is certifying general AI safety
- · that the website itself verifies or provisions anything
ECZ-ID proves more concrete things:
- · who the agent is connected to
- · what authority has been declared
- · which credentials support its operation
- · whether its current state can be resolved
- · where a relying party can verify that state
Find the blockage costing you the most. Remove it.
Six commercial starting points — agent identity, supplier eligibility, enterprise platform governance, digital counterparty posture, trade finance capital release, and construction dispute defensibility. Choose the one costing you the most and enter the guided flow. ECZ-ID is broader than these six paths: nine domains, 78 catalog entries, and a full machine-economy credential estate. Developer Gateway documents and routes. TrustOps handles setup. Resolver remains the public proof surface.
Agent Identity & Agent Operations
Agent builders · AI developers · Autonomous systems operators · Marketplaces
Platforms deny listings. Marketplaces reject agents at onboarding. Institutional buyers block integrations until identity is proven. Without resolver-verifiable credentials, your agent is blocked from every serious commercial deployment target. ECZ-ID issues the identity credentials any ecosystem needs to accept what you build.
Unlocks:
Resolver-verifiable agent identity and KYA readiness — your agent clears the identity gate and is better positioned for serious ecosystem onboarding, marketplace review, and institutional counterparty checks.
Primary Inventory:
- ·Business Passport
- ·Agent Credential
- ·API Passport
- ·KYA Ready Pack™
- ·+ AI Provenance / Developer Payout / AI Model / Dataset / Software Supply Chain (as relevant)
Vendor Onboarding & Procurement Infrastructure
Suppliers · Vendors · Procurement-constrained businesses · Regulated supply chains
Every procurement approval delay is delayed revenue. Eligibility documentation that buyers cannot independently verify creates stalls, rejections, and compliance-chain failures before the deal starts. ECZ-ID replaces assertion-based documentation with machine-readable, resolver-verifiable supplier credentials that procurement systems evaluate without calling you.
Unlocks:
Resolver-verifiable supplier eligibility — designed for procurement systems and regulated buyers to evaluate without PDF review, spreadsheet exchange, or qualification-chase friction.
Primary Inventory:
- ·Business Passport
- ·KYB Gate Pack
- ·Supplier Eligibility Pack
- ·Cyber Governance Pack
- ·DORA Essentials
- ·SBOM Essentials (as relevant)
Enterprise / Platform Trust Infrastructure
Enterprise teams · Platform operators · Critical infrastructure operators · Regulated sector entities
Capital providers are waiting for governance evidence. Insurers cannot confirm your posture from documents. Institutional partners put high-value engagements on hold pending trust verification that takes months. ECZ-ID makes your platform governance posture resolver-verifiable so capital providers, insurers, and counterparties confirm your status independently — without your submission.
Unlocks:
Resolver-verifiable platform governance posture — capital-access ready, insurer-legible, and independently queryable by institutional counterparties through Resolver without your involvement.
Primary Inventory:
- ·Business Passport
- ·Cyber Governance Pack
- ·Critical Operator Pack
- ·DORA Essentials
- ·Capital Access Overlay
- ·Hold Release Overlay (as relevant)
Digital Counterparty Infrastructure
Digital businesses · API operators · Platform counterparties · Trust-gated commerce participants
Before any human contacts you, automated payment platforms, insurance engines, and counterparty assessment systems have evaluated your website or API — and found nothing verifiable. Unknown digital surfaces are rejected or held. ECZ-ID attaches resolver-verifiable identity to your public digital presence so those systems have something to verify before they decide.
Unlocks:
Public-surface-verified digital counterparty posture — your website or API becomes legible to automated trust systems and counterparty assessment pipelines.
Primary Inventory:
- ·Business Passport
- ·ECZ-ID Digital Counterparty Infrastructure Pack™
Trade Finance Release Pack™
Exporters · Importers · Trade finance desks · Corporate treasury · Trade finance intermediaries
Capital release in trade finance is blocked by ambiguity in product identity, custody transfer, risk policy, and financial authority and funds flow. Trade finance counterparties cannot reach a resolver-verifiable capital-release readiness pathway from documents alone. Trade Finance Release Pack™ collapses that ambiguity into a resolver-verifiable capital-release readiness pathway composed from four resolver-verifiable passports.
Unlocks:
Resolver-verifiable capital-release readiness pathway — composed from Product, Custody Transfer, Risk Policy, and Financial Authority & Funds Flow passports. Verified or Assured parent ECZ-ID tier required. Billed at the same cadence as the parent. £999/mo on Verified · £1,499/mo on Assured.
Primary Inventory:
- ·PRODUCT Passport™
- ·CUSTODY-TRANSFER Passport™
- ·RISK-POLICY Passport™
- ·FINANCIAL-AUTHORITY-FUNDS Passport™
- ·Bundle code: ECZ-BUNDLE-TRADE-FINANCE-RELEASE
Construction Dispute Resolution Pack™
Main contractors · Sub-contractors · Clients & developers · Construction product suppliers · Professional advisers
Construction disputes over liability, timeline, and responsibility are blocked by ambiguity in product identity, custody transfer, risk policy, and identity continuity across project phases. Adjudicators, insurers, and counterparties cannot reach a resolver-verifiable dispute defensibility pathway from documents alone. Construction Dispute Resolution Pack™ collapses that ambiguity into a resolver-verifiable dispute defensibility pathway composed from four resolver-verifiable passports.
Unlocks:
Resolver-verifiable dispute defensibility pathway — composed from Product, Custody Transfer, Risk Policy, and Identity Continuity passports. Verified or Assured parent ECZ-ID tier required. Billed at the same cadence as the parent. £749/mo on Verified · £1,249/mo on Assured.
Primary Inventory:
- ·PRODUCT Passport™
- ·CUSTODY-TRANSFER Passport™
- ·RISK-POLICY Passport™
- ·IDENTITY-CONTINUITY Passport™
- ·Bundle code: ECZ-BUNDLE-CONSTRUCTION-DISPUTE-RESOLUTION
Six commercial starting points. ECZ-ID covers nine credential domains and 78 catalog entries across the full machine economy. Explore the full domain estate →
Independently verifiable evidence for regulated ICT supply and software supply chain.
Part of the wider ECZ-ID credential estate, focused on the two compliance surfaces buyers and regulators ask about most: DORA for ICT vendor evidence and SBOM for software supply chain provenance. Six tiers, plus a combined Enterprise Suite. Each tier is explained here, acquired in TrustOps, and Resolver-checked by counterparties through Resolver. Choose the tier that matches your supervised-entity footprint and release cadence.
DORA-aligned credentials for regulated financial supply
For ICT vendors supplying supervised financial entities. Replace document chase with resolver-queryable evidence supervised entities, regulators, insurers, and capital providers can confirm independently.
DORA-aligned ICT vendor evidence — independently verifiable in Resolver. For ICT suppliers entering DORA scope.
Baseline · Guided flow →
Essentials plus managed evidence refresh workflows, supervised-entity register support, and managed compliance reviews.
Operational · Guided flow →
Managed plus critical third-party oversight readiness, multi-entity ICT register operations, and board / capital disclosure.
Board / Capital · Guided flow →
SBOM credentials for serious software supply
For software suppliers whose buyers, auditors, or regulators need machine-readable SBOM evidence. Replace spreadsheets and PDFs with resolver-queryable software supply chain provenance that stays current with your release cadence.
SBOM-aligned software supply chain evidence — independently verifiable in Resolver. For suppliers entering SBOM scope.
Baseline · Guided flow →
Essentials plus per-release SBOM refresh, vulnerability disclosure cadence, and component drift review support.
Operational · Guided flow →
Managed plus portfolio-wide SBOM operations, critical-infrastructure software evidence record, and board / capital disclosure.
Board / Capital · Guided flow →
DORA + SBOM Enterprise Suite
One coordinated programme covering both DORA Enterprise and SBOM Enterprise — under one resolver entry, with one disclosure pack and one managed lifecycle. For organisations where ICT and software supply chain are both under board, insurer, and capital scrutiny.
This site explains tiers and routes you into TrustOps for acquisition. Acquisition, activation, billing, and lifecycle live in TrustOps. Independent verification lives in Resolver. The site does not host checkout and does not perform verification.
Each solution path has a guided flow and a credentialing checkpoint.
Pick a path, enter its guided flow, and pause at the TrustOps checkpoint to acquire exactly the credentials your situation requires. Agent builders also have kits, archetypes, and a directory with required passport lists.
Starter kits, agent archetypes, custom build path, and a full guided flow with built-in credentialing checkpoint.
Guided flow with resolver-verifiable supplier eligibility. Procurement systems accept without PDF review or qualification-chase.
Platform governance posture made resolver-verifiable. Capital providers, insurers, and institutional counterparties confirm status independently.
Attach resolver-verifiable identity to your public digital presence. Automated trust systems and counterparty pipelines have something to verify before they decide.
Walk through capital-release ambiguity, the composed passports, the Verified/Assured parent requirement, and the TrustOps checkpoint for acquisition.
Walk through construction dispute ambiguity, the composed passports, the Verified/Assured parent requirement, and the TrustOps checkpoint for acquisition.
The same process across every path.
Whether you are credentialing an AI agent, a vendor, an enterprise platform, or a digital business — the ECZ-ID process is identical. Developer Gateway guides discovery and build. TrustOps handles setup. Resolver remains the public proof surface for current state.
Identify Friction
Choose the blockage costing you the most
Enter Guided Flow
Step-by-step path to required credentials
Credential Checkpoint
Pause — activate the right trust objects in TrustOps
Return & Complete
Inject credentials into your build or integration
Verify & Deploy
Resolver-verifiable. Make identity resolver-verifiable to counterparties.
Every Domain. One Identity Layer.
From AI agents to cargo containers, from robotaxis to industrial robots—ECZ-ID provides resolver-verifiable identity across the machine economy.
APIs, AI, Data & Software
Resolver-verifiable identity for AI agents, API endpoints, datasets, models, and software supply chains.
5 entity typesIoT & Connected Systems
Trust infrastructure for connected devices, sensors, gateways, and edge computing systems.
4 entity typesProducts, Custody & Risk
Digital product passports, custody chain verification, and risk policy enforcement.
3 entity typesRobotics & Humanoids
Resolver-verifiable identity for industrial, public-space, domestic, and humanoid robotic systems.
4 entity typesVehicles & Mobility
Trust infrastructure for robotaxis, autonomous vehicles, and haulage fleets.
3 entity typesDrones & Aerial Systems
Resolver-verifiable identity for all drone classes from micro UAVs to large autonomous aerial systems.
4 entity typesTrade, Shipping & Infrastructure
Identity infrastructure for global trade, shipping, intermodal transport, and critical systems.
6 entity typesPlatforms, Marketplaces & Control Overlays
Trust overlays for platforms, marketplaces, and multi-party coordination systems.
3 entity typesPassport Families & Packages
Pre-configured identity passport bundles for common deployment patterns and industry verticals.
Catalog estate · 78 catalog entriesInfrastructure-grade identity across the machine economy.
ECZ-ID operates across nine domains. These domain showcases illustrate the infrastructure depth that sits behind the six starting paths and the wider ECZ-ID credential estate. Access any domain through your guided flow or via the domain pages.
Robotics & Humanoids
From industrial arms to human-form robots in public environments — every autonomous physical system needs resolver-verifiable capability evidence, operator accountability, and insurer-legible safety evidence records. ECZ-ID credentials the full robotics estate through environment-based robot passports.
Platforms, Marketplaces & Control Overlays
Every platform that connects buyers, sellers, agents, or services needs resolver-verifiable participants. ECZ-ID provides the identity infrastructure that makes marketplace participants verifiable and control overlays auditable at scale.
Trade, Shipping & Infrastructure
Cross-border trade, supply chain suppliers, and physical infrastructure operators all need resolver-verifiable identity that procurement systems, customs, and institutional counterparties can evaluate without human intermediation.
APIs, AI, Data & Software
Every AI agent, API endpoint, dataset, and software package operating in serious commercial infrastructure needs a verifiable identity. ECZ-ID’s software domain covers the full digital supply chain — from AI provenance to API passport to software SBOM evidence record.
One Trust Infrastructure Layer. Six Solution Paths.
ECZ-ID removes trust friction across six commercial paths — agent identity, supplier eligibility, enterprise platform governance, digital counterparty posture, trade finance capital release, and construction dispute defensibility. Resolver-verifiable. Standards-aligned. Designed for the machine economy.
Resolver-Verifiable
Every identity claim is verifiable through Resolver. No trust-by-assertion. Any party can verify independently.
Domain-Complete
Nine domains, from AI agents to cargo containers. One consistent identity model across the machine economy.
Infrastructure-Grade
Built for serious deployment. Designed to scale with resolver-verifiable identity, lifecycle state, and machine-readable proof.
Commercially Legible
Agents that are easier to evaluate, verify, onboard, and underwrite where applicable. Designed for commerce, not just technology.
Agent-Native
Designed from day one for autonomous agents that need to prove who they are in every interaction.
Standards-Aligned
Designed to align with EU DPP and relevant ISO-style evidence expectations where applicable, and with emerging machine identity frameworks. Not a certification or guarantee of standards compliance.
Choose a Solution Path and Start Moving
Pick the solution path with the highest current friction and enter the guided flow. TrustOps handles setup. Resolver remains the public proof surface for current state. No acquisition happens on this site.