llms.txt Is Where the Real Pricing Is: The File Written for Machines Is Sometimes the Honest One

Buffer charges less per channel as you add channels. Everyone knows that. What almost nobody has seen is the actual table — the four volume bands and the per-channel rate inside each one — because on 19 September 2026 it was not on the pricing page. It was sitting in a plain markdown file at buffer.com/pricing.md, one URL away, formatted for something that is not you.

That is the strange new fact about buying software in 2026: the version of the page written for machines is sometimes more complete than the version written for customers. Occasionally it also disagrees with it.

What llms.txt actually is

We fetched the specification at llmstxt.org on 19 September 2026. It describes:

"A /llms.txt markdown file to provide LLM-friendly content"

placed at a site’s root to help agents use the site. The stated reasoning is that "Agents are best served by concise, expert-level information gathered in a single, accessible location." The file can live at the root (/llms.txt) or at a subpath such as /docs/llms.txt, with each file covering the URLs beneath its path. It is meant to be a curated index with links, not a dump of the whole site.

The second half of the proposal is the part that matters for price-checking. It recommends that pages also offer clean markdown versions at the same URL — either by appending .md to the filename, or by replacing the extension with .md. For paths without a filename, append index.md.

Which is exactly why buffer.com/pricing.md exists, and exactly why you can try that trick on any vendor you are evaluating tonight. It costs nothing. Half the time nothing is there. The other half is where this gets interesting.

The file that was more complete than the page

Here is what buffer.com/pricing.md contained on 19 September 2026, under a heading for per-channel rates on monthly billing:

The same file carries a worked example — five channels at $30 a month on Essentials, $60 on Team — which lets you check your reading of the bands against the vendor’s own arithmetic before you trust it.

Now look at the middle two rows, because this is the thing no comparison article has ever printed: between 11 and 50 channels, Essentials and Team cost exactly the same per channel. The entire Team premium is collected on your first ten channels and nowhere else. At fifty channels the two plans are separated by a fixed amount, not a growing one.

Sort those two plans by their headline starting price and you will rank them wrongly for anyone running more than ten channels. The number that fixes it was in a file for robots.

This is the whole argument for the practice in one example. The pricing page is a conversion surface: it wants a clean card and a button. The markdown file has no conversion job, so nothing gets simplified out of it. If you are comparing tools on a per-account basis — the discipline we walked through in fixing the unit before comparing schedulers — the bands are the only thing that lets you compute your actual bill.

The file that disagreed with the page

Buffer’s case is a file being more complete. The sharper case is a file being different.

On 19 September 2026 we fetched both blotato.com/llms.txt and blotato.com/pricing. Three things came out of the comparison.

One: they disagree about voice. The llms.txt states that credits "are spent only on AI image and AI video generation. Scheduling, publishing, API calls, ElevenLabs voiceovers, and the Viral AI Coach do not consume credits." The pricing page, the same day, states that "Credits power AI generation: images, videos, and voice." Those cannot both be operationally true. For anyone planning around voiceover volume, that is not a nuance — it is the difference between voice being free and voice being your main credit expense.

Two: the machine file answers a question the page does not. The llms.txt says "Credits roll over month to month." The pricing page does not address rollover either way. Rollover versus monthly reset changes how you should buy — and the widely repeated "credits reset monthly" framing had no source in any first-party file we could open today. That belief should be demoted to unverified, not repeated.

Three: one spec exists only in the machine file. The connected-account counts appear in llms.txt for all three tiers — Starter 20, Creator 40, Agency 100 — while our fetch of the pricing page surfaced the first two and not the third. If the account ceiling is the number your whole decision turns on, and it is the one that most often is, you would have had to open the robot file to find it.

A four-step check, before you put a card in

None of this requires tooling. It is four browser tabs and about five minutes, and it is the highest-yield due diligence available on a SaaS purchase right now.

1. Try the machine files. Take the vendor’s domain and try /llms.txt, then the pricing URL with .md appended. Also try /llms-full.txt, which some sites publish as the expanded version. Note which ones exist — that alone tells you something about how the company operates.
2. Find the number your decision turns on. Not the monthly price. The ceiling: accounts, channels, seats, posts per day. Look for it in both places. If it appears in only one, that is the number to confirm in writing before you buy.
3. Diff the two versions on anything metered. Credits, generations, minutes, rollover, what counts against what. This is where the files disagree most, because metering rules are edited more often than prices and the two documents are maintained on different schedules.
4. Send the contradiction to support and keep the reply. One email, both quotes, one question: which is current? You get a written answer to hold them to, and the speed and specificity of the response tells you more about the vendor than any review site will.

It is worth being fair to the vendors here. A contradiction between a marketing page and a markdown file usually is not deception — it is two documents maintained by different people at different times, which is the same reason a pricing card and a comparison table on one page can disagree, and the same reason an expired promo can still be live months later. But the reason for the gap does not change what it costs you. You pay the number on the invoice, not the number you read.

The direction of travel is clear enough: these files are being written because AI assistants are now a real channel through which people arrive at a purchase decision, and a vendor that wants to be quoted accurately has to publish something quotable. We made the same argument from the other side in pricing pages written for AI agents. Our own position is unglamorous and deliberate: what NoobClaw costs lives on the site and in the app, and we do not publish plan numbers inside articles precisely because articles go stale and invoices do not. Do the four-step check on us too. If the two sources ever disagree, that is a fair thing to ask us about.

For a worked example of the same discipline applied to two specific vendors, see Blotato vs Buffer, and for the prior question of whether the tool is even solving your bottleneck, Buffer alternatives beyond scheduling.

FAQ

What is llms.txt in plain terms?

A markdown file a site publishes at its root — /llms.txt — to give AI agents a concise, curated index of what the site contains and where the detail lives. The specification at llmstxt.org describes it as providing "LLM-friendly content", on the reasoning that agents are best served by concise, expert-level information in one accessible location. It also proposes clean markdown versions of individual pages, which is why pricing.md exists on some sites.

Is llms.txt useful for SEO?

It is not a ranking file and nobody should sell it to you as one. What it plausibly affects is accuracy of citation: if an assistant can read a clean, unambiguous statement of your pricing or specs, it is more likely to repeat that statement correctly. Treat it as a quotability measure rather than a ranking measure, and judge it by whether what comes back about you is right.

Which should I trust when llms.txt and the pricing page disagree?

Neither, until the vendor tells you. Both are first-party, both are current, and there is no rule that says the newer-looking one is right. Plan against the more conservative of the two numbers, put the contradiction to support in writing, and keep the reply. The disagreement is not a problem with your research — it is the most valuable thing your research found.