ECZ-ID Agent Credential™
Resolver-verifiable child passport in the Digital & Operational family.
Who it is for: Businesses, platforms, and operators in APIs, AI, Data & Software, IoT & Connected Systems that need a resolver-verifiable identity for this object before counterparties, regulators, or buyers will rely on it.
In plain terms
The ECZ-ID Agent Credential™ is the resolver-verifiable identity for an autonomous agent, AI tool, MCP server, or API-using workflow.
The real-world problem
What this removes
AI agents and autonomous tools are starting to call APIs, trigger workflows, and represent businesses, but most cannot prove who controls them, what authority they hold, or whether their current state can be relied on.
Why this causes delay or loss
Counterparties, marketplaces, and platforms reject or hold integrations when an agent has no resolver-verifiable operator linkage, declared authority, or current-state signal.
Ambiguity removed
Removes ambiguity about which business is accountable for the agent and what authority the agent has been granted.
What it binds / includes
Scope of accountability
Binds an agent to its parent operator passport, declared authority and scope, and the dependencies it relies on (APIs, AI models, datasets, software supply chain).
Parent requirement: Requires an active ECZ-ID Business Passport™ (Verified or Assured) to activate.
Detailed inclusions are confirmed in TrustOps. Developer Gateway documents the model only.
Typical buyers / operators
- Agent builders
- AI developers
- MCP server operators
- Autonomous-workflow operators
Pre-mandate value
Lets a counterparty resolve the operator behind the agent before allowing it to act, even before any regulator mandates AI agent identity.
Stack contributions
What PulseGuard™, LedgerCore™, and Resolver contribute
PulseGuard™
PulseGuard™ contributes present-state monitoring such as liveness, suspension or revocation state, and posture changes where supported by the activated agent credential. It is not behavioural monitoring of prompts, source code, or user data.
LedgerCore™
LedgerCore™ records decisive agent lifecycle events where supported, such as issuance, activation, authority changes, suspension, revocation, and receipt references.
Resolver
Resolver shows current operator linkage, declared authority and scope, attached dependency passports, and current state of the agent credential.
Badge / mandate plate
Where this product has an ECZ-ID badge or mandate plate, the badge is an embeddable visual pointer to the Resolver state. The badge is not proof by itself; the Resolver check is the proof surface.
Insurability Readiness™ impact
An active Agent Credential plus a Verified or Assured parent and supporting dependency passports contribute to derived Insurability Readiness™ where supported.
Customer questions
What buyers and counterparties ask
Who controls the agent?
Bind to a parent ECZ-ID Business Passport™ so counterparties resolve the accountable operator.
What is it allowed to do?
Declared authority and scope are recorded on the credential and visible in Resolver.
Can it be relied on right now?
Resolver shows current state. Counterparties should check Resolver before relying on the agent.
Boundary of claim
What this product does not claim
- · Does not certify the agent always reasons correctly.
- · Does not claim the underlying model cannot hallucinate.
- · Does not monitor prompts, source code, or user data.
- · Does not constitute AI safety certification.
Guided flow
Six steps from need to resolved state
- 01
Understand the need
Decide what commercial friction you are trying to remove. Developer Gateway documents the model. It does not determine eligibility, issue credentials, or create entitlements.
- 02
Confirm parent requirement
Every child passport, package, and add-on attaches to an active ECZ-ID Business Passport™. Verified or Assured may be required (per TrustOps).
- 03
Review what this product does
Check what is bound, what is included, and what it does not claim. No safety, certification, approval, or partnership claim is made on this page.
- 04
Continue to TrustOps
Acquisition, activation, payment, and lifecycle happen in TrustOps. Developer Gateway only routes the handoff.
- 05
Return to Developer Gateway
After TrustOps, return here for next-step docs and related guidance. Developer Gateway still does not prove current state.
- 06
Check current proof in Resolver
Current proof must be checked in the public Resolver. Copied metadata, screenshots, or website claims do not replace Resolver.
TrustOps midpoint
Acquisition, setup, payment, and lifecycle happen in TrustOps
Developer Gateway only routes. It does not host checkout, change canonical state, issue credentials, or replace Resolver proof. TrustOps owns the operational state for this product.
Browse child passports in TrustOps ↗TrustOps URL: https://trustops.ecocitizenz.com/start
Return path
Come back here for next-step docs
After TrustOps completes acquisition or activation, return to Developer Gateway for related docs and guided next steps. Developer Gateway still does not prove current state. Current proof remains in Resolver.
Resolver proof
Current proof must be checked in Resolver
Copied metadata, screenshots, badges on third-party websites, or any claim made on Developer Gateway do not replace Resolver. The Resolver is the sole public proof surface for ECZ-ID.
Open Resolver ↗Resolver URL: https://resolver.ecocitizenz.org
Recommendation
Find your recommended starting point
Enter your website URL. TrustOps will use it to recommend a starting point. Developer Gateway sends the URL only; TrustOps handles the recommendation, setup, payment, and lifecycle controls.
Developer Gateway does not host checkout, change canonical state, issue credentials, or replace Resolver proof. Current proof must be checked in Resolver.