Certificates

A certificate is a public record of one text at one moment: its DropSlop scores, the scores from two outside detectors, GPTZero and Pangram, and a fingerprint of the text so anyone can check it has not been changed since.

What a certificate addsCopy Anchor Link

• Outside scores. DropSlop sends the text to GPTZero and Pangram and records their scores beside its own. Apart from the API's "verified" modes, this is the only time DropSlop sends your text to another company's detector. See Privacy and data.
• A status, from the scores: verified human, human with AI edits, or AI detected.
• Fact-Guard, if you give the original draft as well: a check that the certified text keeps its names, dates and figures.
• A fingerprint (a SHA-256 hash) of the text, and a signature, so the record can't be changed without it showing.

Like every score, these are estimates, not proof. See How to read a score.

The certificate pageCopy Anchor Link

Each certificate has its own page at https://dropslop.ai/v/<certificate id>. It shows the title, date, word count, the scores and the fingerprint.

• Check a text against it: paste the text into the page. Your browser works out the fingerprint itself and compares it, so the text you paste is never sent anywhere.
• Badge: https://dropslop.ai/v/<id>.svg is an image you can put on a page; the certificate page gives you the snippet.
• Data: https://dropslop.ai/v/<id>.json returns the record as JSON.

Certificates are public by default: anyone with the link can see the page, including a short preview of the text.

Making a certificateCopy Anchor Link

Certificates are made through the API (POST /v1/certify) or the MCP server, and need an account or an API key. Each one uses one certificate from your allowance for every 1,000 words or part of them: a 2,400-word text uses 3. A text GPTZero and Pangram scored in the last 7 days uses none. See Words, certificates and plans.