Sign inVerified Badge
Don't let a flawed AI detector ruin your client relationship.
A client running your work through an AI detector and getting a false positive is a real, specific fear — and one bad guess shouldn't cost you the relationship. Pre-verify your human effort: seal the finished file, get a scannable proof badge, embed it on the deliverable.
Free to start, no card required — takes about a minute to set up.
How it works
1. Verify once
A one-time government-ID check (about a minute, hosted by Stripe). Reused across every future seal — no re-scanning your ID each time.
2. Seal the file
Just upload your finished PDF from your dashboard — SignedBy hashes it, timestamps it, and generates your badge.
3. Embed the badge
Drop the badge on your invoice, portfolio, or the deliverable itself. A client scans it and lands on a public ledger page — no account needed.
What this actually proves
A Verified Badge is a provenance and integrity proof, not an AI-detector rebuttal. It confirms this exact file existed, unaltered, as of a cryptographically verified timestamp, sealed by an identity-verified person — a real, useful, different claim from “an algorithm guessed this is human.” Honest framing, on purpose: overclaiming here would undercut the one thing that actually holds up under scrutiny.
Generate Your Proof
Free to start — 3 seals a month included, no card required. Need more? Pro plan or higher gets unlimited sealing, no per-seal charge.
Generate Your Proof →Frequently asked questions
Does this prove my work wasn't written or made with AI?
No — and it doesn't claim to. A Verified Badge proves this exact file existed, unaltered, as of a cryptographically verified timestamp, sealed by an identity-verified person. That's a real, different, useful claim from "an AI detector says this is human," which is exactly why AI detectors have a false-positive problem in the first place: they're guessing at authorship, not proving timestamp and integrity.
What does the client actually see?
A badge on your deliverable — a QR code, the SignedBy mark, and a short verification link as plain text, so it reads as legitimate even printed or screenshotted. Scanning or visiting it lands on a public ledger page: your name, when the file was sealed, and confirmation it hasn't been altered since. No account or login needed to check it.
What if my identity check is old?
Your first seal verifies your identity via a government-ID check (about a minute, hosted by Stripe). Later seals reuse that same verified check rather than re-scanning your ID every time — cheaper and faster. The ledger page always shows "identity verified on [date]" alongside "sealed on [date]" as two separate facts, so it's clear if the identity check itself is from earlier than this specific seal.
Does this work for non-PDF files?
PDFs only for now. If your finished work is a design export, code, or something else, export or print it to a PDF first, then seal that.
What plan do I need?
Any plan, including Free, no card required. Free includes 3 Verified Badge seals a month. Pro plan or higher gets unlimited sealing, no per-seal charge. Seal a file right from your dashboard's New Document menu — developers can also do this from Console chat or the API, see the developer docs.
What actually makes the timestamp "cryptographically verified"?
Every seal is submitted to a real Time Stamping Authority (Sectigo's public RFC 3161 service, with FreeTSA as an automatic fallback if Sectigo can't be reached) that signs the file's hash together with the time. That's independently verifiable by anyone, trusting only the TSA — not just a date in SignedBy's own database. The ledger page at signedby.ai/verify shows which TSA backed a given seal.
Also on SignedBy: Console · Magic Quote · Verify a document · API & MCP docs