Driver screening for rideshare & delivery
Screen and continuously re-verify drivers and couriers against every US sex-offender registry with a low-latency, scored API built for fleet-scale trust & safety.
No code needed — search from your dashboard, or integrate the full API when you’re ready.
The problem for rideshare, delivery, and logistics platforms
- Drivers interact directly with riders and households
- A driver cleared at onboarding can register later
- Rider-safety incidents require a defensible screening record
Outcomes
- Screen drivers at onboarding
- Continuously re-verify an active fleet
- Produce a per-driver check history
How Offendersearch helps
Onboarding screening
Low-latency sync calls fit a driver signup flow.
Continuous monitoring
Daily freshness re-verifies an active fleet near-live.
Defensible records
Provenance and lastCheckedAt document every check for safety reviews.
What the law actually requires
Rideshare is the sector where a registry search is most often written directly into statute — and where the consequence is unusually blunt. In several states appearing on the registry is not a factor to weigh but a flat bar on driving, and at least one state requires the check to be repeated every year rather than once at onboarding.
| Jurisdiction | Citation | Applies to | What it requires |
|---|---|---|---|
| Texas | Tex. Occ. Code § 2402.107(a)(2) | Staff | Before a driver may log in, the company must run a local, state and national criminal background check using a commercial multistate records locator and the national sex offender public website maintained by the US Department of Justice. |
| Texas | Tex. Occ. Code § 2402.107(b)(3) | Staff | A company may not permit an individual to drive who is found registered on that website — a flat disqualification, not a factor to be weighed. |
| Texas | Tex. Occ. Code § 2402.107(c) | Staff | The same background check must be repeated annually for every driver with access to the network. |
| California | Cal. PUC § 5445.2(a)(1)(B) | Staff | The company’s driver screening must include a search of the US Department of Justice National Sex Offender Public Website. |
| California | Cal. PUC § 5445.2(a)(2)(A) | Staff | A company may not contract with, employ or retain a driver currently registered on that website. |
Citations link to the primary text. This is background, not legal advice — obligations change, and your counsel is the right reader of your own facts.
And what it doesn’t
There is no federal TNC screening statute — this is entirely state law, and the details differ enough to matter. A single national screening policy will satisfy the strictest state and over-satisfy the rest, which is usually the right engineering answer, but it is a choice rather than a requirement. The annual recheck in particular is a Texas obligation, not a universal one.
Screening practices for rideshare, delivery, and logistics platforms
Design for the recheck, not just the onboard
Screening at signup is the easy half. Texas requires the whole check again every year, which turns screening from an onboarding step into a scheduled workload the platform has to own.
Treat a registry hit as terminal in the flow
Where statute makes registration a flat bar, an operations process that routes hits to human review as “maybe” is out of step with the rule. The system should encode which findings are disqualifying and which are judgment calls.
Screen against where the driver has lived
Drivers move states more often than most workforces. A search scoped to the state of operation misses a registration two states back — which is exactly the failure the statute is aimed at.
Keep the evidence of the check, not just the verdict
When a platform is asked to show it complied, the useful record is what was searched and when, per source — not a stored pass/fail with nothing behind it.
Questions from rideshare, delivery, and logistics platforms
Can I continuously monitor active drivers?
Yes. Re-run searches on the Daily freshness tier to keep an active fleet re-verified; each record shows its lastCheckedAt.
Does this scale to a large fleet?
Yes. Metered pricing with a volume rate after 2,000 calls a month supports fleet-scale screening.
Registry and criminal records on one key
Most rideshare, delivery, and logistics platforms need more than one check, and running two vendors means two integrations, two contracts and two invoices. Both run on the same account, the same key and the same response shape.
Sex offender registry
58 US registries — the 50 states, DC and the territories — continuously updated, with photographs, aliases, addresses and the official record citation on every match.
Criminal records
more than a thousand county, state and federal jurisdictions — county jail rosters, statewide prison systems, court records and warrants — with coverage in every US state, in the same scored, source-cited schema.
1,375
county jurisdictions in the criminal roster — the layer where most US matters begin, and the one thin vendors skip.
51
states with a live statewide prison system, for the post-conviction picture in the same call.
58
US sex offender registries, continuously updated — the check rideshare, delivery, and logistics platforms are most often required to run.
See what each state publishes, or the live list at /v1/criminal/sources.
Per check, with no floor underneath it
$0.15 a call, dropping to $0.11 for every call past 2,000 in a calendar month. No setup fee, no per-seat licence, no monthly minimum and no annual contract — so the price scales down with you as well as up.
| Checks / month | Cost | Per check |
|---|---|---|
| 500 | $75.00 | $0.1500 |
| 5,000 | $630.00 | $0.1260 |
| 50,000 | $5,580.00 | $0.1116 |
A batch is billed per row, so bulk screening costs the same per person as a single lookup. Full pricing · screen a CSV without code.
Screen rideshare, delivery, and logistics platforms with one API
Screen and continuously re-verify drivers and couriers against every US sex-offender registry with a low-latency, scored API built for fleet-scale trust & safety.