{
  "id": "p_bLuWhxDfiNacJV7S",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_bLuWhxDfiNacJV7S",
  "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: \"Three Hundred Eighty-Nine Agent Cards Are Live, And We Are Not Counting Ours,\" Kin Lane, October 20, 2026, https://apievangelist.com/2026/10/20/three-hundred-eighty-nine-agent-cards-are-live-and-we-are-not-counting-ours/\n\nMarisol read the post on a Tuesday afternoon between two deploy reviews. She is a platform engineer at a mid-size logistics company, and her first thought was whether her company was one of the ones being counted.\n\nThe numbers came fast. The catalog tracked 487 agent cards and re-probed every one. 389 were live, 62 were flavored, 27 were gone, and 7 were not agent cards at all. She liked that someone had checked instead of assuming. Most lists she saw never admitted that 27 entries had simply vanished.\n\nThe section on declaration made her slow down. The post says \"A card on your own domain is a declaration\". She agreed with the logic. Nobody else can put a file on your domain. But she also thought a file is cheap. A card describing what an agent can do takes an afternoon to write, and it proves nothing about whether the agent works. She wrote that objection in her notes. Then she read on and saw the post had already half-answered it: registry listings stay report-only because anyone can list anyone, and cards on shared hosting were held back because the domain proves nothing about authorship. The rule was narrow, and she could see it was not trying to be clever. She still thought it measured willingness more than quality. She decided to leave that disagreement standing.\n\nThe part that stuck with her was about the cards the authors did not count. They host cards themselves for thirteen companies, and they held all of those out. The post says, \"Crediting a provider for a card we wrote would be crediting our own work.\" She had expected a scoreboard to inflate itself a little. Seeing it decline to was oddly reassuring, and also uncomfortable, because it meant nobody was going to fill in her company's gap for her.\n\nThen the line about the frontier. The post says \"the highest-scoring API companies in the cohort mostly don’t publish a card yet\". Her company had a decent API, good docs, and a changelog people actually read. It had no card. By the post's own reading she was in the established camp, waiting for someone to measure the difference. She did not enjoy being a data point in a pattern.\n\nShe checked the dates. The first snapshot was October 15 and the fourth lands November 2. When that happens, \"most of the 122 undeclared providers in this cohort move to declared\". That gave her about two weeks, which was enough time to do something small and not enough to do something grand.\n\nShe did not open a project or call a meeting. She opened a branch in the docs repository and started a draft card, with a name, a plain description of what the shipment-tracking agent does, and how to reach it. Where the post said conformance matters, she left a note to herself to validate it against the spec before anything went near the real domain. She stopped before publishing and posted the branch link in her team's channel with one sentence asking who should own the file once it was live.\n\nThen she closed the tab and went back to the deploy review.",
  "title": "Fiction: A reader of \"Three Hundred Eighty-Nine Agent Cards Are Live, And We Are Not Counting Ours\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-10-20T23:08:28.452Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}