Your AI visibility score is a guess.

Most tools type a prompt into ChatGPT, count the brands in the answer, and sell you the percentage. Ask again and the answer changes. Kymo records what AI engines actually did on your site: every read, every visitor they sent, every sale that followed.

14-day free trial. No card required.
kymo doesn't guess. It watches.
Exhibit A

Same prompt. Five runs.
Five different scores.

A visibility score is one draw from a system that answers differently every time you ask. The dashboard shows you the draw. It hides the dice.

"AI share of voice" · a typical tool
31%
prompt: "best analytics for a SaaS startup"
run 131%
run 212%
run 30%
run 424%
run 518%
Illustration. One account, one datacenter, one moment, a prompt the vendor picked.
SAMPLED
kymo · what actually happened · /docs/astro-setup
09:12:04 ClaudeBot · GET /docs/astro-setup · 200
09:40:17 ChatGPT-User · GET /docs/astro-setup · 200
10:47:31 visitor #000412 · arrived from claude.ai
10:52:09 visitor #000412 · goal: signup
11:03:58 visitor #000412 · purchase · $99.00
Run it again tomorrow. These rows will still say the same thing.
RECORDED
01 · THE PROMPT

They pick the question.

Change the prompt list and your score moves. Nothing on your site changed.

02 · THE DRAW

The answer is random.

Ask the same question twice and a different set of brands comes back.

03 · THE ROBOT

Nobody real asked.

A scraper in a datacenter is not your buyer, in your city, with their history.

04 · THE MENTION

A mention pays nothing.

Even a perfect score stops at a brand name. It never reaches your revenue.

Measured, not estimated

A score is an opinion.
A log line is a fact.

A visibility scorekymo
SourceA prompt someone typedA request that hit your server
Run it twiceA different numberThe same rows
Who was thereA script in a datacenterThe AI engine, then your real visitor
Where it endsA brand name in an answerA goal or a payment on your site
What you can bill for"Share of voice"Revenue with a page path attached
The receipt

One page, traced from read to revenue.

01 · Readserver-side
ClaudeBot
GET /docs/astro-setup
status200
time09:12:04
02 · Referredclaude.ai
visitor #000412
landed /docs/astro-setup
first touchclaude.ai
time10:47:31
03 · Paidrevenue
$99.00
goal: purchase
AI landing page/docs/astro-setup
time11:03:58

Reads come from one snippet on your server: Next.js, Express, Astro, SvelteKit or Workers. Visits and sales come from one script tag.

Who asks for this

For people whose number gets questioned.

SaaS founders

See the hour before the signup.

Your analytics show the signup and the click that came just before it. Kymo shows the AI answer that first sent that person, and the page it sent them to.

AEO & SEO agencies

Your client will ask where the number came from.

Answer with log lines, visitors and revenue, not a share-of-voice chart you can't reproduce.

Docs-led dev tools

Find the tutorials that sell.

See which help pages AI engines read, and which of them send developers who sign up.

Next.jsAstroSvelteKitExpressWorkers
Field recording

Don't trust us either. Open the demo.

The actual dashboard on sample data — visitors landing, AI reading, goals converting. No signup, no sales call.

kymo · example.comREC ●
Pricing

Pay for real numbers, not vibes.

Metered by events, and only human ones. Both plans start with 14 days free — no card required.

Solo
$9/mo
$90/yr · two months free

Up to 10,000 events a month. Every feature included — goals, Stripe revenue, AI reads, and the weekly report.

Start 14-day trial →
Studio
$29/mo
$290/yr · two months free

Up to 100,000 events a month. Same instrument, bigger dial — for sites that have found their audience.

Start 14-day trial →
CAPGo over your limit and the dashboard pauses — never your data. Upgrade and it's all there.

Stop reporting a guess.
Start reporting a receipt.

Every AI read, every visitor it sent, every sale that followed. Free for 14 days, no card required.