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 Technical Side Translated. The Business Side Did Not.," Kin Lane, November 10, 2026, https://apievangelist.com/2026/11/10/the-technical-side-translated-the-business-side-did-not/
Marisol maintains the integration platform at a mid-size company that sells routing software. She opened the post on a Tuesday between two meetings, expecting a scoreboard she could skim and forward. She skimmed the table first. Her own team would have done well in the top half. They publish an OpenAPI contract, they keep auth docs current, and they ship an MCP server that she personally built over a long weekend.
The paragraph after the table slowed her down. The post says an agent can read the contract and call the API, but what it can't do is find out "what it is allowed to do, what it will cost, what happens to the data, or what it is agreeing to without a human opening a browser." She read the sentence twice, then opened her company's terms of service in a browser. It was a long page, and nobody on her team had read it in a long time.
Then she looked at the numbers again. Of 33,045 providers, 40.9% publish terms of service, and 0.4% publish anything an agent can read about what it is agreeing to. Her company was in the 40.9% and not in the 0.4%. That felt less like a gap than like a locked door she had walked past for years without noticing.
She was not entirely persuaded. The post admits that some of its pairings are the author's own judgment, and she thought the pairing of pricing pages with agentic commerce was a stretch. A pricing page can be perfectly good and still have no business being a checkout for software. She also felt uneasy about the part where the catalog generates artifacts on a provider's behalf. The post is open about it. It says part of the agent-ready web right now is "our work and not the provider's," and that derived artifacts are labeled as derived. But she could picture a machine-readable summary of a contract drifting from the contract. If a summary said her company allowed caching and the lawyers meant something narrower, whose words would an agent trust? The post didn't answer that for her, and she wasn't sure it could.
Still, she kept returning to the list of clauses it says an agent actually needs: permitted use, AI and training use, caching and storage, redistribution, attribution, jurisdiction, and termination notice. She could not say where in her company those seven answers lived. Some were in the terms. Some were probably in a contract template. One or two were just things the account managers knew.
She didn't try to fix that. She didn't draft a schema or propose a project, and she didn't write to anyone outside the company. She made a new file in the docs repo, next to the OpenAPI contract, and typed the seven clause names as headings. Under each one she pasted the sentence from the current terms that seemed to cover it, or the word unknown where nothing did.
By the end of the afternoon, four of the seven said unknown. She attached the file to a message for the legal team, asking them only to correct her reading, and sent it before the next meeting started.