A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Agents Will Not Look For An SDK Generator, They Will Look For A Problem To Solve," Kin Lane, November 6, 2026, https://apievangelist.com/2026/11/06/agents-will-not-look-for-an-sdk-generator-they-will-look-for-a-problem-to-solve/
Marisol was a platform engineer at a logistics company, and she read the post on her phone while the build ran. She had an agent that wrote throwaway clients for her team. She had never asked what it was remembering when it wrote them.
The first line stopped her. The author said the client stack had not collapsed, it had gone dark. She thought about the last client her agent wrote, three functions and a fetch wrapper. It had been deleted with the context window, and nobody could say which version of the provider's contract it was written against. She felt a small, specific discomfort. She had been calling that convenience.
Then came the reply from Lubos at Hey API, and the author's concession that the tool already existed. Marisol was partly annoyed. She had assumed this was a problem and the post was about to sell her a fix. It was more honest than that. The author had gone and tried it. He started from a business problem, rotating the API keys an application uses to talk to Twilio, and ended at a contract with five operations, of which the task needed three: list, create, delete. One command later he had a typed client with nothing extra in it. She read the config twice. An include list of three operation keys looked almost too plain to matter.
She liked the line that the dark layer has a light switch. She did not like the next section, and she said so to the empty meeting room. The author wanted APIs.io to be where an agent meets the generator, but he also wrote that an agent will not go looking for one. Her own agent did not browse catalogs. It would do whatever its prompt and tools made easiest, and she doubted a page of machine-readable pointers would change that. The post admitted as much. It called discovery unsolved and said agent conventions were still moving.
The economics paragraph bothered her more, because it had no answer in it. If a catalog sends an agent to a generator and the client ends up in production, who gets paid? The author said he would rather work that out in the open than alone. She respected that. It also meant that part of the argument was an invitation and not yet a plan.
Still, she could not wave the main point away. Her team's key rotation was a wiki page and a calendar reminder. The problem was exactly the kind the author described, a business problem with no mention of SDKs anywhere in it.
The build finished. She did not open a ticket or message anyone. She made an empty scratch folder, outside any repo, and copied the shape of the config from the post. It had the include list for those three operations and the same three plugins. She would run it against the Twilio contract the post named and see whether the output compiled for her too. She would commit nothing and tell no one until she had read what came out.