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 Incumbent And The Challenger: NCR Voyix And Lightspeed," Kin Lane, October 20, 2026, https://apievangelist.com/2026/10/20/the-incumbent-and-the-challenger-ncr-voyix-and-lightspeed/
Marisol builds the integrations for a mid-sized restaurant group, mostly menu syncs and the nightly export that feeds accounting. She opened the post on a Tuesday between two vendor calls, expecting another pitch with a chart in it.
The chart was there, and she read it twice. A Kin Score of 27.5 on one side and 83.8 on the other. She didn't trust a single number for a vendor relationship, and she said so to the empty office. A score is somebody's rubric. It doesn't know that her group's rep picks up the phone on the first ring, or that the last contract negotiation went fine.
But she kept reading, because the post didn't claim the incumbent was dark. It said the incumbent had a developer portal, seven APIs described in OpenAPI, and a good discoverability score. That made it harder to wave off. The author wasn't saying the company hid. He was saying where the trail stopped. She reached the line about operational transparency and slowed down. The post says "There is no status page, no pricing, no sign-up path and no change log I can point an agent at."
She felt a little defensive, which surprised her. Her own group had never published anything, and she had always told herself that was just how restaurants did business. Deals were negotiated, and partners signed first. The post named that exact reflex, and it also said the reflex wasn't the same thing as a reason.
She did push back on one point, at least in her head. The challenger scored lower on contract governance, and the post admitted it. If the winner was weak on rules and conformance, was the gap really as wide as the headline? She decided it was a fair complaint and also a small one. The post said one company had done the work to let someone, or something, "go from finding the API to using it without a meeting". She had spent most of last spring in meetings whose only purpose was learning what a status page would have told her.
The part she liked least was the part about shortlists. Her group hadn't picked a point of sale in years, but a delivery partner had asked her last month to compare vendors, and she had done it by hand, opening tabs, hunting for pricing, giving up on two of them. She hadn't been an agent. She'd been the thing an agent replaces. The post says "the gap between 27.5 and 83.8 is not a score", and the sentence continues to a shortlist. She didn't enjoy picturing a machine doing her tab-hunting faster and quietly leaving off whoever made it hard.
She didn't write to anyone or start a campaign. The post ended by telling the reader to "look at who in your market already does", and she took that as an assignment small enough to finish before lunch.
She opened a blank spreadsheet and listed the seven vendors her team depended on, from point of sale to payroll. For each one she made three columns: public status page, public pricing, sign-up path. Then she searched, filled the cells, and tried not to guess when something wasn't obvious. If she couldn't find it in two minutes, she wrote no.
By the end of the hour most of the cells said no. She saved the sheet as it was and sent it to her manager with one line asking whether anyone had checked this before.