Driver screening API 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.
25 free searches, no card. $0.15 a call, no platform fee, no seats, no minimum. No code needed: search from your dashboard, or integrate the full API when you’re ready.
curl https://api.offendersearch.app/v1/search \ -H "X-API-Key: $OFFENDERSEARCH_KEY" \ -H "Content-Type: application/json" \ -d '{"query": {"firstName": "Tom", "lastName": "Nguyen", "dob": "1991-02-17", "ageTolerance": 1}}' // response { "status": "complete", "elapsedMs": 410, "counts": { "records": 0, "sourcesQueried": 58, "sourcesComplete": 58, "sourcesIncomplete": 0 }, "records": [] } // a match carries its reason { "matchState": "dob_match", "matchConfidence": 0.98, "matchBasis": ["lastName:exact", "firstName", "dob"] }
Making a hiring decision? Use an FCRA workflow.
If a result will help decide whether to hire someone, the check has to run as an FCRA-regulated consumer report, with a permissible purpose, consent, accuracy controls and a dispute path for the person. Our standard search and API are not a consumer report, and standard results are never used for that decision. FCRA workflows run through FCRA Partner Access, for background check companies and screening platforms under a written FCRA agreement.
FCRA pricing is quoted per partner, so contact us for pricing.
Screening challenges 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
What sex offender screening gives rideshare, delivery, and logistics platforms
Screen drivers at onboarding
Continuously re-verify an active fleet
Produce a per-driver check history
Rideshare & Delivery sex offender check API: request and response. One POST per person, or the same search from the dashboard with no code.
curl https://api.offendersearch.app/v1/search \ -H "X-API-Key: $OFFENDERSEARCH_KEY" \ -H "Content-Type: application/json" \ -d '{"query": {"firstName": "Tom", "lastName": "Nguyen", "dob": "1991-02-17", "ageTolerance": 1}}' // response { "status": "complete", "elapsedMs": 410, "counts": { "records": 0, "sourcesQueried": 58, "sourcesComplete": 58, "sourcesIncomplete": 0 }, "records": [] } // a match carries its reason { "matchState": "dob_match", "matchConfidence": 0.98, "matchBasis": ["lastName:exact", "firstName", "dob"] }
Send what you have. Name and date of birth; age or birth year when that is all you hold. Date of birth drives matchState: dob_match, year_match, age_match or no_dob_age_year.
Read the counts. sourcesComplete against sourcesQueried says whether all 58 registries answered, so a partial search is never read as a clear one.
Branch on the score. matchConfidence and matchBasis on every record, with the registry cited.
| Person | Checked for | Result | Answered |
|---|---|---|---|
| Tom Nguyen | driver onboarding | No match | 58 / 58 |
| Jordan Sample | driver onboarding | Match · dob_match | 58 / 58 |
| J. Sample | driver onboarding | Review · year_match | 58 / 58 |
Read the API docs › · Search from the dashboard › · Screen a CSV without code ›
Sex offender screening built for rideshare & delivery. One key, one schema, one stored record of every check.
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.
When rideshare, delivery, and logistics platforms run a sex offender check. Each moment, and the call that fits it.
Before a driver’s first trip
State TNC laws require a background check before a driver can accept rides.
At annual or periodic re-screening
Some states require re-checks on a schedule — Texas requires an annual check.
When a driver adds a new state
Drivers who start working in another state face that state’s screening rules.
Between scheduled checks
Monitoring alerts you when a driver’s registry status changes in the gap between re-screens.
Rideshare & Delivery screening workflow. Step by step, from the first call to the stored record.
Collect verified identity at signup. Legal name, date of birth and driver’s license data.
Search the registries the statutes name. Many TNC laws require a search of the National Sex Offender Public Website; one call here covers the 58 US registries, each official record linked.
Run criminal records on the same key. County, state and federal records for the look-back your state requires.
Decide through an FCRA workflow. Driver eligibility decisions run as FCRA-regulated consumer reports.
Re-check on the state’s schedule and monitor. Annual re-screens where required, with monitoring in between.
Rideshare & Delivery screening: what the law 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.
Rideshare is one of the most regulated screening categories. The GAO counted 45 states and DC requiring TNC driver background checks (GAO-24-107093). California requires TNCs to check drivers against the National Sex Offender Public Website (Pub. Util. Code § 5445.2), Texas requires a check before a driver is approved and annually after (Occ. Code § 2402.107), and North Carolina and Connecticut set their own rules (N.C. Gen. Stat. § 20-280.6; CT HB 7126).
App-based delivery in California is covered by Proposition 22, which requires criminal background checks on drivers (Bus. & Prof. Code § 7458). Statutes typically name the national website as the destination to check; a normalized search across the 58 registries, with each official record linked, gives a compliance team the evidence it needs to show the check happened.
| 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. |
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.
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.
Screening practices for rideshare, delivery, and logistics platforms. Record what you checked, not just what you found.
| NJ | New Jersey · answered | 0 |
| NY | New York · answered | 0 |
| PA | Pennsylvania · answered | 0 |
| FL | Florida · answered | 0 |
| TX | Texas · answered | 0 |
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.
Registry and criminal records for rideshare & delivery, 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.
Sex offender registry
58 US registries, continuously updated, with photographs, aliases, addresses and the official record citation on every match. 1.5M records in one schema.
Sex offender API ›Criminal records
1,408 county jail rosters, 53 state corrections systems, courts, warrants and federal custody, almost 50 million records in the same scored, source-cited schema. Same key, same price.
Criminal search API ›FCRA background checks
When a result decides a hire or a tenancy, the check runs as an FCRA order through FCRA Partner Access: consent, the check, disputes and adverse-action steps. Pricing is quoted per partner.
FCRA Partner Access ›Coverage today: 1,914 criminal jurisdictions catalogued, 1,564 live, 51 states + DC + federal. See what each state publishes, or the live list at /v1/criminal/sources.
What rideshare & delivery screening costs per check. $0.15 a call, $0.11 past 2,000 a month. No platform fee, no seats, no minimum.
| 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. No setup fee, no per-seat licence, no monthly minimum on search and no annual contract, so the price scales down with you as well as up. A fraction of what legacy screening platforms charge.
The background check API · screen a CSV without code. More for developers: the free background check API tier, background check API pricing, the employment screening API and tenant screening API, and the background check API in Python and background check API in Node.js tutorials.
Rideshare & Delivery screening FAQ
For anything else, talk to sales or read the API docs.
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.
Which states require rideshare drivers to pass a sex offender check?
Most do: the GAO counted 45 states and DC requiring TNC background checks. California and Texas name sex offender registry checks specifically.
Do delivery drivers need background checks?
In California, Proposition 22 requires app-based delivery companies to run criminal background checks. Elsewhere, it depends on the state and the platform’s policy.
How often must drivers be re-checked?
Texas requires an annual check. Other states vary; monitoring covers the gap between scheduled re-screens.
Related
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.