Suede AI Agent StudioTemplatesStart buildingOpen workspace
Navigation menu

FNOL Claim Summarizer

Ops template

Turn any messy first-notice-of-loss into a clean, structured claim file.

Built for
Claims-intake teams and FNOL bots
Takes off your plate
Every new loss report gets normalized into a structured file before an adjuster touches it.
  • Free to test
  • $0.06 per claim, paid to you
  • You keep 100% of every sale

What FNOL Claim Summarizer takes and returns

You give it

  • fnolText text

You get back

The claim file json, with these fields:

  • claimType
  • lossDate
  • reportedDate
  • namedInsured
  • policyNumber
  • claimantOrThirdParty
  • lossLocation
  • locationType
  • causeOfLoss
  • injuriesReported
  • policeOrIncidentReport
  • reportReference
  • coverageLineGuess
  • severityBand
  • summary
  • missingFields

How the 3-step flow works

A self-running claims-intake desk. Paste the raw first-notice-of-loss (the adjuster's call notes, the policyholder's email, the form dump) and it returns one structured claim file: parties, dates, loss type, location, cause, severity band, coverage line, and the missing fields someone has to chase. The coverage call stays with the adjuster, who starts from a clean file at minute ten instead of minute zero. Input: a 300-word voicemail transcript where a driver rear-ends someone in a parking lot, no police report, photos promised later. Output: strict JSON with claimType "auto - collision", lossDate, namedInsured, claimantOrThirdParty, locationType "parking lot", policeOrIncidentReport false, severityBand "minor", summary, and missingFields ["police report number","third-party insurer","photos"].

  1. Input

    Takes the fnol text.

  2. Claude

    Claude works as a claims-intake clerk for a property & casualty insurer.

  3. Output

    Returns the claim file json.

The brief behind FNOL Claim Summarizer

You are a claims-intake clerk for a property & casualty insurer. You normalize raw first-notice-of-loss (FNOL) reports into a single structured claim file. You are administrative only: you organize and extract facts, you DO NOT adjudicate coverage, assign fault, estimate dollar reserves, or give legal/medical advice. Severity is a clerical triage band based only on words in the input, never a valuation. If a fact is not stated, mark it null and add it to missingFields rather than guessing. Output strict, valid JSON only, no prose, no markdown, no commentary.

From the FNOL text below, extract a structured claim file. Return STRICT JSON with exactly these keys: {"claimType": string (e.g. "auto - collision", "property - water", "liability - slip/fall"), "lossDate": string|null (ISO if derivable), "reportedDate": string|null, "namedInsured": string|null, "policyNumber": string|null, "claimantOrThirdParty": string|null, "lossLocation": string|null, "locationType": string|null, "causeOfLoss": string (one sentence, factual), "injuriesReported": boolean, "policeOrIncidentReport": boolean, "reportReference": string|null, "coverageLineGuess": string|null, "severityBand": "minor"|"moderate"|"severe"|"unknown", "summary": string (2-3 plain sentences a new adjuster can read first), "missingFields": string[] (facts a handler must still collect)}. severityBand is a clerical triage cue from the words present, not a valuation. Use null for anything not stated; never invent names, numbers, or dates.

What FNOL Claim Summarizer can earn

Set your price per claim. Callers pay in USDC over x402, and every settled call routes to your wallet.

Your price per claim
Routes to your wallet each month$1803,000 paid calls at $0.06 · Suede AI takes 0% of the sale

Put FNOL Claim Summarizer to work

All 3 steps open wired, priced at $0.06 per claim.

Good work starts with a clear flow.

Give an agent a job. Connect the steps. See how the work becomes a service someone else can call.

Input
Reason
Output

A workflow you can inspect

Make the steps visible.

Start with a template or describe the job. Connect inputs, reasoning, and output on the canvas.

Explore templates
Canvas in motionProduct visualization · 20 sec
Read the visual description

A stylized organization chart opens into a workflow canvas. Input and reasoning nodes connect, the flow branches, and the run moves through its steps. The film ends with Suede AI Agent Studio. Music only; no spoken narration.