Skip to content
ECZ-IDAPI

Solutions

The business problem above your API’s identity.

Counterparty lookup, regulated-supplier evidence and software-composition review all start from the same free API Passport. None of them is a certification, a score or an approval.

Solutions for API Passport holders

  • Counterparty

    DCI — Digital Counterparty Infrastructure

    Make a digital counterparty easier for people and machines to identify, inspect and re-check.

    Every integration is a business dependency. DCI makes your API a counterparty customers, partners and agents can identify, inspect and re-check — from the base URL they already have to the organisation that operates it.

    Boundary: DCI is identity and evidence infrastructure, not a counterparty risk score or approval.

    Full page
  • Regulated finance

    DORA ICT-vendor evidence

    Prepare reusable ICT-vendor evidence for customers operating under DORA.

    For banks and insurers your API is an ICT third-party dependency. Prepare reusable supplier evidence for their review.

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

    Full page
  • Where relevant · Software supply chain

    SBOM & software-composition evidence

    Turn software composition and provenance into evidence a buyer can actually review.

    Where a buyer reviews what your API is built from, tie composition and provenance evidence to the API and its SDKs, so they review one enduring product rather than a pile of files.

    Boundary: An SBOM describes composition; it is not a declaration that software is secure.

    Full page

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.