llms.txt examples

A good llms.txt example is short: one H1, a summary that states a limit, three to six sections and specific one-line descriptions. Each file below follows that pattern for a different kind of site. For the official reference example, see the llms.txt proposal at llmstxt.org; real-world files are discussed in the proposal’s GitHub repository.

What does a SaaS product’s llms.txt look like?

The job is to make the product understood quickly: what it does, who it is for, what it costs and how to integrate it.

llms.txt

# Cadence

> Scheduling API for healthcare providers. Handles appointment booking,
> reminders and cancellations. HIPAA-eligible, US and Canada only.

## Product
- [How Cadence works](https://example.com/product): Booking flow, reminder logic and calendar sync in one page.
- [Pricing](https://example.com/pricing): From USD 199/month for 5,000 bookings. Volume tiers above 50,000.
- [Security and compliance](https://example.com/security): HIPAA, SOC 2 Type II, data residency options.

## Developers
- [Quickstart](https://example.com/docs/quickstart): Authenticate and create a booking in under ten minutes.
- [API reference](https://example.com/docs/api): Every endpoint, parameter and error code.
- [Webhooks](https://example.com/docs/webhooks): Event types, retry behaviour, signature verification.

## Optional
- [Changelog](https://example.com/changelog): Release notes since 2023.

What it gets right: the summary states the constraint (US and Canada only) that stops a model recommending it to the wrong person, and pricing is a real number rather than “flexible plans”.

Documentation site

Documentation is the strongest case for this file. Link the section indexes, not every page.

llms.txt

# Lumen CLI Documentation

> Command-line tool for managing container deployments. Open source, MIT
> licensed. Current stable release is 4.2.

## Getting started
- [Installation](https://example.com/docs/install): macOS, Linux and Windows, via package manager or binary.
- [First deployment](https://example.com/docs/first-deploy): Deploy a sample app in about fifteen minutes.

## Reference
- [Command reference](https://example.com/docs/commands): All 34 commands with flags and examples.
- [Configuration file](https://example.com/docs/config): Every key in lumen.yaml, with defaults.
- [Environment variables](https://example.com/docs/env): Runtime variables and precedence rules.

## Guides
- [CI/CD integration](https://example.com/docs/ci): GitHub Actions, GitLab CI and CircleCI examples.
- [Troubleshooting](https://example.com/docs/troubleshooting): Common errors and what causes them.

## Optional
- [Migrating from v3](https://example.com/docs/migrate-v3): Breaking changes and upgrade path.
- [Architecture](https://example.com/docs/architecture): How the scheduler and agent communicate.

Under V2, a documentation section run separately from the main site can publish this file at /docs/llms.txt, where it covers everything below /docs/.

Online shop

Link categories, never individual products. A store with four thousand products still needs a file under ten kilobytes.

llms.txt

# Fern & Fold

> Independent stationery shop in Melbourne. Notebooks, fountain pens and
> paper goods. Ships within Australia and New Zealand.

## Shop
- [Notebooks](https://example.com/notebooks): 60 titles across A6 to A4, dot grid, lined and blank.
- [Fountain pens](https://example.com/pens): Entry-level to enthusiast, AUD 25 to AUD 480.
- [Inks](https://example.com/inks): 140 bottled inks, including 12 exclusive to us.

## Help
- [Shipping and delivery](https://example.com/shipping): Free over AUD 90. 2-5 business days domestic.
- [Returns](https://example.com/returns): 30 days, unused, we pay return postage on faulty goods.
- [Nib grinding service](https://example.com/nib-service): In-house nib work, AUD 60, 2-week turnaround.

## Optional
- [About the shop](https://example.com/about): Opened 2016, the team, our Brunswick storefront.

Agency or consultancy

llms.txt

# Harbourline

> B2B content strategy consultancy working with fintech and insurance
> companies. Team of nine, based in Dublin, projects across the EU and UK.

## Services
- [Content strategy](https://example.com/services/strategy): Audit, messaging framework and editorial plan. From EUR 18,000.
- [Editorial operations](https://example.com/services/editorial): Retained editing and publishing support, monthly.

## Work
- [Case studies](https://example.com/work): Eleven engagements with named clients and measured outcomes.

## Insight
- [Articles](https://example.com/articles): Roughly two pieces a month on B2B content in regulated industries.

## Optional
- [Team](https://example.com/team): Who we are and what we did before this.

Note that the case studies line describes the collection rather than listing eleven separate URLs. That is the right instinct for any archive.

Personal site or portfolio

llms.txt

# Ama Boateng

> Structural engineer and writer based in Manchester. I work on timber
> buildings and write about how they are put together.

## Writing
- [Essays](https://example.com/writing): Long-form pieces on timber engineering, 2019 to now.

## Work
- [Projects](https://example.com/projects): Selected structural projects with drawings and photographs.
- [Speaking](https://example.com/speaking): Past talks and how to invite me to one.

## Optional
- [CV](https://example.com/cv): Full professional history.

What do good examples have in common?

A summary that includes a limit or qualifier, descriptions containing real numbers, categories rather than exhaustive listings, and a short ## Optional section for background pages. None of them is long. If yours is growing past a hundred lines, the best practices guide explains what to cut.