Counterparty · ECZ-ID SDK
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.
People and software meet your SDK or library on a digital surface and have no quick way to reach the organisation behind it. Every counterparty re-does the same lookup.
Built for
- Businesses selling through digital channels where counterparties need to verify who stands behind the service.
- API and platform operators that want a reusable machine-readable counterparty layer.
- Procurement, trade and automated workflows where repeated identity checking creates friction.
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
- The digital surface a counterparty sees
- Binding
- That surface, bound to the ECZ-ID of your SDK or library
- Operator
- The operating organisation and its Parent tier
- Proof
- Resolver page and machine-readable JSON
- Re-check
- recheck_before_reliance: true
Illustrative structure. 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 Passport already has — the identity, bindings, Resolver proof and badge — and organises it around the surfaces your counterparties actually encounter.
Use cases
- Letting a developer go from a package page to the organisation behind it in one click.
- Giving automated procurement a machine-readable record of an SDK supplier.
- Reducing repeated publisher questionnaires for the same library.
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.
- Badge, QR and share link on the surfaces counterparties already use.
- Resolver JSON for procurement and trade software.
- Parent VERIFIED (or ASSURED): the DCI Pack requires it, and TrustOps adds it to the basket.
- Is DCI a trust score?
- No. It makes identity and evidence easier to find and re-check. The decision stays with the counterparty.
- Do I need a paid tier to start?
- For the DCI Pack, yes. The free SDK 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
- Software supply chainSBOM & software-composition evidenceTurn software composition and provenance into evidence a buyer can actually review.Read more
- SDK specialist kitECZ-ID SDK Release Provenance & Customer Assurance KitMake SDK release provenance and dependency evidence easier for customers to review.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 SDK Passport stays free. DCI — Digital Counterparty Infrastructure sits above it; TrustOps shows its current state.