Skip to content
OneLessTool
Audit

Maintained by agents, approved by humans

OneLessTool's content is designed to be maintained by AI agents — including Grok bots via the xAI API — without letting a hallucinated price reach users.

The pipeline

  1. Content is files. Every tool, capability, workflow and guide is a JSON/Markdown file in content/. Agents edit files; they never write to production directly.
  2. Schema + integrity checks. npm run content:check validates every record against Zod schemas and checks every cross-reference. verified evidence without a source URL and date fails the build.
  3. Scheduled maintenance. A GitHub Action (.github/workflows/content-maintenance.yml) runs npm run agent:maintain weekly. The Grok maintainer picks the stalest records, asks Grok (with live web search) to re-check prices against the vendor's own pricing page, and writes proposed changes with source URLs.
  4. Pull request, not publish. Proposed changes go into a pull request labelled content-bot. CI runs the content check, type check, tests and a full build.
  5. Human merge → deploy. A maintainer reviews the diff (each price change shows old → new with a citation) and merges. The deploy workflow ships to Cloudflare.

Rules every agent follows

They're in AGENTS.md and docs/CONTENT_STYLE.md. The short version:

  • Never invent prices, plans, limits or features.
  • verified only with a primary source checked today; otherwise unverified with a note.
  • Keep the honest "reasons to keep paying".
  • One concern per PR; run npm run content:check before opening it.

Running it yourself

XAI_API_KEY=… npm run agent:maintain -- --limit 5 --dry-run

Any other OpenAI-compatible model works via MAINTAINER_BASE_URL / MAINTAINER_MODEL.