Docs
What Saylent is, what one run gives you, and the six sections these docs are organized into.
Saylent asks real buyer questions to real AI assistants - ChatGPT, Claude, Gemini and Perplexity, through their official APIs - records every answer verbatim, and tells you whether your brand was recommended, mentioned or absent, which rival was named instead, which pages the assistants cited, and what to fix. It runs on your own provider keys, on your own machine or your own infrastructure. Nothing is sent through us and nothing is stored by us.
These docs are one story in six parts, in the order people actually need them.
Run it once
One command, your own keys, a report you can open in five minutes. No account, no database.
Keep score as a team
The same engine with a memory: brands, history, a fix tracker, share links, and as many user accounts as you like on one deployment you own.
Operate it for others
The console for whoever owns the keys and the bill: spend cap, kill switch, models per role, users, runs, takedowns.
Automate
A $0 CI gate on every push, an MCP server so an agent can run it, and the pipeline as a library in your own code.
Understand
What a run does at each of its nine stages, what it costs, what leaves your machine, and what it refuses to claim.
Project
The $0 dev setup, the extension points, the changelog, and where to report a security issue.
| What you need | Where it lives | What it costs |
|---|---|---|
| One report on one domain, today | The CLI: npx saylent audit example.com | about $0.60 to $1.20 with four engines |
| To know which AI crawlers your site lets in | The site check: npx saylent gate-check example.com | $0, no keys |
| History, a fix tracker and more than one account | Deploy the app | the same per run, on your own keys |
| A gate that fails a push when a bot is blocked | The GitHub Action | $0, no keys |
| Your agent or your own program to run it | The MCP server or the library | the same per run, on your own keys |
Before you spend anything
- What it costs - real numbers per profile, from recorded runs, and the caps that stop a run before it starts.
- What gets sent to providers - exactly what leaves your machine, to whom, and what never does. No telemetry, anywhere.
- Methodology - how presence is decided, why a judge from the other provider family scores the answer, and the limits we state out loud.
- Compared with hosted tools - sourced prices, dated, and the five things the hosted tools still do that Saylent does not.
- Walk the live demo - a read-only copy of the app on the Kestrel Uptime sample: every screen, nothing saves, no account, $0.