Criminal records data infrastructure for platforms with their own compliant process.
Trust and safety teams, screening platforms, and researchers need criminal court and registry data that is broad, current, and traceable. Recordpipe collects criminal case records and public registry data across your jurisdictions, normalizes charges, dispositions, and identifiers into one schema, and delivers a criminal records API or change feed into your review process.
Criminal case records
Charges, case events, and dispositions as courts publish them.
Arrest records data
Published arrest and booking data where jurisdictions release it.
Sex offender registry data
Registry records and address changes as change feeds.
Criminal records API
Hosted endpoint for your matching engine, backed by managed collection.
Criminal records data, structured from the court record
Criminal records data is scattered across trial courts, clerks, and state repositories, each with its own case numbering, charge coding, and idea of what a disposition means. A trust and safety team or a screening company does not need another search box. It needs the record itself, normalized: who was charged, with what, in which court, and how it ended.
Recordpipe builds and runs pipelines that collect publicly available criminal case records from the jurisdictions you specify and deliver them as structured data — by file, API, webhook, or dashboard, one-time or on a daily cadence. Charge descriptions keep the court's wording and get a normalized category alongside. Dispositions are preserved as filed and mapped to a small set of outcomes your systems can act on. Every row carries the court's own case identifier, so your team can verify against the source.
Coverage is the honest question with this data. Some courts publish rich case detail. Some publish index entries. Some publish nothing usable. The $500 scoping maps what your target jurisdictions actually publish and delivers a sample within 5 business days, before you commit to anything.
Arrest records data and DUI arrests by county
Arrest records data comes from a different layer than court data. Booking logs, jail rosters, and agency blotters are published by sheriffs and police departments where state law allows, and they appear days or weeks before a court case does. For platforms that need an early signal, that gap matters. For anyone doing eligibility work, an arrest without a disposition is exactly the kind of record that needs careful handling — more on that below.
DUI arrests by county is a common request, and a good example of how a scoped pipeline works. You name the counties. Scoping confirms which agencies in those counties publish booking data, what fields they include, and how quickly entries appear and age off. The pipeline then collects on cadence, dedupes repeat bookings, and delivers rows tagged by charge category, agency, and booking date, with the original charge text intact.
Where a court case later appears for the same matter, the AI analysis layer links arrest and case when the identifiers support it, and flags the ones it cannot. No guessing. Linkage confidence is a field you filter on, not a promise we make.
Sex offender registry data and a sex offender data API
Sex offender registry data is public by statute, and it is the most operationally sensitive dataset on this page. Registries publish registrant identity, offense, and location as the law requires. What they do not do is publish it consistently, or in a format a marketplace, a dating platform, or a youth-serving organization can plug into a review queue.
Recordpipe delivers registry records as structured data across the jurisdictions you specify: registrant as published, offense description and statute, registration tier or level where the state uses one, address or location as published, and status changes over time. A sex offender data API returns current status by identifier for your review workflows. A nightly file gives compliance teams a full snapshot to reconcile against. New registrations, moves, and removals arrive as events in the feed, not silent overwrites.
Use of registry data is restricted by statute in many states, including specific rules on what the data may be used for. We deliver the public record, and we ask about intended use at intake. Applications that use registry data in decisions about a person get compliance review before a contract is signed.
Court records API, background check data, and where FCRA draws the line
A court records API sounds like background check data, and that is where discipline matters. Recordpipe delivers raw public data — cases, charges, dispositions, arrests, and registry entries as published by the source. It is not a consumer report, and Recordpipe is not a consumer reporting agency. If your product makes decisions about a person's employment, housing, credit, or insurance, that use is governed by FCRA and state law, and it gets compliance review at intake. Some of those engagements we take. Some we decline. Either way, you know before you pay for a feed.
Trust and safety platforms, screening companies building their own compliant products, insurers doing risk modeling, and researchers doing population-level work are the teams this data is built for. For them, a risk data provider that hands over the record as filed — with identifiers, dates, and the court's own wording — beats one that hands over a score with no path back to the source. The score is yours to build. The record is ours to deliver, correctly and on time.
Engagements are fixed-price from $5,000 to $3 million, scoped in writing. We reply to every inquiry within 2 business days.
What a delivery looks like
| Field | Description |
|---|---|
| record_type | Court case, arrest or booking entry, or registry entry — the layer the row came from. |
| case_number | The court's or agency's own identifier, your verification path back to the source. |
| court_or_agency | The specific court, sheriff, or registry that published the record, with jurisdiction and state. |
| subject_as_published | Name and identifying details exactly as the source publishes them; no identity resolution across people. |
| charge_text | The charge as written by the court or booking agency, unedited. |
| charge_category | Normalized category alongside the original text — DUI, assault, theft, drug, weapons, sex offense, other — plus felony or misdemeanor level as the source classifies it. |
| filing_or_booking_date | Date the case was filed or the booking was logged. |
| disposition | Outcome as filed, plus a normalized value: convicted, dismissed, acquitted, pending, or not published. |
| registry_status | For registry rows: current tier or level, registration date, and change events over time. |
| first_seen_at | When the record or its latest change entered your feed — your audit trail on freshness. |
In the field.
Trust and safety: review queues with the record attached
A marketplace or platform trust and safety team can route flagged accounts through a review queue that shows current registry status and serious felony convictions in the jurisdictions the platform operates in, each with a case number a reviewer can verify. The decision stays with the reviewer; the data is the record, not a score.
Screening companies: sourcing for a compliant product
A screening company that is itself a CRA can source court and registry data from Recordpipe as raw input to its own compliant product, with dispositions as filed and identifiers preserved for its verification process. That arrangement is defined at intake, with compliance review, before any feed is built.
Insurers and risk teams: county-level patterns
An insurer's risk modeling team can track DUI arrests by county and case outcomes over time as a market-level input, aggregated by geography and charge category. Raw public data for modeling, not a consumer report and not an individual underwriting file.
Researchers and journalists: dispositions at scale
A research group or newsroom can study charging and disposition patterns across courts with a structured feed that preserves the court's own wording next to a normalized outcome, so findings trace back to source records instead of a vendor's interpretation.
Public-record risk data for trust and safety, not a background check product
We deliver raw public data, not consumer reports; Recordpipe is not a CRA. Eligibility use cases get compliance review at intake. Fixed-price from $5,000; scoping is $500, credited.