LYRENTH
DocsPricingBenchmarksIndex statsAboutBlogFor site ownersStatusContact
Benchmarks

What famous docs pages cost an agent, raw vs indexed.

Every row below is a real page read through the Lyrenth index, with the token economics reported by the API itself: what the raw HTML would cost a model to ingest, what the clean AIDocument costs instead, and the difference. Measured 2026-07-05. Original data, reproducible with one API call.

PageRaw HTML tokensAIDocument tokensSmallerSavedFirst readRepeat read (median)
Stripe API reference
Payments
307,9022,000154x99.4%959 ms4 ms
Vercel Functions docs
Serverless
237,3902,149110x99.1%171 ms2 ms
Cloudflare Workers docs
Serverless
94,9631,37769x98.5%128 ms3 ms
GitHub REST API quickstart
Developer platform
88,6144,87618x94.5%572 ms3 ms
Kubernetes Pods concepts
Infrastructure
131,9777,47518x94.3%375 ms4 ms
React useState reference
Frontend
111,0428,15614x92.7%213 ms8 ms
MDN: Overview of HTTP
Web fundamentals
56,6925,08511x91.0%677 ms5 ms
Python asyncio docs
Languages
6,1751,2514.9x79.7%196 ms3 ms
Node.js fs module
Languages
259,563102,3722.5x60.6%446 ms10 ms
PostgreSQL SELECT reference
Databases
29,50917,5001.7x40.7%439 ms4 ms

Cost basis: $3.00 per 1M input tokens (mid-tier frontier model class), as reported in the API's economics block.

The last two columns are the same ten pages, measured 2026-08-06: what each cost to read before it was indexed, and after. Every repeat read came back in 10 ms or less, whatever the page weighs.

Read your first page Free tier · no credit card
Latency

How long a read takes, and why the second one is different.

A scraper fetches the page every time you ask for it, so it pays the open web's latency on every call. An index pays it once. The numbers below are percentiles over real reads through the production API, measured 2026-08-06.

Read pathReadsMedian95th pct
Served from the index
The page is already an AIDocument. No origin contact at all.
71412 ms126 ms
First read, server-rendered page
Not indexed yet: fetched live, parsed, and stored on the way out.
1,405386 ms1.96 s
First read, JavaScript-only page
The page ships an empty shell, so a real browser has to run its JavaScript before there is anything to read.
2112.62 s6.27 s

The bottom row is the one worth reading twice. A JavaScript-only page is the slowest thing on the web to read, and we take that hit once, on our side. Every read after it is served from the index at a median of 32 ms. That is the difference between fetching a page and having indexed it.

Percentiles over every successful read in the production request log, server-side handler time. Your own round trip adds the network between you and us, so measure it from where your agent runs.