A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "If You Depend On OpenAPI Please Become a Member," Kin Lane, October 23, 2026, https://apievangelist.com/2026/10/23/if-you-depend-on-openapi-please-become-a-member/
Marisol maintained the API platform at a company that sold scheduling software. Nobody had given the job a better name. She opened the post on a Friday afternoon while her build ran, expecting a spec update.
It started with money. The first lines were "I’m going to ask for money, so I’ll get straight to it." She almost closed the tab. Asks for money in technical blogs usually meant a pitch, and she had a ticket queue waiting.
She kept reading because the post was about the thing her whole week ran on. She knew OpenAPI as the document her linter, her docs generator and her client libraries all read. She had never thought of it as something with a budget. The post said the Initiative now maintained three specifications, and she had only heard of two. Overlays she could place at once, because her team patched vendor descriptions they didn't own, and they did it with a script held together by hope. The post said Overlay 1.2 shipped in September. She hadn't known there was a 1.2.
Then she hit the lists, and her stomach tightened a little. The post named companies that had never been members, companies that had left, and companies that published large descriptions. It said it was working through them one by one. She scanned all three for her employer and didn't find it, which should have been a relief. It wasn't. Her company was too small to be named, but it fit the description exactly.
She also disliked the format. A public list felt like a hallway where people got looked at. The author said he wasn't trying to shame anyone, and she believed that, but a list does what it does whatever the author intends. She noted that he had put his own company on the former-members list, which made it harder to be annoyed.
What stayed with her was the plainest sentence in the post: "Most companies that depend on OpenAPI have simply never been asked." That was her company. In six years she hadn't once heard anyone say that the specification they built on had to be paid for by someone. They had treated it like weather.
She didn't have the authority to join anything. Budgets belonged to her director, who thought of specifications as free in the way roads are free. Marisol wasn't sure the argument would land. She wasn't even sure she could make it well. The post allowed for that: it said engineers could go to the weekly calls, and that time mattered as much as money.
Her build finished. She left it and opened a blank message to her director. She didn't write a case. She wrote three sentences: that the Initiative's membership was priced by company size, that her team's tooling read the specs it maintained, and that she wanted ten minutes to ask whether it was worth looking into. She pasted the link to the post and one more line, quoting nothing, just asking him to read the part about the lists.
She read the draft once, didn't soften it, and sent it. Then she bookmarked the community calendar for Monday.