API-first content authenticity layer for public websites.
Verify authenticity of
any public content.
GetProofAnchor lets you attach a cryptographic proof to your articles, docs and product pages and gives your readers a one-click way to check if what they see still matches the original version you published.
Blogs, docs, changelogs, AI-generated posts, legal pages, product pages…
Public read-only API, strong ETags, CDN-ready from day one.
Embed a tiny badge and let readers verify with a single click.
"content": "Tady je slovo list v obsahu"
Reader clicks “Verify this content” and sees whether the current page still matches the stored proof.
How GetProofAnchor fits into your stack
From your backend or (soon) dashboard, normalize your content and register it as a proof. Each proof gets a stable ID and SHA-256 fingerprint.
Add a small JS snippet to your article, docs page or changelog. The widget reads the visible text and can be targeted to specific elements.
On click, the widget calls the public /verify API and shows whether the content is authentic or modified.
Where GetProofAnchor makes sense first
Attach proofs to AI-assisted posts so you can prove what was actually published – and detect silent edits or hallucination fixes.
Protect API docs, onboarding guides and security pages from unnoticed changes. Prove that your docs say what you think they say.
Anchor your changelog entries so customers can verify what changed and when, even if something is later edited or removed.
Terms, privacy policies, security commitments – add proofs and let your legal team (and users) verify previous versions.
Link a story to a proof, so readers can see if an article has been modified since publication – and by how much.
Anchor key claims on your website (pricing, SLAs, feature pages) to demonstrate integrity to enterprise buyers.
Why content authenticity matters
The web is full of AI-assisted content, silent edits and partial screenshots. Without a way to prove what you actually published, it’s hard to defend yourself when something goes wrong.
- Readers lose trust when articles keep changing without transparency.
- Legal disputes are messy if you can’t prove the original wording of a policy or statement.
- “Gotcha” screenshots can be misleading if they don’t match what’s on the site now.
GetProofAnchor doesn’t try to moderate content or judge whether something is “true”. It focuses on one narrow promise: proving that a given piece of content did – or did not – match what you originally anchored.
As a reader, you don’t want to diff HTML or check archives. You just want to know:
- “Is this the original version?”
- “If not, how different is it?”
The verify widget gives a simple answer: Authentic or Modified, with a fingerprint and details for those who care.
For developers
Integrate the API, compute fingerprints in your own stack and treat proofs as part of your infra.
Read API & widget docsFor writers & editors
Add a small “Verified” badge to your articles and show readers you take authenticity seriously.
Generate embed codeFor teams & companies
Start on the free plan, and upgrade when you need more proofs, higher limits or SLAs.
See pricing & limitsStart verifying content in less than a minute.
Use the public verify page, embed the widget, or hit the API directly. No signup required for the prototype.