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 APIs.io Pricing Page Now Shows How APIs Charge," Kin Lane, November 3, 2026, https://apievangelist.com/2026/11/03/the-apis-io-pricing-page-now-shows-how-apis-charge/
Priya works as a product manager for an API at a company she'd rather not name in a story. She opened the post on her phone while waiting for a build to finish, expecting a link roundup. Instead she got a pricing table, and she read the whole thing standing up.
The first thing she noticed was the count. The page had read 7,203 providers, and 2,892 of them didn't state a pricing model. Her stomach did a small drop, because she knew which side of that line her own company probably sat on. Our pricing page has a slider and a button, she thought. Sales likes the button.
She read on and found the button named in the post, right in the last section. An agent choosing between two providers can't read a pricing page with a slider and a "contact us" button. Priya bristled at that. Negotiated pricing wasn't laziness where she worked. Enterprise customers wanted custom terms, and the post itself put negotiated at 19 percent of the providers that state a model, with 838 of them. Almost one in five providers wants you to talk to sales. She had been told, in meetings, that this was a feature. Seeing it as a share on a table made it look less like a strategy and more like a habit.
Still, she wasn't ready to be moved all the way. The author admitted that a per seat label now needed a seat-like word in the plan rows, and that it was word matching, so it would still get some wrong. Priya liked the honesty and distrusted the method in equal parts. If a tool decides what her company charges by scanning for words, what happens when her plan names are cute? She had a tier called Studio, and no seat in sight.
The line that stayed with her was a different one. The author wrote that he would rather show less than show a number that doesn't mean anything, and so credits got a count and no price. She had spent a week the previous quarter arguing over what one of her own credits was worth, so that landed hard. Every vendor defines a credit differently. She hadn't thought of that as a problem for anyone but her own finance team.
Then came the closing idea, which she copied into her notes. The page measures not just what APIs cost, but how much of that is written down where a machine can find it. She didn't have to agree that machines should be the buyers. She only had to admit that some of her future customers would be sending one.
The build finished. Priya didn't forward the post to her boss, and she didn't announce a pricing overhaul. She opened a blank document and typed out her three plans in plain rows: monthly price, included requests, and what each extra thousand requests cost. Studio went in as a row with a number next to it. The negotiated enterprise plan got a row too, with a starting price she'd have to ask permission to publish.
She saved the file as a draft for Monday's pricing meeting, and went back to her build.