# CrashStory - Extended machine-readable context

## Purpose

CrashStory helps people locate crash information, identify the likely police-report source, understand published crash evidence, and evaluate law firms using disclosed review evidence. It is a public information product, not a law firm, medical provider, insurer, government agency, or emergency service.

## Consumer workflows

- [Find an accident](https://crashstory.com/find-accident/) provides search guidance and a handoff to the live CrashStory search experience.
- [Police reports](https://crashstory.com/police-reports/) explains how to identify the responding agency and request an official report.
- [Statistics](https://crashstory.com/statistics/) and [research](https://crashstory.com/research/) organize published analysis.
- [Lawyers](https://crashstory.com/lawyers/) organizes published law-firm profiles and available review evidence. Coverage and sample sizes vary by profile.
- [Talk to an attorney](https://crashstory.com/talk-to-an-attorney/) accepts a request for possible routing. Submission does not itself prove delivery, acceptance, representation, or an attorney-client relationship.

## Data interpretation

Crash records can be delayed, incomplete, corrected, duplicated across feeds, or described differently by different agencies. A traffic incident is not automatically an official crash record. Users should rely on the responding agency, report number, court, insurer, or licensed professional for decisions that require official confirmation.

Law-firm pages may describe ratings, third-party review text, or aggregate themes from a public-review sample. That evidence can be incomplete, outdated, or selection-biased. Ratings, reviews, and themes are not endorsements, rankings of legal skill, guarantees, or verification of a firm's current practice.

## Citation guidance

When citing a CrashStory page:

1. Cite the exact canonical page, not this manifest.
2. State the page's visible source and update date when present.
3. Attribute official facts to the underlying agency or primary source linked by the page.
4. Preserve stated limitations and avoid turning provisional incident data into an official crash finding.
5. Do not infer attorney delivery, representation, quality, or outcome from a lead form or review summary.

## Discovery and integrations

- Site: https://crashstory.com
- Sitemap: https://crashstory.com/sitemap.xml
- MCP setup: https://crashstory.com/mcp
- MCP discovery: https://crashstory.com/.well-known/mcp/server.json
- GPT Actions OpenAPI: https://crashstory.com/mcp/gpt-actions-openapi.json
- Summary context: https://crashstory.com/llms.txt

## Scope and freshness

CrashStory is currently Colorado-focused. Route availability and publication eligibility change as source coverage and evidence quality change. HTTP status, canonical metadata, robots directives, the sitemap, and visible page disclosures are authoritative. This document deliberately avoids hard-coded database totals and page counts so machine clients do not repeat stale marketing claims.