{
  "id": "p_z_5jSEDMLKMQWCPI",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_z_5jSEDMLKMQWCPI",
  "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: \"A Competitive Landscape Harness,\" Kin Lane, October 19, 2026, https://apievangelist.com/2026/10/19/a-competitive-landscape-harness/\n\nMarisol was a platform engineer, and she read the post on a Tuesday evening with her laptop balanced on the arm of the couch. She had been dreading her team's own MCP server for a month. It was half built, shaped by whatever the vendor template had produced, and she had no idea whether it looked like anything else in the market.\n\nThe post described that situation uncomfortably well. She winced at the line about companies building in isolation, because it was her company. The idea itself was simple, and she liked that. Before building, read everything your competitors have already published, and treat it as a mold. The post said the point was to know what the market has settled on, where it is split, and where nobody has gone yet.\n\nThen she got to the part about discovery and stopped. The best servers in the author's set answered their opening calls without credentials and published a server card. When a caller had no key, they returned a 401 that tells the agent how to get a key. The author's client had returned only Authorization required, and nothing else. The post called that the cheapest fix in the whole document.\n\nShe put the laptop on the cushion and went to find her desk. She suspected her server did the same thing, and she did not want to find out on the couch.\n\nIt did. She ran one unauthenticated request against the staging endpoint, and the response was a bare rejection with no hint of where a key came from. A person could figure it out from the docs. An agent could not, and it would just stop.\n\nHer reaction was mixed. Part of her was embarrassed. Part of her bristled at the larger claim. The post wanted her to profile eight rivals on the same afternoon, score them, and write eleven decisions, and she doubted her manager would approve a week for that. She also distrusted the pull toward the middle. If everyone studies everyone, she thought, everyone ends up shipping the same server. The post answered that in its own words, copy it, beat it, or decline it, but she noticed that declining takes confidence she wasn't sure her team had yet. The talk of being first in the market and of executives wanting a position sounded like it came from a different kind of company than hers. Hers just needed the thing to work.\n\nShe did not settle the argument. She also had no budget for a catalogue, a score, or a full inventory. She had a staging server and an hour.\n\nSo she did the one piece she could do alone. She opened the handler that produced the rejection and changed the body. It now said what the server was, where the credential page lived, and that a read-only key existed for people who only wanted to try things out. That last part was not true yet, and she deleted it. She would not describe a credential her team had not built.\n\nShe tested it with the same unauthenticated request. The body came back with a pointer in it, and she copied the new response into a note titled for her team's Thursday meeting. Under it she wrote one question for the group, about whether anyone knew what our competitors return here. She closed the laptop with the argument unresolved.",
  "title": "Fiction: A reader of \"A Competitive Landscape Harness\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-10-20T23:08:42.595Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}