Verify
Receive either an issued credential or a fail-closed eligibility case with explicit blockers.
API reference →DEVELOPER INTEGRATION
One contract from evidence intake to public consequence.
Consume deterministic verification, registry, event, webhook, SDK, and lifecycle contracts without recreating eligibility or issuer authority in client code.
Canonical recordsFail-closed authorityLifecycle continuity
Resolve
Open the same canonical record through the public registry with field-level response parity.
Registry →Observe
Consume signed event chains and inspect webhook attempts, retry, replay, and lineage.
Webhook guide →Control
Preserve resolvability through suspension, supersession, revocation, expiration, and successors.
Event guide →ONE CANONICAL RESPONSE
Integrate the proof transaction without recreating authority logic.
Clients consume evidence scope, policy eligibility, issuer authorization, lifecycle, registry state, signature state, and mark authorization from the same response.
- Eligibility
- Evidence and protocol result
- Issuance
- Human and issuer authority result
- Registry
- Canonical public projection
- Mark
- Separate controlled authorization
const result = await provenance.verify({ publicId: 'PV-TEST-T4D004', mode: 'test' }); if (result.credential.status !== 'issued') { console.log(result.authorization.blockers); }
CANONICAL AUTHORITY
Trust remains inspectable.
Every Test Mode result carries its evidence scope, policy result, signature state, lifecycle state, registry projection, and machine-readable response.