cd /news/ai-safety/why-detecting-ai-generated-text-is-h… · home topics ai-safety article
[ARTICLE · art-138747] src=dev.to ↗ pub= topic=ai-safety verified=true sentiment=· neutral

Why Detecting AI-Generated Text Is Harder Than You Think (And What I Built Anyway)

A developer built an AI-text detector that reports a calibrated confidence score and the specific statistical signals that fired, rather than a single accuracy claim, after finding that text lacks the robust watermarking available to image models. The tool combines perplexity, sentence burstiness and known-watermark probes, with verdicts calibrated by text length, and is available at detectaiwatermarks.com.

by read1 min views1 publishedSep 24, 2026

Every "AI detector" landing page promises 99% accuracy. Then you paste in a

paragraph you actually wrote yourself and it flags you as ChatGPT. I kept

seeing this in the wild — students wrongly accused, editors discarding human

copy, and a pile of tools that were really just guessing.

So I went down the rabbit hole of how AI-content detection actually works,

built a tool to test the claims, and learned that the honest answer is far more

interesting than the marketing.

Image models can embed an invisible statistical watermark (the SynthID-style

approach), and that's a real, checkable signal. Text is different. A model

generates tokens probabilistically; there's no natural place to hide a bit

string that survives copy-paste. Researchers have proposed watermarking the

logit distribution (green/red token lists), but it breaks under:

If a tool claims 100% accuracy on short text, it's lying. Anyone who's actually

benchmarked one knows it.

In practice detectors lean on a few weaker, statistical signals:

None of these is a watermark. They're probabilities, and they fail on edited,

mixed, or short content. That gap between "statistical likelihood" and

"provenance" is where most products quietly pretend to be something they aren't.

I got tired of the gap, so I built a detector that reports honestly — a

confidence score plus an explanation of which signals fired, rather than a

single fake certainty. You can try it here: https://detectaiwatermarks.com

The technical choices I'd highlight:

python
signals = {
    "perplexity": score_perplexity(text),
    "burstiness": sentence_variance(text),
    "watermark_scan": probe_known_watermark(text),  # often None, that's fine
}
verdict = calibrate(signals, length=len(text))
── more in #ai-safety 4 stories · sorted by recency
── more on @chatgpt 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/why-detecting-ai-gen…] indexed:0 read:1min 2026-09-24 ·