A registry data layer for screening providers
Power your product with a single sex-offender registry API instead of maintaining 57 scrapers — scored matches, provenance, freshness tiers, and an offenders.io drop-in.
The problem for background-screening providers and CRAs
- Maintaining per-state scrapers is a constant tax
- Existing aggregators lack provenance and confidence scoring
- Migrating vendors usually means re-integrating
Outcomes
- Retire in-house registry scrapers
- Migrate from offenders.io with minimal code change
- Ship provenance and scoring to your customers
How Offendersearch helps
One data layer, 57 sources
Replace a fleet of brittle per-state scrapers with a single normalized API.
Drop-in offenders.io compat
Point existing integrations at /v1/compat/sexoffender and switch with only a base URL and key change.
Provenance & scoring built in
matchConfidence, matchBasis, and per-source links your customers can trust.
Questions from background-screening providers and CRAs
How hard is it to migrate from offenders.io?
Use /v1/compat/sexoffender, which accepts offenders.io’s exact parameters and returns their exact envelope; switch by changing only the base URL and key.
Can we white-label the data?
The API returns normalized, source-tagged records you can present in your own product, subject to per-jurisdiction legal-use terms.
Screen background-screening providers and CRAs with one API
Power your product with a single sex-offender registry API instead of maintaining 57 scrapers — scored matches, provenance, freshness tiers, and an offenders.io drop-in.