Loading...
Choose the right account
Use Console for APIs, SDKs, AI agents and organizational work. Use Verify for your own records and statements. Public proof recipients can check evidence without creating an account.
console.truthlocks.com
Build an integration or manage your organization's records. This is also the right account for a solo developer working with APIs, SDKs or AI agents.
verify.truthlocks.com
Keep and share your own records, credentials and signed statements. Use this for personal work rather than configuring your company's integration.
At a glance
| What you want to do | Where to go | What to expect |
|---|---|---|
| Build an app, use an SDK or connect an AI agent | Business & Developer Console | Workspace credentials, sandbox testing and integration setup |
| Issue records for a company or manage a team | Business & Developer Console | Issuers, access controls, onboarding and workspace usage |
| Publish a personal statement or manage your own records | Personal Verify portal | Personal records, sharing preferences and account allowances |
| Check a proof link received from someone else | Public Verify page | Inspect available evidence without an account for public records |
| Learn an API or install an integration | Documentation + Console | Read the guide, then configure the workspace used by the integration |
Before you continue
Use Business & Developer Console when you are building an application, integrating an SDK, managing agent identities or configuring workspace API access. Choose it even when you are the only person building the integration. Enter accurate project and organization information; production access still requires the applicable onboarding checks.
No. Developers and organizations use Console at console.truthlocks.com. Documentation explains how to build; Console is where you manage the workspace, credentials, issuers and environments used by your integration.
Verify at verify.truthlocks.com is the personal portal for your own records and statements, and the public place to check shared proofs. A personal account is not the workspace for your company's team, organizational issuers or business integrations.
No. Open an intentionally public proof link or the public verification page. Creating and managing records requires the appropriate account; inspecting public evidence does not. Private records remain subject to access controls.
Keep your personal records in Verify. Create or join the appropriate Console workspace for the integration, and use its credentials with the matching API environment. Signing in to Verify does not automatically move personal records, subscriptions or permissions into Console. Contact support if you need help choosing or locating a workspace.
New business workspaces begin in sandbox. Complete the required onboarding and approval steps before production access. Billing country verification, account permissions, plan limits and provider setup still apply. A sandbox example is not evidence of production readiness.
Missing an account email? Check spam and confirm the address entered. Check service status or contact support.