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 Microsoft API Estate: 169 Surfaces, One Company, and the Work of Making It Coherent," Kin Lane, November 5, 2026, https://apievangelist.com/2026/11/05/the-microsoft-api-estate-169-surfaces-one-company-and-the-work-of-making-it-coherent/
Marisol read the post on a Thursday, between a failed deploy and a meeting she was avoiding. She is a platform engineer at a mid-sized freight software company, and she opened it expecting a scorecard she could dismiss.
The opening numbers were hard to dismiss. A hundred and sixty-nine provider profiles, ten waves, three retired. Then the part about Entra. She had a spreadsheet at work with a column called identity provider, and in it three of her own team's services still pointed at something called Azure AD. She knew it had been renamed. She had never once thought of the rename as something a machine would trip over.
She got to the line saying "Renames leave three names for one thing." and felt a small, irritated flinch, because she had been one of the three names. Last spring she had written a runbook that said Active Directory in the title and Entra in the body, and she had thought of that as being thorough.
Her first reaction was to argue. The author was scoring a company from outside, at scale, with a rubric he wrote himself. A gap between a Kin Score of 58.0 and an agent readiness of 27.1 sounded to her like a number built to produce a gap. She said as much to the empty meeting room, quietly. Nobody she knew was asking an agent to discover Microsoft's whole estate. People asked for one API and found it by searching.
But the post kept conceding her points before she could make them. Each rename, it said, was a sound product decision. None of it was criticism of the teams doing the work. She had come ready to defend them and found nothing to push against, which was oddly more uncomfortable.
The section on retirements stayed with her longest. Azure Notebooks shut down in 2020, and the only signal was prose on a page. She thought about her own company's deprecated endpoints, and about the banner on their docs site that said the v1 shipment API was going away. She had written that banner. It was a good banner. Then she read "An agent cannot read a retirement that only exists as a blog post." and she could not find a way to say her banner was different.
She did not agree with everything. The call for an estate-wide index seemed easy to ask for and slow to deliver, and she suspected that anyone who had worked inside a company that size would laugh at it. She said so in a note to herself and left it there.
What she did before lunch was small. She opened her team's internal API list, found the v1 shipment entry, and looked at the fields. There was a status, and there was no field for what replaced it. She added one, pointing at v3, and filled it in for that single entry. The other eleven stayed as they were. She wrote a line in the pull request description saying this was a trial, and asked a colleague to look at it Monday.
Then she went to the meeting she had been avoiding.