Personal injury leads from public filings — not consumer inquiries
Personal injury leads, as most vendors sell them, are web-form inquiries resold to several firms at once. That is not what this page is about. Recordpipe delivers public-record signals: civil cases as they are filed, docket events as they post, and published incident and accident reports where the agency makes them public. It is the record itself, structured, delivered to your intake or marketing system on a cadence you choose.
The distinction matters. Public filings are a fixed-price feed built to your courts and case types, not a shared pool. And they carry the case number, the court, the parties as published, and the dates — so every lead is verifiable at the source before anyone picks up a phone.
Recordpipe builds and runs the pipeline: collection from the courts and agencies you specify, normalization to one schema, filtering and ranking by the AI analysis layer, and delivery by file, API, webhook, or dashboard. The $500 scoping maps what your target jurisdictions publish and returns a sample within 5 business days, so you know what a lead actually looks like before you commit.
Car accident leads and accident report leads, where the report is public
Car accident leads and accident report leads come with a hard constraint that honest vendors state up front: crash reports are restricted in many states, and personal information on them is protected by federal and state driver privacy law. Recordpipe does not deliver restricted reports, and does not deliver private contact data from any report. What it delivers is what agencies publish as public record — daily incident logs, crash summaries, and press blotters where those exist — plus the civil cases that follow when a crash becomes a lawsuit.
That second signal is often the better one for a firm. A filed motor vehicle negligence case names a plaintiff who has already decided to pursue a claim, an attorney of record or a pro se flag, a defendant, and a court. For firms handling co-counsel, referral, or defense work, that is the lead. For firms marketing to the not-yet-represented, the pro se flag is the filter.
Police report leads are scoped the same way: what is public in your jurisdictions, at what cadence, with what fields. Scoping tells you before you buy.
Mass tort leads, class action leads, and docket monitoring at scale
Mass tort leads and class action leads are docket work. A firm building a mass tort docket needs to see every case filed under a given cause of action, product, or defendant across state and federal courts, and it needs to see it as filings happen. The same is true for class action counsel tracking related actions, opt-outs, and transfers. Doing that by hand across many courts does not scale. A managed pipeline does.
Recordpipe collects civil filings from the courts you specify and tags each case by nature of suit, named defendants, product or subject where the docket text supports it, and attorney of record. The AI analysis layer clusters related cases, flags likely duplicates, and ranks new filings against the criteria your team sets — a specific defendant, a product name in the complaint, a venue.
Delivery as a webhook per new filing lets a firm's intake or co-counsel outreach run the same hour the case posts. A weekly file gives a litigation analytics team the full tape. Both come from the same pipeline, fixed-price.
Bankruptcy leads for attorneys and judgment recovery leads
Bankruptcy leads for attorneys and judgment recovery leads are the other public-record signals legal marketers ask for, and they behave differently. Bankruptcy filings are federal and comparatively uniform: chapter, debtor as published, filing date, trustee, attorney of record, and case status. Judgments are county-level and messy: a civil judgment entered in state court, its amount as stated, the creditor and debtor as published, and any recorded abstract or lien that follows.
Recordpipe runs both as structured feeds. For judgment recovery, the feed joins the judgment to recorded property interests and business registrations where the identifiers support it, and exposes match confidence so a recovery firm can set its own threshold. For bankruptcy, the feed can filter to pro se filings, to specific chapters, or to cases where a firm already appears as creditor's counsel.
All of it is raw public data, not a consumer report; Recordpipe is not a CRA. Solicitation of represented or unrepresented parties is governed by state bar rules, including waiting periods in some states, and that compliance is the firm's obligation. Engagements are fixed-price from $5,000 to $3 million; we reply within 2 business days.
What a delivery looks like
| Field | Description |
|---|---|
| record_type | Civil case, published incident report, bankruptcy filing, or judgment — the layer the row came from. |
| case_number | The court's or agency's own identifier, with the publishing court or agency and state — your verification path back to the source. |
| filing_or_incident_date | Date the case was filed, the judgment entered, or the incident published. |
| nature_of_suit | Motor vehicle negligence, premises liability, product liability, medical malpractice, or as the court codes it. |
| parties_as_published | Plaintiff and defendant names exactly as the docket shows them; no private contact data. |
| attorney_of_record | Counsel for each party as shown on the docket. |
| pro_se_flag | Whether the plaintiff or debtor is unrepresented, where the docket indicates it. |
| judgment_or_chapter | Judgment amount as stated, or bankruptcy chapter, depending on record type. |
| docket_last_event | Most recent docket entry and its date, so status is current rather than a snapshot. |
| first_seen_at | When the filing or event entered your feed. |