Truthlocks

Signed records, shareable proofs and accountable AI actions

Visit website

SubscriptionCodeAPISecurity1,228 impressions#22 of its week3 comments

Maker links to DevHunt

>log in to comment

Nnaa[maker]· 20d ago
Kelvin, thank you for the question. One example is a support agent proposing a refund: the application can keep a signed record of the agent identity, requested action and relevant metadata. A reviewer can check the signature and detect changes to those signed fields. To establish that money actually moved, they still need the payment provider’s transaction evidence; a signed receipt alone does not prove execution. You can try the smaller building block without an account: verify our synthetic receipt, change its action, and watch the check fail. Node and Python instructions: https://github.com/truthlocks/maip/tree/v2.1.0/examples/developer-validation Which workflow would you like to try this with? Happy to work through the trust boundaries and integration steps here. — Nnaa, Truthlocks co-founder; reply prepared with AI assistance.
KELVIN KAIMENYI· 20d ago
This is really interesting, Nnaa. I like the idea of being able to verify whether an AI agent actually did what it claims and whether the record has been changed. I’m curious to see how this can be applied in real-life situations and how people and businesses will use it. Great to see you building something meaningful! 👏🏽
Nnaa[maker]· 21d ago
Hi DevHunt! I’m Nnaa Igwiloh, co-founder and CEO/CTO of Truthlocks, building it with Emmanuel Adeyinka, our co-founder and COO. We’re inviting developers to try a concrete experiment: verify a signed AI-agent receipt, change its action, and check that verification fails. Our public walkthrough works in Node or Python without a Truthlocks account or API key. It explains the trust assumptions and the limits of signature verification. Try it here: https://github.com/truthlocks/maip/tree/e5451ad/examples/developer-validation What would you want to integrate first: AI-agent action receipts, document integrity checks, or credentials? Tell us where the example or documentation gets confusing—we’d value your feedback. Prepared with AI assistance on behalf of Truthlocks.

Truthlocks provides cryptographic trust infrastructure for digital records, signed statements and AI agent actions. Individuals and organizations can publish signed text with explicit disclosure controls, share public proof links and check whether presented content matches the signed evidence. Proof Frame supports an editable demonstration copy without changing the original signed record, and linked revisions retain the relationship between statement versions. Businesses use a workspace console; developers integrate supported APIs, SDKs and MAIP integrations for machine identity and signed action receipts. Public proof pages distinguish content integrity, digital signatures, issuer assurance and available status and transparency evidence. A self-registered issuer is not independently accredited, and a valid signature is not proof that the underlying statement is true. The hosted platform is proprietary. Public SDKs and integrations have their own repository licenses. A recipient can open an intentionally public proof without creating an account. Eligible public text records include a separate editable demonstration copy: changing a character tests the content fingerprint while leaving the original signed statement intact. The interface explains what was signed, which checks completed and what evidence remains unavailable. This makes the workflow useful for public announcements, professional declarations and technical records. Signing a revised statement creates a linked version instead of silently overwriting the original. For teams integrating the product, documentation and public examples provide a starting point for evaluating the supported record and receipt workflows. Issuance follows account permissions, onboarding requirements and applicable usage allowances. Organizational operations are metered; personal plans and allowances are separate. The public website links to current pricing and a reproducible technical evidence page. Try Proof Frame: https://www.truthlocks.com/proof-frame Technical evidence: https://www.truthlocks.com/resources/evidence Runnable MAIP v2.1.0 examples: https://github.com/truthlocks/maip/tree/v2.1.0/examples/developer-validation Documentation: https://docs.truthlocks.com

Code API Security

More Code tools →74 free dev tools →

Create proof. Make it easy to check
AI autopilots record every action as a receipt
Machine identity gives cryptographic trust to AI agents
Organize evidence trails for finance, procurement, claims, and fraud

Key features

6 features of Truthlocks

Create signed records — Issue digital records (credentials, documents, action receipts) with cryptographic signatures.
Record verification — Check available signatures, content integrity, expiration, revocation and transparency evidence separately. Missing evidence remains explicit.
Agent identity management — Register machine identities and scoped permissions. An identity entry alone does not prove an external action happened.
Workflow integration — Connect records and receipts to business or AI workflows for audit trails.
APIs & SDKs — Integrate verification, issuance, and identity functions into apps via REST APIs and SDKs.
Transparency logs — Generate proof bundles and logs that can be inspected outside the original system.

Use cases

Issue and share verifiable certificates for training completion
Audit AI-driven financial approvals with signed action receipts
Inspect signed AI action evidence without treating it as proof of regulatory compliance

Truthlocks FAQ

What does Truthlocks actually verify?+

Truthlocks reports supported signature, integrity, status and transparency checks separately. Issuer assurance is distinct; a valid signature does not prove factual truth.

Do I need to understand cryptography to use it?+

No. Individuals can use the verification portal, teams can use the console, and developers can call the same capabilities via APIs and SDKs.

Is the platform only for certificates?+

No. It also supports documents, signed action receipts, AI agent identities, and evidence for operational workflows.

Is Truthlocks free or open source?+

The hosted platform is proprietary and issuance is subject to permissions, onboarding and usage allowances. Organizational operations are metered; personal plans are separate. See truthlocks.com/pricing. Public SDKs and integrations use their own repository licences.

Edited by the makers, based on truthlocks.com · Oct 18, 2026. Details may change; check the official site.