Machine-buyable storefront files

Public sample11 files · 10 named companies · 66 sealed reads

These files are written over in place. Some checkout manifests do declare a version, point back at earlier dated copies that still answer, and the protocol behind them keeps a public dated release log. None of that tells you the day a particular shop started serving its file, and that is the thing this feed records. We save a copy of all seven files from all 276 companies every day. Every row below is a file that was provably not there on one named day and provably there on the next day we read.

10 of those 11 files, on 9 companies, were still there on our newest read on 22 Aug 2026. 8 of the 10 are agent instructions and 2 are checkout manifests. One went the other way and is the row worth reading twice.

The three worth reading twice

roguefitness.com is the only file that came down. A checkout manifest was there on 28 and 29 July and gone on 30 July. It has answered not-found on every one of the 20 days we have read it since, so this is a file that was taken down and left down, not a fetch that failed. It is the only disappearance in the whole window and we do not print one until it has stayed gone.

on-running.com’s server never once said not-found. It answered 200 for /llms.txt on every day we could read it, and on the first 43 of those days it sent a web page rather than the file. The real file appeared on 28 Jul 2026. dillards.com did the same thing for two days: not-found for weeks, then 200 with a web page on 28 and 29 July, then the real file on 30 Jul 2026. Anything that only reads the status code would have called on-running.com’s file present since June. Only the saved body tells you which day the real one arrived.

bowflex.com and chubbiesshorts.com sit either side of a hole in our own reading. We have no read at all for 18, 19 and 20 August, so all we can honestly say is that those three files went up somewhere between 17 and 21 August. We give you both dates and let you see the gap rather than picking a day.

The size of the panel, and the honest count

We ask 276 companies for the same seven files every day and have kept every answer since 11 Jun 2026. That is 66 sealed days and 127,512 saved reads, with exactly 1,932 reads on every one of those days and no half-finished day in the set. On our newest read, 22 Aug 2026, 202 companies served a real robots.txt, 92 served agent instructions at /llms.txt, and 67 served a checkout manifest at /.well-known/ucp. Not one served an agent card, at either of the two addresses those live at, and not one served either of the two tool-server files, on any of the 66 days.

Counted by company rather than by file: 100 of the 276 served at least one of the six files an automated buyer looks for. 98 served none of them. For 71 of those 98 every one of the six came back a plain not-found. The other 27 answered 200 at least once with something that was not the file — still not the file, but not a not-found either, and we say which it was rather than rounding it up. The remaining 78 we could not fully read, and 63 of those gave us nothing readable on any of the six. Those three groups are kept apart on every page in this feed, and each one is named and broken down on what this feed covers.

Doing this yourself

You can fetch any of these seven files from any company yourself in a second. What you cannot fetch is yesterday’s. Checkout manifests are a partial exception: some declare a version, some point back at earlier dated copies, and the protocol keeps a dated release log. None of that tells you the day a particular shop started serving its file — that only exists if somebody was already asking every day before it happened.

The other half of the work is telling a real file from a server that says 200 and means nothing. That is why the honest count above is smaller than the number of 200s, and it is the part that quietly breaks anything built on status codes alone.

The pages under this one

• The day each company opened a doorAll 11 files that appeared, with both dates, what the server said the day before, and whether it is still there.
• Companies serving agent instructionsEvery company with a real /llms.txt on our newest read, plus the day it appeared and every rewrite since.
• Companies serving a checkout manifestEvery company with a real /.well-known/ucp, the version it declares, and what it says an agent may do.
• Servers that say 200 and mean nothingThe named companies whose servers answer 200 for files they do not have, and how we tell the difference.
• Companies a robot cannot buy fromThe companies where all six files are provably absent, kept apart from the ones we could not read.
• Companies we cannot readWho refuses our reader, why, and how long they have been shut to us. Never counted as a missing file.
• What this feed coversThe panel, the seven addresses, the days we missed, and what all 127,512 reads produced.

What you get

• Every company in your list that started or stopped serving one of the seven filesCompany, file, both dates, and what the server said the day before.
• The saved body behind any row, on requestSo you can see it really was the file, not a 200 with a web page in it.
• Days we could not read are named, not filled inA gap in our reading is shown as a gap. We never date a change inside one.
• Cancel any month by emailNo account to close, no notice period.

How it works

1. You buy below, or you email us first with the companies you care about, or ask for the whole panel of 276.
2. If you emailed, we tell you which of them we already read and since when, then send the same checkout link in that thread.
3. A person emails you the changes file, and names anything we could not read.

What this page cannot tell you