Check submitted copy or web pages for AI-writing tells
Run guest posts, freelancer copy or a site's pages through Jev's checks for common AI-writing tells before you accept or publish them.
Author's figure: Author's figure: 35 tells, one check at 243 ms, $0.00015 (Jon Kraayenbrink). Reported by the builder, not measured by us.
The use case
Editors, agencies and site owners receive copy from freelancers or guest writers and want to know if it reads like unedited AI output before they pay or publish. These tools check text or a whole page against a list of known tells, from filler phrasing to fake testimonials and stock layouts, and give a score with the tells found. The editor uses the list to ask for a rewrite. A high score is not proof that someone used AI, so it should start a conversation with the writer, never decide payment or a ban by itself.
Example workflow
- Paste a draft or a URL into the checker
- Fetch page text with Firecrawl if checking a site
- Ask Jev Noul questions for each tell on the list
- Show the score and the tells found to the editor
- The editor decides on edits and talks to the writer
Tools
- Jev (TypeSafe AI)
- Firecrawl
- Google Docs
Risks and guardrails
- Human writing can trip the same tells
- Writers may be treated unfairly on a score alone
- Tell lists go stale as writing styles shift
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- AI slop detector by Jon Kraayenbrink on Made with Jev: madewithjev.com/builds/ai-slop-detector
- Jev Detector by Jozef Gherman on Made with Jev: madewithjev.com/builds/jev-detector
- Jev Detector: original post or repo by Jozef Gherman: x.com/jozef_gherman/status/2100627898436571555
- Firecrawl MCP server (official page): github.com/firecrawl/firecrawl-mcp-server (checked 2026-11-09)