A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Insurance: The Shape Of The Answer Is Behind A Login," Kin Lane, October 23, 2026, https://apievangelist.com/2026/10/23/insurance-the-shape-of-the-answer/
Marisol works as a claims systems analyst at a regional carrier. She read the post on a Friday afternoon, between two tickets about a batch job that kept rejecting first notices of loss. She expected a vendor pitch. What she got was an argument that the hard part had moved.
The opening made her sit up. The post says the problem shifts from getting valid JSON to getting people to agree on the shape. Her team had spent a month on the first problem and never talked about the second. Their model produced tidy objects every time. The objects just weren't quite the claim her core system wanted, and nobody could say why the reserve on one test claim differed from the reserve on the same claim run the next day. The post's line about the answer being "probably not" when someone asks whether you would get the same number again felt uncomfortably like her own standup notes.
She was less comfortable with what came next. The post says ACORD's landing pages are public and then states flatly, "The landing pages are public. The schemas are not." Marisol's company holds a membership. She had never opened the portal herself, because a colleague in architecture handled it. Reading that sentence, she realized she had been treating the standard as folklore: something people referenced in meetings and she had never read. She wasn't sure whether to feel defensive on behalf of the standards body or annoyed on behalf of everyone outside the login. She felt both, and left it there.
She also pushed back a little. The author wants ACORD to publish open JSON Schema, and she could think of reasons an organization that depends on membership might not. The post never says why ACORD works this way, and she noticed it doesn't try to. Still, that made the point stick rather than weaken it. Her team was one of the carriers the post describes, each writing its own claim schema and hoping.
The part she reread was about the placeholder. The author admits the claim request schema in the catalog has six fields: policyId, lossDate, lossDescription, lossLocation, claimant and estimatedLossAmount. It is, in the author's words, "a placeholder for the shape, not the shape." Marisol counted her own team's claim schema against it. Hers had thirty-one fields. She suspected most were improvised, and she couldn't say which ones.
She liked the 1Fort detail best, a setting to "use ACORD form tables to generate questions instead of LLM." She laughed, then stopped laughing. Somebody had decided that for that question the standard should beat the model. Nobody on her team had made that decision, because nobody had written it down.
She didn't open a project or draft a proposal. She opened a blank spreadsheet and typed the six field names from the post in one column. Next to them she put the matching fields from her team's schema, and she marked the ones that had no code list behind them. Then she sent her colleague in architecture a short message asking whether she could be added to the ACORD portal login, so she could read the real claim object herself before Monday's review.