Mint a cryptographic attestation for content you want to protect. Your personal issuer and signing key are resolved automatically. Hash the content client-side (SHA-256) and submit the hash with file metadata.
Mint a cryptographic attestation for a piece of content you want to protect. Your personal issuer and signing key are resolved automatically — you do not need to create an issuer or register a key. Hash your content client-side with SHA-256 and submit the hash along with file metadata. The endpoint returns a protection record with a shareable proof URL you can use to demonstrate authorship. Rate limits depend on your plan tier:Documentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
| Plan | Protections per month |
|---|---|
| Free | 50 |
| Creator | 500 |
| Pro | Unlimited |
content_hash and protected_at so you can confirm which content was protected and the exact timestamp without making a follow-up call.
image/png, application/pdf, text/x-python).code, research, design, media, dataset, ai-output, writing, digital-art, or other. Defaults to other.public or private. Defaults to private.API key for machine-to-machine authentication
SHA-256 hash of the file content, computed client-side.
Human-readable title for the protection.
Optional description of the protected content.
MIME type of the content (e.g. image/png).
Original file name including extension.
File size in bytes.
Content category. Defaults to other.
code, research, design, media, dataset, ai-output, writing, digital-art, other Optional AI-extracted metadata object.
Whether the protection appears on your public portfolio. Defaults to private.
public, private