AI Read Cost · free · no account

What does it cost an AI to read you?

We send a small retrieval system to your site with two questions and count what it takes to answer them. Tokens, requests, bytes, and whether the answer was right. Two routes: your pages the conventional way, and your llms.txt if you have one.

A scan reads your live site and takes 20 to 60 seconds. Nothing is stored. 5 scans an hour per visitor.

What is measured

Tokens to answer: Text read before the answer was found
Requests: HTTP requests made, failures included
Transferred: Bytes on the wire
Useful content: Share of what was read that held the answer
Answer quality: Graded against a written rubric

Two questions every commercial website should answer: What does this organisation do? and How much does it cost? Each is asked twice, once through your pages and once through your llms.txt. A route that never finds the answer says Not reached, not a number.

What is not claimed

Not a score. Five measured numbers, no 0–100 anything.
Not a ranking signal. This does not say whether any AI assistant reads llms.txt or whether you will be cited more.
Not any company's crawler. The reader is ours, and results describe it. The ratio between routes is more meaningful than any absolute count.
Not the web. Comparisons are against 20 sites we chose, mostly software and documentation.

In that dataset, an llms.txt under roughly 10,000 tokens was about 2x cheaper to read than the site it described. Over that size it was about 9x more expensive. A large llms.txt is not an index; it is a second copy of the website. Your result may differ, which is why we measure rather than guess.