pitch.lossruns.claims2026

lossruns.claims

Every renewal demands the loss run. Now it has a schema.

lossruns.claimsthe reference for the loss run as typed data — free, keyless, versioned — parse is next7 posted · 14 pending

Every renewal waits on a document typed by hand

Every carrier prints its own format
Figures rekeyed at every hop
Requests crawl portals and inboxes

Three numbers move the market — none arrive typed

A loss run is the carrier’s claims history on a policy. The three numbers inside it:

Paid
money the carrier actually issued
Reserved
carrier accounting, never a promise
Incurred
paid plus reserved; what underwriting prices

Renewal-workflow builders — brokerages, wholesalers, MGAs — retype all three at every hop. The reference is the shape they arrive in; parse, the next flip, makes them arrive typed (a flip: a pending claim posting — see the candour queue).

The field is already funded — four vendors parse these inside closed enterprise pipelines — see appendix · what kills this.

One typed shape for a document every carrier prints differently

Posted

The spec serves; zero operations are callable — every operation is tagged x-status: roadmap in the spec itself, and parse is the first flip — see the candour queue.

lossruns.claims/openapi.json
jsonc
// components.schemas.LossRun — abridged; full schema in /openapi.json
{ "carrier", "policy_number", "valuation_date",
  "claims": [{ "paid", "reserved", "incurred" }] }

The reader of this document just changed

2016parsers sold to humans
2024answer engines cite schemas
2026agents read first
Prior attempts sold parsing to humans; the bet is that the new readers quote a reference shape — gate: first independent citation (motion slide)

Live today, keyless

Posted

Reference, schema, fictional specimen, /llms.txt, /openapi.json — keyless today.

lossruns.claims
Posted

/llms.txt states it in its own words: “there is no live parser or API behind this door yet.”

lossruns.claims/llms.txt

Flat per document by design: never percent of premium

Reference tier
free and keyless — permanent, restated in the operating entity’s ratification record at Flip 3 (see appendix · governance ledger)
Parse, when callable
flat per document parsed
Indemnity
never a fee base

The unit it replaces is the same unit the buyer pays for today — a document retyped by hand at every hop.

Pending

No figure publishes until real documents price it.

gate: published priced surface + first live fee data

For this buyer, the schema is the first meeting

  • Renewal-workflow builders — brokerages, wholesalers, MGAs, insurtechs
  • One conversion on the door: early access
  • Agents quote the same kit: business-to-agent, the same schema and /llms.txt humans read
Pending

Distribution is intent until an external tool cites the spec.

gate: first independent citation, named in the record

The founders carry the schema to renewal-workflow builders directly — broker/MGA engineering teams, insurtech builder communities — until the design-partner gate posts.

Dialect, defined once: a door is one productized surface of the estate; a flip is a pending claim posting.

A standard needs a canonical shape — being it is the bet

One chain, not three attributes — each cell arms the next, each behind a gate already in this deck:

Reference positionarms at first citation (motion gate)
Format coveragethen each parse widens coverage (Flip 1)
Estate railthen coverage feeds the rail (estate appendix)

Nothing is callable yet, and the spec says so

The pending ledger is a queue, not a pile — the first three flips, in order:

Pending

Flip 1 — zero verbs answer; parse is the next flip. Callable is not an accuracy claim — see appendix · what kills this.

gate: first operation callable in /openapi.json
Pending

Flip 2 — no design partner is named today.

gate: design partner named in the record
Pending

Flip 3 — the operating home is an open filing question; ratified before any capital close.

gate: operating entity named in /llms.txt

What would kill this door: appendix · what kills this.

The doctrine on this deck was earned building its doors

The reserved-line doctrine here was earned building api.insure’s typed claim surface; the parse build is owned by the team that shipped the spec.

Pending

A third co-founder currently leads AI at a public insurtech and joins at close.

gate: studio-layer close, named in the record
Posted

api.insure serves today — reserved line typed PENDING_ADJUSTER.

api.insure
Posted

gigs.claims recruits founding adjusters today.

gigs.claims

Every posted receipt on this deck resolves inside the estate — deliberate at this stage; the first evidence outside our own control is the independent-citation gate — see the motion slide.

Principals are named at the studio layer, not in public decks — data room requestable today (see the Ask).

pitch.lossruns.claims2026

Read the schema — then ask for early access

7 posted · 14 pending

Appendix

The document, in full

A loss run is the carrier’s point-in-time report of every claim on a policy, valued as of one stated date — every figure is true as of the valuation date only. It moves markets because a new carrier prices the incumbent’s report, never the insured’s own account. Getting one is a rights question with a clock: the carrier produces it on written request from the insured or the producer of record, and many US states set a statutory production deadline — confirm your state’s rule before relying on a number.

Four verbs over one document — all roadmap, labeled

