STANDARD INSURANCE FORMS · DATA FIELDS · TYPED
The industry runs on standard forms. Your agent reads typed fields.
The forms published by ACORD are how claims open and coverage gets proven: the loss notice, the certificate of insurance. This door is an independent reference to the data fields those forms carry, as one typed model an agent can fill, check, and read. The field model below is free and keyless; the parse surface over it is roadmap, and labeled that way.
Early access. The reference and field model on this page are live and keyless today; everything callable is roadmap, and says so. The document at right is an original illustrative rendering with fictional data, not an ACORD form. Independent site; not affiliated with ACORD Corporation.
RECORD FIRST NOTICE OF LOSS · PROPERTY REPORTED 2026-06-11 · 18:02 CT REPORTED BY Bright Harbor Insurance Agency CARRIER Meridian Mutual Insurance Co. POLICY HO3-2214087-01 · HOMEOWNERS TERM 2025-10-01 to 2026-10-01 INSURED D. Okafor CONTACT (940) 555-0164 · d.okafor@example.com
DATE OF LOSS 2026-06-11 · 16:40 CT TYPE OF LOSS WIND_HAIL LOCATION 2114 Pecan Hollow Dr, Denton, TX 76205 DESCRIPTION Hail impact to roof decking and two skylights; water staining in the upstairs hallway ceiling. No injuries. AUTHORITIES None contacted REMARKS Insured requests contact by email.
One family of forms, one recurring field model.
The most-searched document names in insurance are form numbers: the certificate of insurance, and the property, auto, and liability loss notices. Different paper, one recurring set of data fields.
ACORD Corporation is the standards body whose published forms the industry files claims and proves coverage on; carriers, agencies, and management systems license them through ACORD. When an agent says "send the 25" or "file the loss notice", they mean a specific, standardized set of fields, and it is the fields, not the paper, that an agent-first system needs typed.
The wave 1 focus of this door is the loss notice: the first notice of loss (FNOL) an agent, broker, or insured files to open a claim. Its fields are the intake record of the entire claims loop. Who reported, under which policy, what happened, where, when, and who to contact: every downstream deadline and every adjuster assignment keys off this record.
The specimen above is an original, dossier-styled rendering of the data fields commonly found on a loss notice. It is illustrative, its values are fictional, and it is not a reproduction of any ACORD form.
- Published by
- ACORD Corporation, the insurance industry's standards body. This site is independent and not affiliated with ACORD.
- Filled by
- Agents, brokers, and insureds at first notice of loss; agencies, when a certificate is requested.
- Sent to
- The carrier's claim intake, where it opens the claim file and starts the FNOL clocks.
- The family
- Property, auto, and general liability loss notices (ACORD 1, 2, 3); the certificate of insurance (ACORD 25); named nominatively.
- This specimen
- An original illustrative layout of common loss-notice fields with fictional values. Not an ACORD form.
The loss notice, as fourteen typed fields.
This is the field model a filed notice resolves to, whichever standard form carried 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 |
|---|---|---|---|
| form | property | auto | liability | Which loss-notice family the record maps to. | Agent intake |
| reported_at | datetime | When the notice was filed. FNOL clocks start here. | Agent intake |
| reported_by | string | Who filed it: the insured, the agent of record, a broker. | Agent intake |
| carrier | string | Carrier the notice is addressed to. | Policy record |
| policy_number | string | Policy the loss is claimed under. | Policy record |
| term_start · term_end | date | Policy period. A loss date outside the term is the first validation an agent runs. | Policy record |
| named_insured | string | Named insured on the policy. | Policy record |
| contact | object | Name, phone, and email for the person the adjuster should reach. | Agent intake |
| date_of_loss · time_of_loss | datetime | When the loss happened, as precisely as known. | Insured's report |
| loss_type | string | Peril: wind_hail, fire, water, collision, liability. | Insured's report |
| loss_location | string | Where it happened. | Insured's report |
| description | text | Plain-language account of the loss, injuries noted. | Insured's report |
| authorities_contacted | string | Police or fire department and report number, if any. | Insured's report |
| remarks | text | Anything material that does not fit a field. | Agent intake |
The full JSON Schema ships in /openapi.json under components.schemas.LossNotice. The spec is served today; the operations it documents are roadmap and tagged that way.
Four verbs over the intake record.
Filling, checking, and delivering a notice is open intake work: no state reserves it. This is the typed surface being built over the field model, labeled honestly: nothing below is callable yet.
| Verb | What it does | Status |
|---|---|---|
| parse | A completed loss notice in, typed FNOL fields out: insured, policy, loss date, peril, location, description. | Roadmap |
| prefill | Draft a loss notice from an intake conversation, every required field present before it goes anywhere. | Roadmap |
| validate | Flag missing or inconsistent fields, like a loss date outside the policy term, before submission. | Roadmap |
| route | Deliver the finished notice to the right carrier intake for the line of business. | Roadmap |
None of these verbs is a reserved act. The claim a loss notice opens is decided by a licensed adjuster under delegated authority; that reserved act lives 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 field model, and the honest status of everything. | Served now |
| /openapi.json | OpenAPI 3.1 stub: the LossNotice 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_loss_notice, get_loss_notice_schema, prefill_loss_notice. 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.
Read the fields now. Call them later.
Request early access and you are emailed the moment the loss-notice surface is callable. Early integrators shape the field model while it is still cheap to change: which forms, which carriers' intakes, which validations.
The honest fine print. acords.co 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 document above is a specimen with fictional data. acords.co is an independent reference and is not affiliated with, endorsed by, or licensed by ACORD Corporation; ACORD and the form numbers are ACORD Corporation's marks, used nominatively to identify the industry-standard forms, which are ACORD's copyrighted publications. The specimen is an original illustrative rendering of common loss-notice data fields, not a reproduction of any ACORD form. Nothing on this page is legal or coverage advice.