{
  "id": "p_ffpz2kfZxnKYNWIF",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_ffpz2kfZxnKYNWIF",
  "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: \"The Agent Hype is at Odds with Your API Foundation,\" Kin Lane, November 11, 2026, https://apievangelist.com/2026/11/11/the-agent-hype-is-at-odds-with-your-api-foundation/\n\nMarguerite read the post on her phone, standing in the kitchen with her coffee going cold. She was a platform engineer at a freight company, and on Monday her director had put an MCP server on the roadmap for the quarter. Nobody had said what it was for yet.\n\nShe was a little annoyed by the post before she finished it. The author scored roughly 25,000 API providers on two separate instruments and then told her the exciting thing she'd been asked to build was resting on something dull. She had heard that kind of sermon before. Governance had always been the thing people did after the launch party.\n\nStill, one sentence stayed with her: \"The finding is that readiness is a layer, and a layer does not rise above its foundation.\" She read it twice. She didn't like how plain it was.\n\nThe post named four dimensions that separate the agent-native band from everyone else: idempotency, error semantics an agent can branch on, auth and consent clarity, and rate-limit signaling. Marguerite knew her own estate well enough to feel her stomach drop. Their booking endpoint had no idempotency story. A retry meant a phone call to someone in operations. A human developer would have learned that quirk in a week and routed around it. An agent wouldn't know there was a quirk.\n\nShe pushed back, in her head at least. Her estate wasn't a catalog of strangers' APIs. She knew where the bodies were buried. A thin MCP layer could paper over the rough spots, with a few guardrails in the wrapper. But the post had anticipated her. Putting an MCP server on an ungoverned API did not move the readiness number, and it could hand agents \"a confident interface to an unreliable contract.\" That was exactly what her wrapper would be. She thought it was a little unfair that the author had never seen her wrapper, and then she admitted she hadn't written it yet, so she couldn't defend it.\n\nWhat she couldn't get past was the line \"Readiness is bounded by the least-governed contract in the path.\" She had been counting endpoints. The post said agents don't consume endpoints. They try to complete a capability, and the capability fails at the weakest contract in the chain.\n\nShe didn't think the post had everything right. The tone was too certain for her taste, and she wasn't going to cancel the roadmap item over a blog post. But the closing advice was cheap enough to try. It said to map your capabilities to the contracts behind them, score those contracts, and look for the weakest link.\n\nShe finished her coffee anyway, cold, and opened a blank note. She wrote one capability at the top, which was rebooking a missed pickup. Underneath she listed the four contracts that capability touched, in order. Next to each she wrote a single word, yes or no, for whether a failed call told the caller what to do next.\n\nIt took eleven minutes. Two of the four said no. She didn't fix anything or send anything to her director. She saved the note where she'd see it on Monday, and went to find her keys.",
  "title": "Fiction: A reader of \"The Agent Hype is at Odds with Your API Foundation\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-11T14:37:56.201Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}