Engineering notes on building the AI-readable web index: AIDocuments, agents that read the web, and the infrastructure behind Lyrenth.

Clean text is half the job. How AIDocument's structure, headings, links, and media, lets agents navigate, cite, and act on pages instead of just reading them.

Five checks to run on your agent's web access before Cloudflare's new crawler defaults land: inventory, identity, failure handling, freshness, and fallback.

Agents get blocked for behaving like strangers. What polite machine access looks like, why evasion is a treadmill, and how identified reading stays welcome.

A practical guide to caching the web for agents: why every agent team ends up building a cache, what staleness actually costs, and what a shared index changes.

Lyrenth's index crossed two billion AI-ready documents this week, on a public live counter. Here is what an index that size changes for agents as the web's defaults turn restrictive.

Cloudflare's new defaults land on September 15. Here is what gets blocked, who is affected, what stays allowed, and what agent builders and site owners should do before the date.

Why one crawl serving every reader changes the cost of machine-read web data: real token numbers, cache math, and what shared infrastructure means for origins.

What llms.txt is, the exact file format, how it differs from robots.txt and sitemaps, who adopted it, and how to write one that AI assistants actually use.

What robots.txt actually governs in 2026, how AI crawler tokens work, recipes to allow search and block training, and why verification matters as much as rules.

Cloudflare's new defaults block agent fetchers on ad pages and per-fetch access is getting priced. How agent builders keep reading the web through an index.

Cloudflare blocks Training and Agent crawlers by default on ad pages from September 15, 2026. What changes, who it affects, and a site-owner checklist.

User-agent strings are easy to fake. Here is how to verify which AI bots really read your site, and how AI bot traffic analytics show it without grep.

Crawl on miss, explained: how Lyrenth serves every page from its index, whether cached or freshly indexed, and when a re-crawl happens before serving.

A custom LangChain web loader that reads pages as clean AIDocuments instead of raw HTML: about 30 lines of Python, with real token numbers.

What web scraping infrastructure cost actually looks like over 12 months: fetch workers, browser pools, engineer time, and the shared-index alternative.

Run an AI readability website check with Lyrenth's readiness score: 0 to 10, the mean of per-page audits. What it measures and how to raise it.

LLM tool use for web reading, end to end: one tool schema for OpenAI and Anthropic plus a 30-line Python handler that returns clean AIDocument Markdown.

What is the token count of a web page for an LLM? We measured five famous pages: raw HTML vs AIDocument tokens, with real per-read costs.

What an AI-readable web index is, how it differs from scraping and from a classic search index, and why one crawl should serve every machine reader.

A five-minute quickstart: drop one MCP block into your assistant and it reads any URL as a clean AIDocument. Covers read_url, read_urls, and check_usage.

Humans browse the web through layout and pixels; AI agents read it as text, structure, and provenance. That difference inverts how an index should be built.

Raw HTML burns your context window on nav, scripts, and boilerplate. Here is how to feed web pages to an LLM as clean AIDocuments, with real token numbers.

Who reads your site now, what a well-behaved AI-index bot looks like, how robots.txt and llms.txt apply, and how to verify your domain with Lyrenth for free.

An AIDocument is one stable JSON shape for any web page: Markdown body, title, description, structure, and measured economics. Here is how it works.

Fetch a React or SPA site and you get a hollow div, not content. Here is why JavaScript sites return empty HTML, and what real rendering takes at index scale.