{
  "id": "p_jb1KS7_Jd2PQ4u3H",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_jb1KS7_Jd2PQ4u3H",
  "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: \"Regulation Writes The API,\" Kin Lane, October 27, 2026, https://apievangelist.com/2026/10/27/regulation-writes-the-api/\n\nPriya, a product manager at a small lender, read the post on Tuesday night with a cold cup of tea and the compliance tracker open in another window. She worked on the team that shipped the product data endpoints, so she read the section about banks and energy retailers the way you read a school report with your name on it.\n\nThe first thing she noticed was the count. Of 227 companies, 31 carried a Consumer Data Right signal, 22 of them in banking and finance. She felt a flicker of pride, because she knew what it cost to make those contracts match everyone else's. Then she reached the line about AMP, whose only published contract is its CDR product data, and her pride went sour. It could have been her own company's page.\n\nShe didn't like the next part, and she told the empty room so. The post says plainly that this is not a complaint, and she half believed it. But the sentence that stayed with her was the one saying that when the regulator writes the API, the API stops where the regulation stops. Her team hadn't stopped there because they were timid. They had stopped because the deadline was real, the budget was fixed, and nobody had asked for anything else. A sandbox is a hosting bill and a person who answers questions. Pricing for developer access is a meeting she had never managed to schedule.\n\nShe read the list of what was missing: no sandbox, no MCP server, no agent card. Then the blunt line, \"The CDR contract is the API program.\" She bristled. It was unfair, she thought, to measure a team by what it publishes when the law only asked for one thing. Then she opened the repository and scrolled through what her company actually published. Her stomach dropped a little. It was one standard contract and nothing else.\n\nShe wasn't won over by the optimistic reading either. The post argues that a shared shape is exactly what an agent needs, and she agreed. But she distrusted the neat conclusion that mandates produce programmable markets fastest. They had produced a narrow one. She underlined, in her head, \"Product data, not products.\" That was the honest summary of what her team had built, and she hated how little she could say against it.\n\nThe post's closing questions were aimed at a room in Melbourne she wouldn't be in. One asked what it would take to publish beyond the mandate, so the CDR becomes the floor of the API program instead of the whole of it. She had no answer ready, and she didn't pretend to have one.\n\nShe didn't draft a strategy. She opened a blank note and wrote two columns. In the left one she listed everything her company published today, which took one line. In the right one she wrote the cheapest thing she could think of that wasn't required by anyone, and it turned out to be a plain page describing who to email about the API. She saved the note and attached it to the next planning meeting, under a heading that said only that it was a question. Then she closed the laptop and drank the cold tea.",
  "title": "Fiction: A reader of \"Regulation Writes The API\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-10-27T13:08:22.695Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}