A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "The Business Terms Of An API, Made Machine-Readable," Kin Lane, November 13, 2026, https://apievangelist.com/2026/11/13/the-business-terms-of-an-api-made-machine-readable/
Marisol, a procurement analyst at a freight company, opened the post on a Friday afternoon because a developer had dropped the link in a channel with no comment. She expected a standards pitch. She read it with a pen in her hand, the way she reads contracts.
The opening problem was one she already knew. Her job was to read what the post called "a legal page written for a lawyer to read once". She did it for every vendor, usually in the week before a purchase order, and she had never once been asked to do it on behalf of software that would decide for itself. That sentence landed uncomfortably. Her team had been talking about letting an agent pick a geocoding service in the middle of a routing task, and nobody had asked what the agent would be allowed to do with the answers.
She went down the table of seven layers slowly. Terms of Service covered 243 providers. Eligibility covered 205. AI Preferences covered 159. Then Deprecation: 3. She sat back. Notice before something gets shut off was the question that had cost her team a weekend two years ago, and here it was, nearly empty. The author called this a finding rather than a gap, and she half agreed. It confirmed what she suspected. But she also thought three was a number that made the whole section easy to wave off, and she said so out loud to nobody. Only three providers had a deprecation policy the author could read and record, and she found she trusted the page more for admitting it.
The part she argued with was the model. A model transcribes the page into rows, and that made her wary. She read on and found the safeguard: each row carries text that is checked word for word against the fetched page, and rows that fail are dropped. Fine. But then the author wrote that the stance is a judgment, and she underlined it: "The stance is still a judgment about what the quote means, and a judgment can be wrong." She did not feel reassured. She felt something closer to respect, and some irritation that the honest version was also the more work for her. The quote travels with the stance so a person can check it. That meant checking was her job now, not the site's.
She nearly closed the tab. Instead she thought about the agent her team wanted, and about the difference between finding an API that can do the job and finding one it is allowed to use. The post's phrasing, not hers, but it was the right way to put it.
So she did one small thing. She picked a single vendor her team already paid for, opened the Terms of Service page, and found its row. The row quoted a sentence about caching. She did not take the stance on trust. She opened the vendor's own terms in another window, found the sentence, and read the paragraph around it to see whether conditional really meant conditional.
Then she added one line to the intake checklist she kept for new vendors: a question asking how much notice they give before they break something, with room to paste the sentence that answers it. She sent the checklist to no one. It was only a line, and she saved the file.