docs.dev vs Slopsift

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

Catch AI writing tells with a custom-trained NLP parser, not a word list. SlopSift runs locally in your browser, CLI, or VS Code, with exact, explainable findings.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Slopsift

Catch AI writing tells with a custom-trained NLP parser, not a word list. SlopSift runs locally in your browser, CLI, or VS Code, with exact, explainable findings. SlopSift uses a small dependency parser we trained to map the relationships between words and find canned arguments, unsupported claims, and filler. As an AI language model, let's delve into the load-bearing idea behind this solution. To be fully transparent, I am genuinely open to both designs. Notes attached, and they are a fuller record than the summary.