A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Where The Market Layer Of The Kin Score Stands," Kin Lane, October 21, 2026, https://apievangelist.com/2026/10/21/where-the-market-layer-of-the-kin-score-stands/
Marisol ran partnerships for a mid-sized freight software company. She read the post on a Wednesday, between a renewal call and a call that had been moved twice. She had opened it because a colleague forwarded the link with a single line asking whether this was about them.
She didn't know yet. The post was about markets, registers and positions, and she skimmed the first half for the word logistics. It never came up. What caught her was the section on rules, where one sentence stopped her: "A long list of logos earns nothing on its own."
She thought about the partner page she had spent most of a year on. It was a grid of forty-some logos, tidy and color-matched, and she had been proud of it. She read the sentence again and felt something close to defensiveness. Some of those logos were hard-won, and a few had taken three quarters of negotiation. Counting them as nothing seemed unfair.
Then she kept reading and saw the point was narrower than her reaction. The post didn't say the partnerships were worthless. It said a machine needed to be able to read them, and that a listing earns participation while a certification earns depth. Her page was a picture. Nothing on it was written in a form a program could follow.
She didn't like how that landed. She also didn't fully trust the framework. The author said plainly that the weights were a prototype, calibrated against his own read of each market, and she found that honest and unsettling in equal measure. A score built on one person's judgment still ranks real companies, even if the person admits it. She wrote a note to herself in the margin of her notebook: who decides what a good market read looks like? The post had an answer of sorts, which was to tell them if they have your market wrong, but she wasn't ready to find that comforting.
She was also irritated, in a small way, by the idea of undeclared. If a provider publishes nothing a machine can read, it reads undeclared. That seemed a harsh word for a company that simply hadn't gotten around to it. Then she noticed the post's own rule that gaps are attributed, and that it only blamed the provider for what was the provider's responsibility. Declaration was hers to make, and she hadn't made it.
She thought about the certifications her company held, which lived in a PDF in a shared drive, and about the integrations, which lived in her head and in a spreadsheet only she opened. If an agent, or a person using one, went looking for who this company worked with, there was nothing for them to find. That was a plain fact, and it was her fault, which she resented a little.
Near the end she found the line she kept coming back to: "publish your integrations, partnerships, and certifications somewhere a machine can read them." It didn't ask for a rebuild or a platform. It asked for somewhere.
She didn't have the authority to redesign the site, and she wasn't going to pretend the score had persuaded her of anything. But she could do one small thing before the day ended. She opened a blank text file and typed the name of each partner, what kind of relationship it was, and a link to where that relationship was documented. She stopped at twelve, the ones she could source without asking anyone. It wasn't the forty she wanted, but every line was something she could stand behind.
She saved the file and sent it to the engineer who owned the website, asking where something like this could live. Then she went back to her renewal call, only a few minutes late.