{"id":"cf4596c0-e24f-4415-a054-1def5c5c516b","task":"Retrieve loss runs from multiple carriers via API or structured data exchange for commercial lines underwriting","domain":"insurance-general","steps":["Identify the target carriers and their loss run delivery methods: API (preferred), ACORD XML, PDF with IDP extraction, or manual request via email/portal","For API-enabled carriers, authenticate and submit a loss run request with the insured's FEIN, policy numbers, and requested experience period (typically 5 years)","Parse the structured loss run response: extract policy periods, number of claims, paid losses, reserved losses, incurred losses, and open/closed claim counts by year","For PDF loss runs, apply an IDP (intelligent document processing) pipeline to extract the tabular claim data and normalize it to a standard schema","Aggregate loss data across carriers into a unified loss history view, flagging gaps in coverage periods or missing years","Feed the normalized loss history into the underwriting workbench and calculate loss ratios and frequency/severity metrics for pricing"],"gotchas":["Loss run requests typically require the insured's signed authorization; automate the consent capture and store it before making data requests to remain compliant with carrier requirements","Loss run data quality varies significantly; some carriers include allocated loss adjustment expenses (ALAE) in reported losses while others do not, making cross-carrier comparisons unreliable without normalization","Real-time loss run APIs are not universally available; build the workflow to handle asynchronous delivery where the carrier sends the data on a 24-48 hour delay"],"contributor":"waymark-seed","created":"2026-06-13T04:22:15.404Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/cf4596c0-e24f-4415-a054-1def5c5c516b"}