Disclosure tiers
Which fields a verification response carries, and what an API key changes.
Every response states which tier produced it, in disclosureTier. Read that field rather than
inferring the tier from whether you sent a key.
disclosureTier | Who gets it | What it carries |
|---|---|---|
public | Anyone, no credential required | The verdict, all four checks, the full public-ledger anchor proof, revocation state and reason, live signer standing, and the signer's opt-in public hint. Enough to decide whether to trust the document. |
organisation | A valid API key on a validated organisation | Everything above, plus a durable verificationId, the environment the key belongs to, your own reference echoed back, the reconciliation log, and higher rate limits. |
Organisation records
When an organisation authenticated a document, the organisation tier also names that
organisation, as long as the organisation is still validated and the record's standing can be
determined. If either is not the case, no name is shown. At the public tier the match says an organisation signed, without naming it, but
the anchor's ledger address is public at both tiers and points to the organisation.
What a credential does not change
The verdict. Both tiers run the same four checks against the same records and return the same answer. A credential buys accountability on your side and a higher tier of service — it does not buy a different result.
Who signed something. Signer identity is disclosed because the signer opted in, not because the verifier authenticated. A signer's public name or role is whatever they chose to publish, at either tier.
While your organisation is being validated
Your keys work, and are served at the public tier. Nothing is refused and no key needs
replacing — you keep the same key through validation, and it moves to organisation automatically
once validation completes.
Until then:
verificationId,environmentandreferenceare absent from responses. Code that dereferences them unconditionally will break.- The two read operations — listing verifications and reading one back — return
403. The reconciliation log is what theorganisationtier adds, and apublic-tier response carries noverificationIdto read back. - Anonymous rate limits apply. See Errors.
Your verifications are recorded throughout. The log is populated from the moment you started, not from the moment you were validated.
Fields by tier
The verdict and match details are the same at both tiers, apart from the organisation's name on an organisation-signed match (see above). These three response fields also differ:
| Field | public | organisation |
|---|---|---|
verificationId | Absent | Present |
environment | Absent | Present |
reference | Absent | Present when you sent one |
Public ledger visibility
Disclosure tiers control the API response, not the public ledger. The ledger entry is public at every tier and stays public. It holds the document's fingerprint, identifiers and a timestamp, with no names and no document content. An organisation's ledger address points to the organisation, as described above.