Skip to content
ECZ-IDSDK
Free Passport: Get a FREE SDK Passport

Included free · For software · ECZ-ID SDK

Machine-readable identity

The same record, as JSON any program can read.

Every published SDK Passport has a machine-readable record at a stable URL. Agents, procurement tools and CI pipelines can resolve it without an account or an API key.

Get a FREE SDK PassportVerify an ECZ-IDAll SDK products
Type
Included free
Price
£0 — included with every free Passport
Acquired and paid in
TrustOps
Operated in · proved by
Dashboard · Resolver

The problem

Why it matters.

Identity pages built for people are hard for software to use, so automated decisions fall back to scraping or skip the check entirely.

Built for

  • Agents and tools that must identify what they call.
  • Procurement and vendor-risk software.
  • CI and release pipelines that check what they ship.

What changes

  • Automated identity checks without a bespoke integration.
  • The same facts for people and machines.
  • Guard fields that tell software not to over-read the record.

What you receive

Concrete deliverables, not a vague trust score.

  • A stable JSON record for every published Passport.
  • No authentication in front of public records.
  • The same binding facts as the page, including when each verified binding was last verified and when a re-check is due.
  • The guard fields is_proof and recheck_before_reliance.
Fields a program reads
ecz_id
ECZ-XX-XXXXXX::SDK_PASSPORT-XXXXXX
state
The current lifecycle state
operator
The organisation on the record
is_proof
false
recheck_before_reliance
true

Illustrative fields with placeholder values. The Developer Gateway documents the schema.

How it works

A short path from need to something usable.

  1. Publish your Passport.

  2. Resolve the ECZ-ID at its machine URL.

  3. Read state, operator and bindings from the JSON.

  4. Re-check before reliance: resolve it again before each decision that relies on it.

How it relates to your Passport

The machine record is the Resolver's JSON projection of the record Core writes. The Developer Gateway documents it; this site only explains it.

Use cases

  • A release job resolving the publisher record of each first-party SDK before a version is tagged.
  • A dependency-review tool reading the operator and bindings of a package it is evaluating.
  • An agent or build tool checking which organisation stands behind a library it has been asked to use.

Price

Included free, with every Passport.

£0. It is part of the free SDK Passport — permanent, not a trial, and no card is required.

After you take it

  1. TrustOps acquires

    Take the free Passport in TrustOps; your organisation's ECZ-ID Business Passport — Declared — FREE is reused or created.

  2. Dashboard operates

    Operate it in the Dashboard: publish, bind and copy your proof links.

  3. Resolver proves

    Anyone resolves the current record on the Resolver.

Privacy, security and evidence

What is collected, published and kept.

  • Only published, public-safe fields appear.
  • Every response is a reading at a time, and says so.

Boundaries

The claims stop here.

  • The JSON is the same projection as the page — it is not a stronger claim.
  • is_proof is false. Software must treat the record as current evidence, not a verdict.
  • A binding is verified as of its Last verified time, and the record shows its Freshness. ECZ-ID does not renew a bound binding: once its proof method's freshness window has passed, the result is history and a new binding is the fresh proof. Re-check before reliance.

Integrations and questions

Works with what you already run.

  • The Developer Gateway for schemas and client guidance.
  • The ECZ-ID Trust MCP for agents that resolve identities.
Do I need an API key?
Not for public records. Anyone can resolve them.
Where is the schema documented?
On the Developer Gateway, which documents and supports integration.

Related

Start with a free SDK Passport.

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

Get a FREE SDK PassportVerify an ECZ-ID