{
  "id": "p_v8Q52LBFEof0qi_p",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_v8Q52LBFEof0qi_p",
  "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: \"Make The Case For API Investment With Facts Instead Of Feelings,\" Kin Lane, November 3, 2026, https://apievangelist.com/2026/11/03/make-the-case-for-api-investment-with-facts-instead-of-feelings/\n\nMarisol ran the platform team for a mid-sized freight company. She read the post on Tuesday morning, between a failed build and a meeting about the agent pilot. The pilot had a budget line and a slide with a robot on it. Her own list had been sitting in a document called backlog for two years.\n\nShe liked the opening, because it described her situation. Money was going to AI, and the foundations she kept raising couldn't get a hearing next to anything with an agent in the title. She nodded at the claim that a neutral fact base moves the discussion from emotion to evidence, and then felt a small sting. Every time she had argued for API cleanup, it had been emotion. She had been frustrated, and her director had heard frustration.\n\nThe table made her slow down. HubSpot at 93.2 on the Kin Score and 54 on Agent Readiness. SendGrid at 85.9 and 45. Elastic at 77.6 and 30. These were companies she thought of as the standard to copy, and the post said being very good at the traditional work does not automatically carry over. Cloudflare, at 80.6 and 73, showed the gap could be narrowed. She read that row twice, because it meant the gap was something you could close, not just something you had.\n\nShe didn't trust it all the way. A score built from public artifacts felt like a stranger grading her homework without seeing her team's work. She thought about the internal tooling her engineers had built, the careful retry logic nobody outside the company would ever see. The post anticipated her. It said the score sees what you publish and cannot see your internal engineering. She was still uncomfortable, and being told to expect that didn't dissolve it. The line about the author being sure an early version was wrong, and then finding it was not, made her wince. She suspected she would react the same way.\n\nShe also felt a flicker of resistance to the whole idea of scoring. Numbers could be gamed, and she'd watched teams polish what a dashboard measured while ignoring what mattered. But the advice itself was practical. Do not ask for an API quality budget, the post said. Say the agent initiative depends on idempotency, error semantics and machine-readable auth, and show which of those you have. That was a different conversation from the one she had been losing. She wouldn't be asking leadership to care about her backlog. She'd be asking whether the thing they had already funded could work.\n\nShe didn't open a ticket or draft a business case. She didn't have the nerve to pull her own company's reading in front of anyone yet. She opened a blank page and wrote three headings: idempotency, error semantics, auth. Under each she listed, in plain sentences, what her public developer docs actually said today, as an outsider would find it. Two of the three were thin, and she wrote that down without softening it.\n\nThen she moved the page into the folder for the pilot meeting, so it would be there if someone asked what the agents needed.",
  "title": "Fiction: A reader of \"Make The Case For API Investment With Facts Instead Of Feelings\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-03T14:59:57.246Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}