Create a developer account
Establish the identity and organization context that owns the integration.
Create accountDevelopers
Integrate trust workflows without hiding the control plane.
Build around identity, verification, credentials, Passports, reputation, and public proof using scoped access, explicit contracts, event delivery, and operator-visible audit history.
Integration journey
A governed path from account to operating integration.
Work in sandbox
Prepare scoped access and test trust workflows without treating test activity as production evidence.
Open workspaceSubscribe to events
Configure signed webhook delivery for the verification, credential, Passport, and trust events your system needs.
Manage webhooksReview usage and audit history
Keep integration activity, key lifecycle, delivery attempts, and usage records visible to accountable operators.
View developer toolsControl plane
Security and observability are integration requirements.
- Scoped keys with rotation and revocation paths
- Signed webhook delivery and observable retry state
- Idempotent mutation expectations for safe integration
- OpenAPI-oriented contracts and explicit error behavior
- Sandbox-first setup with production access kept separate
- Usage and audit records available to authorized operators
Need an institutional integration?
Define the data boundary before production access.
We will map the actors, evidence, permissions, events, data residency needs, and human review path for the proposed integration.