Counterparty · ECZ-ID API
DCI — Digital Counterparty Infrastructure
Make a digital counterparty easier for people and machines 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.
- Type
- Solution
- Price
- Not restated on this site; TrustOps publishes the current price and availability
- Acquired and paid in
- TrustOps
- Operated in · proved by
- Dashboard · Resolver
The problem
Why it matters.
Every integration is a business dependency. A customer, a partner or an agent meets your API at a base URL and has no quick way to reach the organisation behind it, so each counterparty re-does the same lookup, the same questionnaire and the same approval.
Built for
- API providers selling to businesses whose procurement and security teams must identify every supplier they integrate.
- Platform and partner programmes where many counterparties depend on the same APIs.
- APIs increasingly called by agents and automated procurement, which need a machine-readable counterparty record.
What changes
- A clearer path from a digital surface to the organisation behind it.
- Reusable evidence that can be checked by people and software.
- Lower lookup friction in counterparty and procurement workflows.
What you receive
Concrete deliverables, not a vague trust score.
- Counterparty-oriented ECZ-ID identity and evidence presentation.
- Public Resolver proof and machine-readable records.
- Support for bindings from real digital surfaces back to the same identity.
- A TrustOps path to strengthen assurance and evidence when required.
- Surface
- https://api.example.com — what the counterparty sees
- Binding
- The API's OpenAPI description, bound through OpenAPI info.x-ecz-id
- Operator
- Example Payments Ltd, with its Business Passport tier
- Proof
- Resolver page and machine-readable JSON
- Re-check
- recheck_before_reliance: true
Illustrative structure on a reserved example domain. The live proof is always the Resolver record.
How it works
A short path from need to something usable.
Identify the digital surface a counterparty encounters.
Bind it to the relevant ECZ-ID identity and operator context.
Publish a direct proof path for people and machines.
Keep the record current as the business or digital surface changes.
How it relates to your Passport
DCI builds on what every free API Passport already has — one identity, bindings, Resolver proof and the badge — and organises it around the surfaces your counterparties actually meet. The DCI Pack itself requires a Verified (or Assured) Business Passport tier for the organisation behind it, which TrustOps adds to the basket.
Use cases
- A customer's reviewer going from your base URL to your organisation's record in one click.
- An agent resolving the operator of an API before it plans a call on a user's behalf.
- A partner programme giving every integrating partner the same counterparty record.
- Reducing repeated identity sections in supplier questionnaires for the same API.
Tiers and price
Price and availability
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. This site does not restate this product's price; TrustOps publishes its current tiers, price and availability, and shows them before anything is bought.
How it is arranged
TrustOps acquires
TrustOps publishes the tiers and holds payment and entitlement whenever it is offered.
Dashboard operates
Once you hold it, it appears in your Dashboard, where you operate it.
Resolver proves
Public facts stay on the Resolver; holding it never changes what a record proves.
Privacy, security and evidence
What is collected, published and kept.
- Only what you consent to publish becomes public.
- DCI is identity and evidence infrastructure, not a counterparty risk score.
- A resolvable identity does not mean a counterparty has been approved.
Boundaries
The claims stop here.
- DCI is infrastructure for identity and evidence; it is not a counterparty risk score.
- A resolvable identity does not mean a counterparty has been approved or is safe to transact with.
Integrations and questions
Works with what you already run.
- OpenAPI info.x-ecz-id in the description you host.
- Badge, QR and share link on your developer portal and API reference.
- Resolver JSON for procurement tools and agents.
- A Verified (or Assured) Business Passport: the DCI Pack requires it, and TrustOps adds it to the basket.
- Is DCI a trust score for my API?
- No. It makes identity and evidence easier to find and re-check. The decision stays with the counterparty.
- Does DCI replace our customer onboarding or KYB?
- No. It gives counterparties a reusable record to start from. Their own checks and contracts stay theirs.
- Do I need a paid tier to start?
- For the DCI Pack, yes. The free API Passport provides the identity, bindings and public proof DCI builds on, and the DCI Pack itself requires a Verified (or Assured) Business Passport tier, which TrustOps adds to the basket.
Related
- Regulated financeDORA ICT-vendor evidencePrepare reusable ICT-vendor evidence for customers operating under DORA.Read more
- API specialist kitECZ-ID API Enterprise Security Review & Customer Assurance KitTurn API ownership, control and security evidence into an enterprise-review pack.Read more
- Relationships · DependenciesECZ-ID Graph IntelligenceSee the relationships that make a machine-economy identity meaningful.Read more
Keep the identity free. Everything above it is optional.
Your API Passport stays free. DCI — Digital Counterparty Infrastructure sits above it; TrustOps shows its current state.