Workflow bundle · ECZ-ID API
ECZ-ID Developer Distribution Assurance Bundle
Connect one organisation's identity, packages and developer distribution evidence.
A workflow bundle for teams shipping SDKs, APIs and the packages behind them across multiple channels.
- Type
- Bundle
- 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.
Developers meet your API through a portal, an OpenAPI description, client SDKs on several registries and sometimes an MCP server. Buyers want one distribution story; you maintain several, and none of them names the same operator the same way.
Built for
- Developer-tool vendors
- SDK and API providers
- Multi-registry distribution
What changes
- One organisation behind every channel, clearly named
- Reusable distribution evidence
- Less channel-by-channel duplication
What you receive
Concrete deliverables, not a vague trust score.
- Relevant specialist kits
- Organisation and release context
- Developer-distribution review artefacts
- Surfaces
- Every channel the product is distributed through
- Identities
- Each surface's own ECZ-ID
- Organisation
- The organisation behind all of them
- Evidence
- Release and distribution evidence, organised
- Boundary
- No channel approval or security certification implied
Illustrative structure.
How it works
A short path from need to something usable.
Map the distribution surfaces.
Connect them to persistent identities.
Complete the evidence products.
Publish the review pack.
How it relates to your Passport
The bundle connects the API and SDK identities your developer product already has, each still its own free Passport, under one operator.
Use cases
- An API shipped with client SDKs on npm, PyPI and Maven, reviewed as one distribution.
- A developer platform shipping an API and an SDK together.
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.
- Distribution evidence does not imply approval by any distribution channel, or security certification.
- Each identity stays distinct.
Boundaries
The claims stop here.
- Distribution evidence does not imply approval by any distribution channel, or security certification.
Integrations and questions
Works with what you already run.
- SDK and API Passports.
- Developer Gateway for integration.
- Do I need every family's Passport?
- Only for the surfaces you actually distribute. Each is free.
Related
- API specialist kitECZ-ID API Enterprise Security Review & Customer Assurance KitTurn API ownership, control and security evidence into an enterprise-review pack.Read more
- Portfolio suiteECZ-ID Digital Entity Trust SuiteBring the specialist assurance products into one portfolio-level programme.Read more
- Software supply chainSBOM & software-composition evidenceTurn software composition and provenance into evidence a buyer can actually review.Read more
Keep the identity free. Everything above it is optional.
Your API Passport stays free. ECZ-ID Developer Distribution Assurance Bundle sits above it; TrustOps shows its current state.