Skip to content
ECZ-IDDevelopers

ECZ-ID — Reciprocal Trust Infrastructure for the Machine Economy

ECZ-ID Developers

Build reciprocal trust into machine interactions.

  • Identify the actor.
  • Establish authority.
  • Carry Intent.
  • Evaluate before consequence.
  • Record what happened.
  • Re-check the proof.
Get startedExplore conceptsVerify ECZ-ID (opens in a new tab)
Live recordRead 2026-10-10 · no key, no account
$ curl -s https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json
{
  "ecz_id": "ECZ-GB-RBS1NW",
  "resolver_v2": {
    "state": {
      "lifecycle_state": "ACTIVE",
      "parent_tier": "VERIFIED",
      "reliance_level": "PARENT_IDENTITY_ONLY"
    },
    "binding": { "state": "NO_PUBLIC_PROOF" },
    "reliance": { "reverify_before_reliance": true }
  }
}

Abridged. The record names what it supports and what it refuses to let you infer. Five-minute introduction

01 · The Accountability Chain

Ten questions every consequential machine action should answer.

Each link has a defined place in ECZ-ID, a system that holds its truth, and a production status. Passing one never stands in for another.

  1. 01IdentityWho or what is acting?Live · public
  2. 02AuthorityWho or what authorised it?Live · signed in
  3. 03DelegationWhat authority was delegated?Live · signed in
  4. 04IntentWhat does it intend to do?Live · signed in
  5. 05Current stateWhat state and policy apply now?Live · public
  6. 06DecisionShould the action proceed?Release-gated
  7. 07ActionWhat action was taken?Your system
  8. 08ReceiptWhat receipt exists?No public retrieval
  9. 09EvidenceWhat evidence supports it?No public retrieval
  10. 10Re-verifyHow can it be re-verified?Live · public

Know who acts.Know why they may act.Know what they intend.Decide before consequence.Prove what happened.

02 · Seven machine surfaces

A free Passport for every kind of machine you operate.

Agent, MCP, Plugin, API, IoT, SDK, and Service & Workload. One subject, one ECZ-ID, under your organisation’s Business Passport. No payment, one sign-in. Each has a guided flow through the whole chain and a quickstart for its identity.

Facts from the TrustOps families contract. Availability is read live and never stored by this site.

03 · Build the flow

Resolve, establish authority, carry Intent, evaluate, act, record, re-check.

The integration follows the chain. Each step is labelled with what is live today, so you build against what exists.

  1. 01ResolveRead the actor’s public record live.Live · public
  2. 02Establish authorityKnow who authorised the work, and with what bounds.Live · signed in
  3. 03Carry IntentReference the authorised Intent with the request.Live · signed in
  4. 04EvaluateAsk for a decision before the consequence.Release-gated
  5. 05ActYour system acts, holds or blocks.Your system
  6. 06ReceiptThe recording system issues a Receipt.No public retrieval
  7. 07Re-checkAnyone can re-resolve the proof later.Live · public
Choose a guided flowFirst integration, end to end

04 · ECZ-ID Intent and IntentControl

Permission is not Intent.

A token with payments:write can pay anyone, any amount, at any time. An Intent says what this agent is authorised to do, within what bounds, for how long, so a proposed action can be checked before it has a consequence.

ECZ-ID Intent: the authorised envelope

Live · signed in
jsonIllustrative, abridged. Field names from the Core contract.
{
  "objective_summary": "Pay approved supplier invoices",
  "actor": { "ecz_id": "ECZ-GB-EXAMPL::AGENT_PASSPORT-AB12CD" },
  "constraints": {
    "actions":   { "permitted": ["invoice:pay"], "excluded": ["invoice:pay_new_payee"] },
    "financial": { "currency": "GBP", "max_per_action": 500, "max_total": 5000 },
    "approval":  { "above_amount": 250 },
    "data_classes_denied": ["card_data"]
  },
  "window": { "not_before": "2026-10-12T00:00:00Z", "expires_at": "2026-10-19T00:00:00Z" }
}

IntentControl: decide before consequence

Release-gated
Proposed actionAgainst the IntentDecision
Pay £180 on an approved invoice, in GBPInside every boundAllow: the configured checks passed, nothing more
Pay £420 on an approved invoiceAbove the £250 approval thresholdReview: held until an owner or admin approves
Pay £720 to a new payeeExcluded action; above the £500 capDeny: the action never runs
Any payment once the Intent has expiredOutside the window; no Intent in forceDeny

IntentControl is documented ahead of release. Commercially: coming soon in TrustOps and not yet on sale. Signed in: not yet available. Public decision API: none. An allow never means the action happened, succeeded or was safe. Enforced is claimed only where an inline enforcement point demonstrably mediated the action.

IntentIntentControlEnforcement modes

05 · Receipts

Prove what happened, and only what happened.

A Receipt proves what the recording system recorded. It does not automatically prove that every underlying real-world assertion was true.

06 · Trust boundaries

Each surface does one job.

This site explains and integrates. It issues nothing and proves nothing. Purchases happen in TrustOps.

  • ECZ-ID Core

    determines canonical state

    Canonical identity, lifecycle, binding, Intent, decision and Receipt state.

  • TrustOps (opens in a new tab)

    acquires

    Acquisition, payment, entitlement and activation.

  • Dashboard

    operates

    Authenticated operation inside TrustOps: Passports and Intents today; bindings and policy as each is released.

  • Resolver (opens in a new tab)

    exposes public proof

    Public, read-only proof of published ECZ-ID state. Not a verdict on anything it does not publish.

  • Developer Gateway

    explains and integrates

    Concepts, contracts, schemas, examples and interoperability. This site. It issues nothing and proves nothing.

07 · Developer Trust

See what an MCP server or agent declares before you let it act.

Free, local-first VS Code extensions, Community editions free forever with no account. No source, prompts, tool arguments, tool results or secret values are uploaded, and there is no telemetry.

Developer TrustFree Preflight checklist (PDF)

MCP Trust

See what your MCP servers expose. Know what changed. Control the ones that matter.

Community: MCP X-Ray, Trust Delta. Pro: Trust Epochs, Advanced Tool X-Ray, Local Trust Gate.

Agent Trust

Know what your AI agents can reach. See how their authority changes before they act.

Community: Agent X-Ray, change detection. Pro: Authority Graph, action chains, Authority Epochs.

Developer Trust Pro

Both sides of the agent ↔ MCP connection. One licence for both extensions.

Coverage: OBSERVED — configuration is inspected on this machine and ECZ-ID is not on the request path; no call is intercepted, allowed or blocked. Community never mediates. MCP Trust Pro can optionally run a Local Trust Gate you start yourself; coverage reads ENFORCED only for traffic routed through that gate, only while it is running and its live local mediation proof holds, and drops back to OBSERVED the moment it stops. Local inspection is not public proof: the Resolver is the public proof surface.

08 · Proof

Don’t take our word for it. Resolve us.

This site is operated by EcoCitizenz Ltd under the ECZ-ID Business Passport ECZ-GB-RBS1NW. Its current state is whatever the Resolver says now, not what this page says.

ECZ-ID Business Passport badge for EcoCitizenz Ltd, ECZ-GB-RBS1NWVerify EcoCitizenz live ↗