Understand the record
Read the documentation and choose the record type and verification flow.
Loading...
For developers
Use APIs and SDKs to issue records, verify evidence, and connect agent identities with recorded actions.
For developers
Truthlocks exposes the same foundation behind its applications through service APIs. Start with issuance or verification, then connect identities, receipts, and workflows when your application needs them.
The documentation is the source of truth for endpoint contracts, supported SDKs, authentication, and configuration.
For developers
Read the documentation and choose the record type and verification flow.
Configure authentication and integrate the supported API or SDK.
Exercise success, invalid signatures, revocation, and dependency failures before production.
Details and limitations
Create or join a Console workspace before configuring business APIs, SDKs or agent integrations. The same workspace serves a solo developer and a development team. Documentation gives you the contracts and examples; it does not create credentials. A personal Verify account serves your own records and is not the configuration workspace for an organizational integration.
Start with a non-sensitive sandbox example and the workspace's supported API access. Match the credential to the environment and grant only the required permissions. Keep secrets on your server or in your approved secret store, not in frontend bundles, public issues or copied tutorials. Production access follows onboarding and approval; do not assume a working sandbox request has enabled it.
Pick one event in your application: a course completed, a document version approved or an agent action reported. Map that event to the documented record format, retain the returned identifier and show the recipient a verification path. Handle an altered payload, revoked record, missing issuer evidence and unavailable dependency distinctly.
Before expanding, exercise retries and inspect the resulting record in the same workspace and environment. Your application remains responsible for its own authorization, privacy and user experience. The evidence page offers reproducible checks; the integration directory links to package-specific installation instructions and supported operations.
Watch the idea · 33 seconds
An AI action needs a useful record. Decide what to capture before you sign it—and keep secrets out.
AI presenter and illustrative scenes. This is a product explanation, not a live verification result or customer testimonial.
Build with receipts in ConsoleYour AI agent needs a receipt. Your customer's secrets don't belong in it. Before you sign an action record, choose what it should contain. Keep passwords, private messages and unnecessary personal details out. Truthlocks supports signed action receipts so you can check the recorded evidence. A signature does not make oversharing safe. What would you leave out of your agent's receipts?
Two workspaces. Choose by what you want to do.
Developers, businesses and teams share the same Console. Verify is for personal records and checking shared proofs. You do not need a large team to choose the developer path.
console.truthlocks.com
Build with APIs and SDKs, manage workspace credentials, register issuers and AI agents, invite teammates and review usage. Start in sandbox, then complete onboarding for production.
Create a Console workspaceverify.truthlocks.com
Manage your own documents, credentials and signed statements. Share a proof link with someone who needs to check your record. Personal plans and records stay in this portal.
Create a personal accountOnly checking a record? Open public verification. No account is needed for an intentionally public proof. Compare accounts and sign-in options.
Before you start
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.