Docs
CommunityJev Cookbooks
Content Audits with Jev
Official Jev cookbook that audits all 279 pages of the Django documentation in under 5 seconds for about $0.10, asking 45 score, choice, and noul questions per page and plotting quality against importance.
- Format
- Docs
- Reading time
- 2 min
- Published by
- Community
- Added
- Nov 2026
Highlights
- Audits 279 Django documentation pages and 584,234 words in under 5 seconds for about $0.10.
- Each request holds one page and 45 questions covering quality, importance, classification, problems, and quick wins.
- On one test page, the median request took 144 ms with 1 question and 151 ms with all 45.
- The 45 questions count as input tokens and make up roughly 40% of the $0.10 cost.
- A deep scan button asks Jev which sentence holds each problem and links findings to their line on GitHub.
Questions about this entry
Short answers drawn from the linked project or page.
Clone the Django repository with git clone --depth 1, set TYPESAFE_API_KEY, and run audit.py. The sample asks 7 of the 45 questions, sends 12 pages at a time, and lists the 20 pages with the highest priority.
About $0.10 for all 279 pages. The 45 questions per request count as input tokens and make up roughly 40% of that cost; more questions add cost but little time.
On one test page the median request took 144 ms with 1 question and 151 ms with all 45, because Jev answers every question in a request in parallel. The full audit runs in under 5 seconds.
It uses Score, Choice, and Noul questions: 8 on quality, 5 on importance, 7 classification questions such as Divio type and fix effort, 21 problem flags, and 4 quick-win flags.
One request holds one page plus site context describing docs.djangoproject.com and noting that Sphinx reStructuredText markup is source markup, not an error. An API key from the TypeSafe console is required.
There is no limit on the number of questions, only on context length. The audit asks every question that might be useful, including ones that flag only a handful of pages.
Each page has a deep scan button that asks Jev which sentence holds each problem and highlights it. Findings link to their line on GitHub, so flagged typos can be fixed in a pull request.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.