{
  "id": "p_qQLF7A4m0K9UkEnS",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_qQLF7A4m0K9UkEnS",
  "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: \"What To Look For In A Vendor Before You Sign Or Renew,\" Kin Lane, November 13, 2026, https://apievangelist.com/2026/11/13/what-to-look-for-in-a-vendor-before-you-sign-or-renew/\n\nMarisol read the post on a Friday afternoon, with a renewal sitting in her queue. She was a procurement analyst at a logistics company, and the contract was for an SMS provider, one of those line items that nobody thinks about until it renews. Nobody on her team could say whether it was any good. They could only say it had never caused a fire.\n\nThe restaurant bathroom metaphor made her wince at first. It seemed a little glib for something with a six-figure signature at the end. But the point underneath it stuck: the public surface of a vendor is a clue to the part you cannot see. She had never looked at a vendor's changelog before signing anything. She had looked at the sales deck, and the sales deck was never going to show her the bathroom.\n\nShe found the SMS tag and saw it ranked 171 providers. Her vendor was somewhere in the middle. She noticed that her first instinct was to treat the number as a verdict, and the post had already warned her off that. It said a lower-scoring provider may have the routes, the price or the support you need. So she read the facet breakdown the way the post suggested, as a list of follow-up questions rather than a grade.\n\nThe agent readiness page was the one that bothered her. Her company had started letting software agents trigger shipment notifications, and she had never once asked what happened if one of them retried. She wrote the question down just as the post had it: what happens to a message when an agent retries a send. If the answer was that a customer got the same text twice, or five times, that was something she wanted to know before the signature, not after.\n\nShe also felt some discomfort, and she did not hide it from herself. The post admitted that vendors can be scored too low, that enterprise docs often sit behind a login, and that the public surface does not show everything. Her vendor was one of those. Walking into a renewal with a number from outside felt a bit like accusing someone from behind a window. She did not want to be the person who got a fact wrong in a negotiation.\n\nSo she kept the part she trusted. The line about a neutral document to bring to the table made sense to her, and so did the example of saying \"Your category’s leaders publish machine-readable rate limits and you do not\" instead of a vague wish for improvement. But she decided she would not quote a score at the vendor at all. The post itself said \"A good vendor conversation starts with the facts and ends with a better relationship\", and she had worked with this account manager for three years.\n\nHer one modest act was small. She opened the renewal notes and added two dated requests, to be sent before the call. The first asked for the vendor's uptime history. The second asked how an agent retry is handled, and whether they could show her in writing. She left the score out of it entirely.\n\nThen she closed the tab, and went to find out who on the engineering team would be able to read the answer.",
  "title": "Fiction: A reader of \"What To Look For In A Vendor Before You Sign Or Renew\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-13T12:16:40.619Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}