# Content

Once an agent has a page, can it read it cheaply and correctly?

An agent pays for every token it reads and most never run JavaScript. This layer is about whether the words are in the response, whether a cheaper machine-readable form is offered, and whether the text is labelled well enough to be interpreted rather than guessed at.

| Technology | What it is | Adoption | Status |
|---|---|---|---|
| [Server-side rendering](/docs/content/ssr) | Whether the content exists before JavaScript runs. Most agents never run it. | Web baseline, ► flat | scored |
| [Markdown twin](/docs/content/markdown-twin) | A clean low-token markdown version of the page for agents. | Early production, ▲ rising | scored |
| [JSON-LD](/docs/content/json-ld) | Structured data describing what this page is about. | Web baseline, ► flat | scored |
| [Language and encoding](/docs/content/lang-encoding) | Declared language and charset, so text is interpreted correctly. | Web baseline, ► flat | scored |