{
  "id": "p_mtfA9tiN6NawUvLp",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_mtfA9tiN6NawUvLp",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"Benchmark Your APIs Against Competitors You Did Not Know Were Looking,\" Kin Lane, November 9, 2026, https://apievangelist.com/2026/11/09/benchmark-your-apis-against-competitors-you-did-not-know-were-looking/\n\nMarisol was eating lunch at her desk when a colleague forwarded the post. She is a backend engineer at a small company building a new messaging service, and she had been told to design it quickly. She opened the link expecting a pitch.\n\nThe first paragraph made her uncomfortable. It described someone looking up their company at a table and finding that their APIs already had a score, one they had never heard of. She thought about her own team's work and realized she could not say whether anyone had ever scored it. The line that stuck was \"Your APIs are being read and compared whether or not you asked.\" She read it twice. She did not like it, and she did not think it was wrong.\n\nThen came the table. Sinch and Vonage, two SMS providers, sat at 71.5 and 71.3, which she would have called a tie. Underneath, the facets told a different story. One scored 80 on developer ergonomics and the other 91. One scored 56 on agent readiness and the other 41. Both scored 22 on contract governance. She noticed she was reading the table the way she reads a diff, looking for what changed. The author's point was that a headline number hides the shape underneath, and she had to admit that was true of nearly every dashboard she had ever been shown.\n\nShe did push back, privately. A score built from public artifacts cannot know how a company actually behaves when a customer is on the phone. The post seemed to know this. It said the score only sees what is public, and that a score says nothing about whether the product is better. Still, she bristled at the idea of her team's work being judged by a reader that never talked to anyone. An agent choosing a vendor for somebody would not care about her intentions, only what she had published. That was the uncomfortable part, and she decided it was also the useful part.\n\nShe noticed that the post asked for something small. It did not tell her to chase a ranking. It said to compare facet by facet, and ignore the composite for now. It also said that winning every facet is not the goal. That freed her a little. Her service was months from launch, and the post pointed out that designing in what category leaders already publish costs almost nothing, while retrofitting costs a lot. She had been dreading a backlog of cleanup. Maybe she could avoid it.\n\nShe did not sign up for anything or call a vendor. She also did not forward the post to her manager with a note about strategy, which she had considered for a moment and then dropped. Instead she opened the tag page for SMS, which the post said was free to read, and looked at the two leaders it named, Twilio at 91.6 and Telnyx at 86.1.\n\nIn a plain text file next to her design notes, she wrote down one thing each of them published that her draft did not yet plan to. She picked the single item that looked cheapest to build in from the start and added it to the task list for the first sprint. Then she closed the tab and went back to her sandwich.",
  "title": "Fiction: A reader of \"Benchmark Your APIs Against Competitors You Did Not Know Were Looking\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-09T14:39:02.623Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}