Saylent

Run it automatically

The places Saylent runs without you typing the command - a CI step, an agent, and your own code.

The command is one person at one terminal. These are the same engine with nobody watching: a check on every push, tools an agent can call (directly, or through the Claude Code plugin), and the pipeline imported straight into your own program.

Which one you want

You wantUseWhat it costs
CI to fail when a search or user-fetch bot gets blockedthe Action$0 - it has no keys and calls no model
Claude Code to run the checks for you, with a price shown before any spendthe Claude Code plugin$0 for the crawler check and reading reports; your own credits for an audit, after you agree to the estimate
An agent to run the audit and read the result backthe MCP serverYour own credits: about $0.80 to $1.20 for a smoke run with four engines, $5.10 to $7.10 for a full one, checked against max_usd before anything is sent
The pipeline inside your own program, with your own database@saylent/engineYour own credits, at the same per-run cost
Your own presentation of a run you already have@saylent/report$0 - pure functions, no network
A re-check on a schedule, with no app deployeda cron entry or a scheduled workflowYour own credits, at the same per-run cost, once a month

The Action and a scheduled saylent verify are different jobs and belong in different workflows: the Action is the $0 gate that runs on every push, and a verify spends real credits, so it goes on a schedule you chose.

They cannot drift

saylent audit's flags and the MCP audit tool's arguments are generated from one shared schema, and a test fails the build if the argument table on the MCP page stops listing every field. The Action runs the same gate-check code the CLI does. Nothing here is a second implementation.

On this page