Included free · Public proof · ECZ-ID SDK

Resolver

Public, read-only proof of identity for your SDK or library, for anyone who asks.

The Resolver publishes the current record behind an ECZ-ID — who operates the SDK or library, what is bound to it, its current state and the evidence that exists — to people and software alike, with no account and no key.

Get a FREE SDK Passport Verify an ECZ-ID All 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.

Your SDK or library is judged by people who cannot see inside your organisation. Without a public record they either take its name on trust or send you a questionnaire.

Built for

Anyone deciding whether to use, approve or integrate your SDK or library.
Procurement and security reviewers who need a record, not a screenshot.
Software that needs to resolve an identity before acting.

What changes

A single public place where the identity can be checked.
Fewer identity questions answered by hand.
A record that says when it was read and how to re-check it.

What you receive

Concrete deliverables, not a vague trust score.

A public Resolver page for every published Passport.
The same record as machine-readable JSON.
Current state, operator, bindings and evidence presence.
For each verified binding, its proof method, when it was last verified and when a re-check is due.
The guard fields is_proof: false and recheck_before_reliance: true.

A Resolver record

ECZ-ID: ECZ-XX-XXXXXX::SDK_PASSPORT-XXXXXX
Operator: Your organisation, with its Parent tier
State: Current lifecycle state, as last read
Bindings: Public places where the SDK or library appears, each declared or verified
Last verified: YYYY-MM-DD, for each verified binding
Re-check due: YYYY-MM-DD
Guards: is_proof: false · recheck_before_reliance: true

Illustrative structure with placeholder values. The live record is always the Resolver's. Re-check before reliance.

How it works

A short path from need to something usable.

Your Passport is issued in TrustOps and written by ECZ-ID Core.
You consent to publication; nothing is public before that.
The Resolver projects the current record, read-only.
Anyone resolves it — by page, JSON, badge or QR — and re-checks before relying on it.

How it relates to your Passport

Core writes the canonical record; the Resolver projects it. TrustOps and the Dashboard change what you hold and operate; only Core changes what the Resolver shows.

Use cases

A platform team checking who publishes an SDK before adding it to an approved-dependency list.
A dependency-review step resolving the publisher record behind a package it is about to pull in.
A developer clicking the badge in a README to reach the current publisher record.

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

TrustOps acquires
Take the free Passport in TrustOps; your organisation's ECZ-ID Business Passport — Declared — FREE is reused or created.
Dashboard operates
Operate it in the Dashboard: publish, bind and copy your proof links.
Resolver proves
Anyone resolves the current record on the Resolver.

Privacy, security and evidence

What is collected, published and kept.

Publication requires your explicit consent, and you can withdraw it.
Only public-safe fields are projected.
Absence is neutral: no public record is not a finding.

Boundaries

The claims stop here.

The Resolver is public, read-only proof of what is currently declared and verified, with the time it was read. A record is not a verdict — is_proof is false and recheck_before_reliance is true. Re-check before reliance.
The Resolver is read-only. It never edits, issues or approves anything.
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.

Machine-readable JSON with no authentication in front of it.
Badge, QR and share links that land on the record.
The Developer Gateway, for resolving from your own code.

Does a Resolver record prove my claims?: No. It publishes what is currently declared and verified, and what evidence exists, with the time it was read. A record is not a verdict. Re-check before reliance.
Is it really free?: Yes. Every free SDK Passport gets a public Resolver record.
Can I take a record down?: Publication is your decision, and you can withdraw it.

Start with a free SDK Passport.

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

Get a FREE SDK Passport Verify an ECZ-ID