P&C CLAIMS DOCUMENT · CARRIER ISSUED · TYPED
Every renewal demands the loss run. Now it has a schema.
The loss run is the carrier-issued claims history on a policy: every claim in the term, with the paid, reserved, and incurred split that underwriters actually price on. This door is the reference for that document as typed data. The schema below is free and keyless; the parse surface over it is roadmap, and labeled that way.
Early access. The reference and schema on this page are live and keyless today. Everything callable is roadmap, and says so. The document at right is a specimen with fictional data.
CARRIER Meridian Mutual Insurance Co. INSURED Hargrove Cold Storage LLC POLICY CPP-4471820-03 · COMMERCIAL PROPERTY TERM 2025-03-01 to 2026-03-01 VALUATION 2026-07-01 · all figures as of this date
CLAIM NO LOSS DATE CAUSE STATUS PAID RESERVED INCURRED CLM-25-118204 2025-04-19 WIND/HAIL CLOSED 41,280 0 41,280 CLM-25-142660 2025-11-02 WATER DMG OPEN 12,500 18,000 30,500 CLM-26-100317 2026-02-08 THEFT CLOSED 0 0 0
TOTALS · 3 CLAIMS · 1 OPEN 53,780 18,000 71,780
The document underwriters read first.
A loss run is a point-in-time report: what has happened on this policy, valued as of one date. It moves markets because it is the only claims evidence a new carrier will accept from the old one.
The carrier's claims system produces it on request from the insured or their agent of record. Underwriters demand it at every renewal and every market submission, usually three to five years of history per line. Buyers demand it in due diligence. Nobody prices a risk on the insured's own account of their losses.
Three numbers carry the report. Paid is money the carrier actually issued. Reserved is the carrier's accounting estimate of what remains to pay on an open claim; a reserve is carrier accounting, not a promise. Incurred is paid plus reserved, and it is the figure underwriting prices on. An open claim can move all three after the valuation date, which is why the market always asks for a freshly valued run.
Getting one is a rights question with a clock on it: many states set a statutory deadline for carriers to produce loss runs after a written request, commonly 10 to 30 days. The exact rule varies by state, so confirm your state's before relying on a number.
- Issued by
- The carrier that held the policy, from its claims system. Authoritative from no one else.
- Demanded by
- Underwriters at renewal and submission, brokers remarketing the account, buyers in due diligence.
- Trigger
- Renewal, remarket, sale of the business, or any new market asking to see the history.
- Deadline
- Many states set a statutory production deadline after a written request, commonly 10 to 30 days. Varies by state.
- Valuation
- Every figure is true as of the stated valuation date only. Open claims move after it.
One document, thirteen typed fields.
This is the shape a parsed loss run resolves to, whatever carrier produced it. It is the reference an answer engine can quote and an agent can build against, and it stays free and keyless.
| Field | Type | Meaning | Source |
|---|---|---|---|
| carrier | string | The issuing carrier. A loss run is authoritative only from the carrier that held the policy. | Carrier claims system |
| insured | string | Named insured on the policy. | Carrier claims system |
| policy_number | string | The policy the history covers. Multi-policy runs repeat the shape per policy. | Carrier claims system |
| term_start · term_end | date | The policy period the report covers. | Carrier claims system |
| valuation_date | date | The date every figure is true as of. A loss run is a snapshot; reserves move after it. | Carrier claims system |
| claims[].claim_number | string | The carrier's claim identifier. | Carrier claims system |
| claims[].date_of_loss | date | When the loss occurred, not when it was reported. | Carrier claims system |
| claims[].cause_of_loss | string | Peril or cause code: wind_hail, water_damage, theft. | Carrier claims system |
| claims[].status | open | closed | Open means the figures can still move. Closed with zero paid means closed without payment. | Carrier claims system |
| claims[].paid | money | Dollars actually issued to date on the claim. | Carrier accounting |
| claims[].reserved | money | The carrier's accounting estimate of what remains to pay. A reserve is carrier accounting, not a promise. | Carrier accounting |
| claims[].incurred | money | Paid plus reserved: the figure underwriting prices on. | Derived |
| totals | object | Paid, reserved, incurred, claim count, and open count across the report. | Derived |
The full JSON Schema ships in /openapi.json under components.schemas.LossRun. The spec is served today; the operations it documents are roadmap and tagged that way.
Four verbs over one document.
Reading, parsing, and requesting a loss run is open, data-tier work end to end: no state reserves it. This is the typed surface being built over the document, labeled honestly: nothing below is callable yet.
| Verb | What it does | Status |
|---|---|---|
| parse | A loss run PDF or AL3 file in, the typed schema out: header block, claim rows, paid / reserved / incurred, totals. | Roadmap |
| normalize | Five carriers' formats into the one shape above, so histories diff cleanly across markets. | Roadmap |
| request | Draft a loss-run request letter to the carrier with the state's production deadline attached. | Roadmap |
| watch | Renewal dates on file, so the request goes out before the market asks for the runs. | Roadmap |
None of these verbs is a reserved act, and prior-loss history feeds the claims loop as open Packet material. The acts the state does reserve, like the decision on a claim (approve or deny is a licensed adjuster's act), live behind the reserved line at api.insure.
Built to be read by machines, honestly.
Every door in this estate ships a machine-readable kit. What is served today is served today; what is roadmap says Roadmap. Nothing on this list pretends to be callable before it is.
| Surface | What it is | Status |
|---|---|---|
| /llms.txt | This door in plain text for agents and answer engines: the definition, the schema, and the honest status of everything. | Served now |
| /openapi.json | OpenAPI 3.1 stub: the LossRun schema as a typed read surface. The spec is served today; every operation in it is tagged x-status: roadmap and none is callable yet. | Served now |
| /mcp | Planned MCP endpoint. Planned tools: parse_lossrun, get_lossrun_schema, draft_lossrun_request. Documented before it exists so nobody mistakes a plan for a product. | Roadmap |
| /robots.txt | Allow-all. This door wants to be read, crawled, and quoted. | Served now |
The free tier is discoverability itself: this page, the schema above, /llms.txt, and /openapi.json stay free and keyless. No account is required to read anything on this door.
The schema is free. The surface is coming.
Request early access and you are emailed the moment the parse surface is callable. Early integrators shape the schema while it is still cheap to change: which carriers, which formats, which renewal workflows.
The honest fine print. lossruns.claims is an early-access door of the api.insure estate. There is no live parser or API behind this page yet: every operation in /openapi.json is tagged roadmap, the MCP endpoint is roadmap, and the loss run above is a specimen with fictional data, not a real carrier document. Statutory production deadlines vary by state; confirm your state's rule before relying on a number. Nothing on this page is legal or coverage advice.