Skip to content

Business solution · most relevant for Agent

DCI — Digital Counterparty Infrastructure

Make the agent a counterparty meets easy to identify, inspect and re-check.

DCI combines identity, public proof and reusable evidence around the digital surface a counterparty actually encounters — such as a website, API, portal or machine service.

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.

An agent is increasingly the digital surface a counterparty meets first: it calls their API, talks to their agent, files into their workflow or turns up in their logs. DCI gives that counterparty one path from the agent in front of them to the organisation behind it, and to the evidence you publish — for people and for software, without a questionnaire and without asking you.

The questions it helps answer

  • Who stands behind the agent that just contacted us?
  • Can our systems resolve that answer without a human in the loop?
  • What evidence has the operator published, and when was it last current?

Fit

Who it is for, and what changes.

Best for

  • Businesses whose agents act on their behalf in other organisations' systems.
  • API and platform operators that want a reusable, machine-readable counterparty layer.
  • Procurement, trade and automated workflows where repeated identity checking creates friction.

Outcomes

  • A clearer path from an agent to the organisation behind it.
  • Reusable evidence that people and software can check.
  • Lower lookup friction in counterparty and procurement workflows.

Inside

What is included, and how it works.

What is included

  • Counterparty-oriented ECZ-ID identity and evidence presentation.
  • Public Resolver proof and machine-readable records.
  • Bindings from the real surfaces your agent appears on back to the same identity.
  • A TrustOps path to strengthen assurance and evidence when required.

How it works

  1. Identify the surfaces a counterparty encounters — the agent, and the APIs and services it acts through.
  2. Bind them to the agent's ECZ-ID and its operator.
  3. Publish a direct proof path for people and machines.
  4. Keep the record current as the business and its agents change.

Why DCI leads for Agent

The counterparty's path: from the agent in front of them to the organisation behind it.

An agent that acts on your behalf is the part of your business another organisation actually meets. DCI makes that meeting checkable.
  1. The agent arrives

    It calls an API, messages another agent or files into a workflow, carrying its ECZ-ID where the counterparty will see it.

  2. The counterparty resolves it

    A person or a system opens the public record — no account, no key, no request to you.

  3. They see who stands behind it

    The operator on the record, the bindings it declared, and the evidence you chose to publish.

  4. Their policy decides

    ECZ-ID tells you what is published and by whom. What that is worth in your context is your policy's decision, not ours.

Boundaries

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

Already included free

A FREE Agent Passport already gives the agent a public Resolver record, machine JSON, a live badge and basic bindings — the identity foundation DCI builds on.

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

What it never does

  • DCI is identity and evidence infrastructure; it is not a counterparty risk score or approval.
  • A resolvable identity does not mean a counterparty has been approved or is safe to transact with.
  • 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.

Related

Read next.

  • Assurance

    ECZ-ID Agent Authority & Enterprise Assurance Kit

    A practical evidence product for teams that need to explain who operates an agent, what authority it has been delegated, where that delegation comes from and what a reviewer can independently re-check — without rebuilding the answer for every customer review.

    Boundary: The Kit organises evidence; it does not certify the agent as safe or compliant.

  • 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.

  • 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.

  • Regulated finance

    DORA ICT-vendor evidence

    The DORA solution helps an ICT provider organise identity, service, resilience and supporting evidence into a reusable review pack for financial-sector customers and their procurement or risk workflows.

    Boundary: ECZ-ID supports evidence preparation and review; it does not certify DORA compliance.

Every Agent product

Start with the identity. Add DCI — Digital Counterparty Infrastructure when it earns its place.

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