Verify
Resolve governed public record state with explicit lifecycle, trust, limitations, and authority boundaries.
API reference →DEVELOPER INTEGRATION
One governed trust system for public records, applications, and AI.
Consume machine trust, registry, lifecycle, events, webhooks, SDKs, and MCP without recreating eligibility, actionability, or authority logic in client code.
Governed recordsFail-closed authorityLifecycle continuity
Resolve
Open the same governed record through the public registry and machine-trust endpoint.
Registry →Observe
Consume governed event chains and inspect webhook attempts, retry, replay, and lineage where your integration is authorized.
Webhook guide →Control
Preserve resolvability through suspension, reactivation, supersession, revocation, expiration, and successors.
Event guide →AI + MCP
Keep record state, lifecycle, trust, actionability, and authority state distinct in agentic workflows.
AI integration 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); }
Use the public endpoint first. Add privileged integration only when the workflow needs it.
Public governed records can be resolved through machine trust without an API key. MCP tools and privileged operations remain subject to their own authorization contract.
PUBLIC TRUST
Trust remains inspectable.
Governed records expose their evidence scope, trust state, lifecycle state, limitations, and authority boundary without upgrading record state into authority that is not live.