---
title: "Reading & Delivery"
description: "How content leaves Byline and reaches its readers — the typed client SDK, the server-function transport surface, future HTTP transports, markdown and llms.txt for agents, an MCP server, and the caching strategy that ties them together."
canonical: "https://bylinecms.app/docs/reading-and-delivery"
locale: "en"
collection: "docs"
updated: "2026-06-21T04:10:50.020Z"
---

# Reading & Delivery

How content leaves Byline and reaches its readers — the typed client SDK, the server-function transport surface, future HTTP transports, markdown and llms.txt for agents, an MCP server, and the caching strategy that ties them together.

Modeling content is only half the job; the other half is getting it out to the things that read it — browsers, other services, and increasingly language models and agents. This section covers every way content leaves Byline and how to serve it efficiently.

- [Client SDK](/docs/client-sdk) — `@byline/client`, the typed, DSL-style API for querying and writing documents from outside the admin UI.
- [Routing & API](/docs/routing-api) — the current transport surface (TanStack Start server functions) and the boundary where a stable HTTP API becomes worthwhile.
- [Transports](/docs/transports) — how Byline layers framework-agnostic logic under host-specific bindings so the same operations can be exposed over different transports.
- [Markdown Export](/docs/markdown-export) — one-way Lexical-to-markdown rendering, the `.md` URL surface, and `llms.txt` for agent consumers.
- [MCP Server](/docs/mcp) — exposing Byline content to AI agents over the Model Context Protocol.
- [Caching](/docs/caching) — CDN edge caching, invalidation strategies, and the optional in-memory data cache.