In repeated customer side-by-side audits, Offenders.io returned 100% of the expected records on customer test lists. Pair that retrieval evidence with 184 U.S. registry jurisdictions, official source references, independently audited security controls, and a documented service availability SLA.
Find the Records Your Workflow Expects
A sex offender search API is only useful if it finds the records your workflow expects. Evaluate known records against the inputs your team actually uses, then review the returned candidates and their official registry references.
These are results from the tested customer lists. Your results depend on the search inputs, matching mode, and information available from the source jurisdictions.
Built for Mission-Critical Teams
Operational trust matters when missed records have real downstream impacts. Evaluate both the data returned and the review process your team will use with it.
Nationwide Coverage Across 184 Registry Jurisdictions
A national sex offender API should cover the states, territories, and tribal jurisdictions your work actually depends on. Jurisdiction coverage and record totals answer different questions; neither should be reduced to a headline number alone.
Per-Record Provenance & Verification
Strong registry screening should make the evidence behind each returned record understandable. Offenders.io provides per-record provenance to official registry sources, so teams can see the underlying official registry source associated with an individual result.
For deeper review, a completed Verification Report adds per-record verification status from its source checks. Verification context belongs to the returned record, not only to the overall search. Where supported, the report workflow can perform individual record re-verification against the underlying official registry source.
Freshness, Live Lookup & Verification Are Different Layers
Offenders.io continuously synchronizes registry data for standard screening. Extensive Mode adds live registry lookups where supported. Verification Reports are a separate evidence workflow that records source-check outcomes for individual candidates and can re-verify underlying official sources where supported.
These layers serve different purposes: freshness keeps screening data current, live lookup expands real-time source access, and record-level verification documents what was confirmed for a specific candidate.
What to Look for in a Production Registry API
Coverage is one part of a production evaluation. Source provenance, verification depth, evidence preservation, reliability, and access controls matter too. The table shows how Offenders.io supports those needs.
| Evaluation criterion | Offenders.io capability |
|---|---|
| Nationwide coverage | 184 U.S. registry jurisdictions across all 50 states, DC, U.S. territories, and tribal registries. |
| Record provenance | Per-record provenance to official registry sources for official results. |
| Record-level verification | A completed Verification Report shows per-record verification status for its NSOPW and state-source checks. |
| Deeper verification | Individual record re-verification against the underlying official registry source where supported. |
| Freshness and live lookup | Continuously synchronized registry data; Extensive Mode adds live registry lookups where supported. |
| Search and matching | Name, DOB, address, ZIP, free text, and GIS searches, with supported aliases and optional fuzzy matching. |
| Structured detail | Jurisdiction-specific registry detail in Extensive Mode where available. |
| Batch and GIS | CSV screening workflows and native API radius search from 1 to 100 miles. |
| Evidence preservation | Signed Verification Reports retain search context, source checks, results, and preserved official-source evidence. |
| Dual-source visual evidence | Point-in-time screenshots from both NSOPW and the underlying state registry for the same verified record, where supported. |
| AI integration | Offenders.io MCP server for supported AI workflows. |
| Enterprise controls | SOC 2 Type II compliant controls; approved HIPAA-enabled Enterprise workflows under a BAA; separately approved FCRA-regulated access under written scope. |
| Reliability and performance | 99.9% service availability SLA and sub-200ms average standard API response time. |
Explore Batch Processing, the MCP server, and current plans for your integration path.
Preserve the Evidence Behind the Search
Source provenance explains where a record came from. A Verification Report can preserve point-in-time screenshots from both NSOPW and the underlying state registry for the same verified record, where supported. This dual-source visual evidence shows what the public registry views displayed during that verification.
The signed Verification Report keeps search inputs, source-check outcomes, results, and preserved official-source evidence together for later authorized review. It provides the actual captured views, not only a source URL.
Explore Verification Reports →
Security Backed by Independent Audit Evidence
Ask for evidence, not just a security badge. A SOC 2 Type II report issued by an independent CPA firm and a current penetration test report give your review team concrete material to assess.
Production Reliability You Can Review
Review the service availability commitment, documented integration, and status history together. Data quality and operational reliability are separate requirements, and a production service needs both.
Choosing a Sex Offender API: Common Questions
What makes a sex offender API the best choice?
Prioritize expected-record results, relevant jurisdiction coverage, per-record source provenance, verification depth, independent security evidence, and production reliability. Offenders.io brings those capabilities together; evaluate them with the inputs your workflow uses.
What does per-record source provenance mean?
Each official result can identify the underlying official registry source associated with that record. The source context belongs to the result, rather than only to the overall search.
How can a team tell whether a specific record was re-verified?
A completed Verification Report provides record-level verification context for each candidate and shows what its NSOPW and underlying state-source checks established where supported. A standard source reference alone is not proof of a new live check.
Can Offenders.io verify a record against its state registry source?
Where supported, the Verification Report workflow can perform individual record re-verification against the underlying official registry source. Extensive Mode separately adds live registry lookups and jurisdiction-specific information where available.
What evidence can a Verification Report preserve?
A signed Verification Report can preserve point-in-time screenshots from both NSOPW and the underlying state registry for the same verified record, where supported, together with the search context, source-check results, and preserved official-source evidence.
Is a larger record count always better?
No. Record totals depend on counting methods and overlap between jurisdictions. Evaluate jurisdiction coverage and expected-record results alongside the total, and review how duplicate entries are handled.
Where should developers start?
Start with the Search product overview, then use the API documentation for supported inputs, response fields, and integration details. Review Pricing for current plans and optional search modes.
Test the Claim With Records You Already Know
Try Offenders.io with the search inputs your team expects to use, then review the returned candidates against official registry references. Start with a standard API account or contact us for Enterprise evaluation support.
Start With 50 Free Monthly RequestsDiscuss Enterprise EvaluationHIPAA-regulated and FCRA-regulated workflows require separate approval and written scope; they are not included in standard self-service access.