A spec-compliant llms.txt at the root of your published docs (e.g. docs.your-api.com/llms.txt).
llms.txt tool
Generate an llms.txt file from your OpenAPI spec.
Bloom can generate a spec-compliant llms.txt from your OpenAPI input — endpoints grouped, schemas linked, examples included, per-page Markdown emitted alongside (in preview alongside the SDK pipeline). Free for 30 days, no credit card required.
Completely free for 30 days. No credit card required.
01Details
What the generator produces
Per-page canonical Markdown so each link in llms.txt resolves to a clean .md file agents can read without HTML chrome.
An Optional section grouping examples, changelog, and migration notes that agents can skip when context is tight.
All of this regenerates on every spec push — no separate llms.txt build step to maintain.
02Outputs
Why generate llms.txt from OpenAPI
OpenAPI already contains the structure agents need: endpoints, parameters, schemas, examples, auth.
Manually written llms.txt files drift the moment your API changes. Generating from the spec keeps it accurate by default.
Bloom's generator preserves operationIds and tag groupings so the file mirrors how developers think about the API.
03Details
Three ways to ship an llms.txt with Bloom
Upload your OpenAPI spec at signup. Bloom generates llms.txt as part of the docs preview before you publish.
Connect a GitHub repo and Bloom rebuilds llms.txt on every spec change.
Run the migration scanner first if you already host docs elsewhere — it reports what to keep, redirect, and replace.
04Checks
llms.txt checker — validate before you ship
Bloom's preview surfaces the generated file in the dashboard with the parsed structure, link count, and any orphaned references.
You can also paste your existing file into the dashboard to compare what Bloom would have generated against what you currently ship.
Outside of Bloom: the spec at llmstxt.org documents validation rules — H1 required, blockquote optional, Markdown link format strict.