{
  "id": "p_a12lbMNh3BGcp2Ma",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_a12lbMNh3BGcp2Ma",
  "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: \"Two Hundred Nine API Companies And Seven Hundred Seventy-Five Enterprises Hire In Different Worlds,\" Kin Lane, October 28, 2026, https://apievangelist.com/2026/10/28/two-hundred-nine-api-companies-and-seven-hundred-seventy-five-enterprises-hire-in-different-worlds/\n\nMarisol runs developer relations for a small company that sells a shipping-rates API. She read the post on a Wednesday night with the laptop on the arm of the couch, expecting a dull table of percentages. Her own docs, she had to admit, were written for a Zapier-and-Kubernetes sort of person. She had never questioned that.\n\nShe started with the numbers. The post says the pull read 343,299 job postings from 984 companies, 775 of them in the Fortune 1000 and 209 of them API providers. Then it said Zapier was named by 18.7 percent of the providers and 2.3 percent of the enterprises. She felt a small, pleased recognition. That was her world: SOC 2 reports, a Vercel front end, the Kubernetes jobs her engineers complained about.\n\nThe enterprise table made her sit up. Three out of four Fortune 1000 companies named Outlook, and almost half named Word. She laughed, then stopped, because her biggest prospect was exactly that kind of company, and she had never once thought about what their people opened in the morning.\n\nShe also pushed back. The post was careful about its own limits, and she gave it credit for that. It said to read every gap as \"a direction, not a measurement\", since 209 companies is a small sample. But she wondered whether the comparison was a little unfair. Of course a company that employs everyone posts for people who use Word. Hiring intent is not buying power, and the post said so itself. She felt a flicker of irritation at the tidy bridge metaphor, two worlds and one span, because her real customers were messier than either column. One of them ran a cloud she had never heard named in a job ad. The post covered that too, noting that plenty of large companies run on a cloud they never mention in a posting. That made her trust the table less and the shrug more.\n\nStill, the last paragraph stuck. The post said that if a developer experience only makes sense from inside the first world, \"you are making the second world translate\". She thought about her quickstart. It assumed a command line and an API key pasted into an environment variable. It said nothing about gateways, identity providers or security reviews, the things the post said a big customer would bring with it. She had always treated that as their problem.\n\nShe didn't have a plan, and she knew a plan was beyond a Wednesday night. She didn't want to rebuild the docs on the strength of one quarter of data, and the post itself said the Q4 read would come on November 20 and that nothing yet showed a gap widening or closing.\n\nSo she did something small. She opened her onboarding checklist and added a single line at the bottom: ask each new enterprise contact which gateway, identity provider and automation tool their team will route us through. Then she saved the file, closed the laptop, and wrote herself a reminder to read the Q4 numbers when they came.",
  "title": "Fiction: A reader of \"Two Hundred Nine API Companies And Seven Hundred Seventy-Five Enterprises Hire In Different Worlds\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-10-28T13:13:07.488Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}