The seal is the same. What changes is what you need to prove.
Certifying is free and needs no account, whoever you are. These four sections only explain how it fits each trade.
Let a third party set the date, not your word for it
When someone reposts your photo or your cut and calls it theirs, the argument collapses into who had it first. A screenshot with your phone’s date does not settle that. A timestamp issued by an external authority does.
- PDF certificate carrying a thumbnail of your work, its fingerprint and the exact hour
- A public link the other party checks on their own, with no account and nothing asked of you
- Usable in platform claims and as an annexe to a formal complaint
Seal it before they delete it
A post is edited or gone in minutes, and with it the proof that it ever existed. We keep what the server actually returned — content, headers and hour — and anchor it where nobody, us included, can rewrite it.
- Sealed capture of a public address: you paste the URL, that is the whole step
- Batch sealing for an entire assignment; every item gets its own certificate
- Documented chain of custody: fingerprint, RFC 3161 seal, Merkle log and Bitcoin
Publish knowing where the material came from
Running third-party content without documented provenance is the most expensive editorial risk there is, and the easiest to avoid. Every licensed item arrives with its record: who the rights holder is, on what basis they are granting it, and how far the permission goes.
- Written consent, dated and sealed — not a message in a thread
- Rights holder with verified identity and a declared basis of rights
- Explicit licence scope, so the desk knows what it may actually do
Checking a seal is one HTTP request
Verification is public, free, unauthenticated and unmetered. You can check any certificate from your own code, or let an agent do it without anyone having to ask you.
- Open verification endpoint: returns validity, sealing time and anchor block
- MCP server with scoped tools and a person always kept in the loop
- The proof does not depend on us: the anchor is checked against Bitcoin
You do not have to pick a profile
All of the above starts from the same act: upload a file and get its seal. Start there and decide afterwards.
The tools themselves are currently served in Spanish. The proof they produce — a SHA-256 fingerprint, an RFC 3161 seal and a Bitcoin anchor — is language-neutral and verifiable from anywhere.