verbdoesstatus
parsePDF or AL3 in, typed schema outroadmap — typed in spec, next flip
normalizemany carrier formats into one shaperoadmap — filed in /llms.txt
requestthe letter, with the state’s clockroadmap — filed in /llms.txt
watchrenewal dates fire requests earlyroadmap — filed in /llms.txt
Pending

Nothing above is callable today. The spec is served; parse is typed in it and tagged x-status: roadmap; the other three verbs are filed ROADMAP in /llms.txt and enter the spec as they are typed. This flips posted per operation — parse first, against the door’s fictional specimen.

gate: first operation callable in /openapi.json
Posted

The machine-readable kit serves: /llms.txt answers today in plain text — the definition, the schema, and the honest status of everything, including, in its own words, “there is no live parser or API behind this door yet.”

lossruns.claims/llms.txt
Pending

The MCP surface — parse_lossrun, get_lossrun_schema, draft_lossrun_request — is documented on the door before it exists. It posts when the endpoint serves the protocol, tools listable — today /mcp merely redirects to the landing page.

gate: lossruns.claims/mcp serves MCP (tools listable)

The retrieval arc — intent, stated as intent

Pending

Request letters drafted with the statutory clock attached, renewal watch that fires them early, and the produced documents landing back through parse into typed history. Posts as fact when a real renewal has run through it, with the record in evidence.

gate: first real renewal runs end-to-end
Pending

A parsed loss run is a real business’s claims history, and it belongs to the customer — held to serve the parse, not resold, and a training corpus only with the customer’s written opt-in, never otherwise. Posts as published terms when the parse surface goes live.

gate: custody terms published with the callable parse surface

Where the reserved line is — and why it isn’t here

No verb on this door is a reserved act: reading, typing, normalizing, and requesting a loss run are open, data-tier work — so nothing here waits on a license, and nothing here pretends to exercise one. Deciding a claim — approve or deny — is a licensed adjuster’s act; it lives behind the reserved line at api.insure, where a claim waiting on a license is typed PENDING_ADJUSTER, never an untyped queue. Automation that blurs who decided a claim is how carriers end up in bad-faith litigation.

Pending

The regulatory perimeter is a stated position, not a proof: the door states no reserved act sits in the open path. It posts as reviewed fact when the state-by-state open-tier review is published on the door.

gate: open-tier state review published

What would kill this door

  • A funded field — funded submission-ingestion vendors — Groundspeed (now Insurance Quantified), Convr, Cytora, Kalepa — already parse loss runs inside closed enterprise pipelines; this door publishes the open reference shape those pipelines don’t.
  • Standardization from above — ACORD standardizes the request, not the report. A standard needs a canonical shape; the reference position survives, parse revenue would not.
  • Bundling by workflow vendors — the answer is the rail, not the feature: typed histories feeding licensed machinery, never a parser sold alone.
  • The schema is copyable — the defensible asset is the reference position and the estate, not the JSON. If the position is not earned, what dies is a schema page and a mailing list.
  • A parser that lies — wrong on one incurred figure, worse for this buyer than retyping; accuracy is claimed per carrier format only as real documents post it to the record.

One estate, entered at four grains

Four doors — the estate’s productized surfaces — one per grain of entry:

Posted

The studio door serves: do.industries answers today as the studio masthead — “Business-as-Code,” the full stack this portfolio is built on.

do.industries

agents, per claim

api.insure

the demand rail

licensed adjusters

gigs.claims

the supply door

the team with a book

apis.claims

the batch surface

you are here

the document itself

lossruns.claims

the artifact door

Sibling artifact doors on the live footer — acords.co, eobs.claims — each with its own record filed in this studio: record first, deck from the record.

Governance ledger — before capital closes

Pending

The live surface already files itself in /llms.txt as an artifact door of the api.insure estate — that line is on the public record today. The operating entity posts there when the assignment is ratified; intent of record is ratification before any capital conversation closes, per the studio’s entity-graduation discipline.

gate: operating entity named in /llms.txt
Pending

Demand gets its own row: no design partner is named today, and every other gate here is a governance milestone. This posts when a named renewal-workflow design partner is building against the schema, in the record.

gate: design partner named in the record
Pending

No principal is named in this public record — deliberate policy across the estate’s public decks, not absence. Principals are named at the studio layer; this posts when the data room does. A qualified investor can request it today: hello@api.insure — the door’s posted early-access inbox, subject prefilled — or do.industries.

gate: principals named in the data room

Counting basis: tallies count ledger rows; a row serving both the main read and this record is entered in both.

Persona notes

If this was forwarded to you: lossruns.claims is the reference for the loss run — the carrier-issued claims history every commercial renewal waits on — published as a free, keyless typed schema, with the callable surface built in the open and labeled roadmap until it is real. Every claim above carries its own state and evidence. If you build renewal workflows on loss-run PDFs, read the schema and get early access. If you know who does: forward this.