# NSOPW U.S. Public Registry Search Scraper (`dromb/nsopw-offender-search`) Actor

Search source-native public sex offender registry records from the National Sex Offender Public Website by name, ZIP, jurisdiction, or geographic radius for public-records research, registry lookup, and source monitoring.

- **URL**: https://apify.com/dromb/nsopw-offender-search.md
- **Developed by:** [Dmitriy Gyrbu](https://apify.com/dromb) (community)
- **Categories:** Automation, Developer tools, Other
- **Stats:** 5 total users, 3 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## NSOPW U.S. Public Registry Search Scraper

Search source-native public sex offender registry records exposed through the National Sex Offender Public Website (NSOPW). Export names, aliases, jurisdiction IDs, source registry links, images, and location fields into an Apify Dataset for public-records research, registry lookup, and source monitoring.

This is an unofficial tool and is not affiliated with NSOPW, the U.S. Department of Justice, or any participating jurisdiction.

### What the Actor does

- Searches by first and last name with optional city, county, and jurisdiction filters.
- Searches up to five ZIP codes.
- Performs supported 1-, 2-, or 3-mile geographic searches.
- Returns current state, territory, Indian Country, radius, and distance filter metadata.
- Selects one source-native record from a live search context by exact offender URL or ID.
- Preserves the originating jurisdiction and registry URL instead of pretending all participating registries are one identity system.

NSOPW matching semantics are source-defined. A search for a name can return exact names, aliases, spelling variations, and records whose alias matches the query. Do not interpret a returned row as proof that two people are the same person.

### Supported operations

| Operation | Required input | Dataset result |
|---|---|---|
| `search` | Name pair, ZIP list, or complete geographic search | Normalized source-native registry records |
| `item` | Exact `offenderUri` or `offenderId` plus the original search context | One matching registry record |
| `search_filters` | None | One current filter-directory object |
| `probe` | None | Health summary in `OUTPUT`; no person Dataset rows |

The default input is the current jurisdiction/filter directory. It produces a nonempty Dataset without silently adding person-search fields to ZIP or geographic inputs.

### Ready-to-run examples

#### Name and jurisdiction search

```json
{
  "operation": "search",
  "firstName": "john",
  "lastName": "smith",
  "jurisdictions": ["AL"],
  "limit": 10,
  "proxy": "direct"
}
```

#### ZIP search

```json
{
  "operation": "search",
  "zip": ["36117"],
  "limit": 10,
  "proxy": "direct"
}
```

#### Geographic search

Geographic mode requires latitude, longitude, distance, and at least one supported jurisdiction. Do not combine it with name or ZIP fields.

```json
{
  "operation": "search",
  "latitude": 32.3617,
  "longitude": -86.2792,
  "distance": 1,
  "jurisdictions": ["AL"],
  "limit": 10,
  "proxy": "direct"
}
```

#### Filter and jurisdiction discovery

```json
{
  "operation": "search_filters",
  "refresh": false,
  "proxy": "direct"
}
```

#### Select one record from search context

`item` is intentionally source-aware: it repeats the supplied search and selects the exact ID or URL from that response. It is not a universal person-detail lookup.

```json
{
  "operation": "item",
  "offenderId": "17994482",
  "firstName": "john",
  "lastName": "smith",
  "jurisdictions": ["AL"],
  "proxy": "direct"
}
```

IDs and registry participation can change. For durable workflows, take `id` or `source_url` from a fresh `search` result and pass the same search context to `item`.

### Input rules

- Name mode requires both `firstName` and `lastName`.
- ZIP mode accepts one to five numeric five-character ZIP codes.
- Geographic mode requires `latitude`, `longitude`, `distance`, and at least one jurisdiction.
- Supported distances are 1, 2, and 3 miles.
- Do not combine geographic mode with name or ZIP search.
- `limit` is bounded from 1 to 500. Use small limits for scheduled monitoring.
- `includeJurisdictionStatus` can add source response diagnostics to `OUTPUT`; it does not create additional person rows.

### Dataset fields

Person rows can include:

- source-native `id` and `slug`;
- full, first, middle, and last names;
- aliases;
- age, gender, and absconder flag when supplied by the participating registry;
- jurisdiction ID and registry domain;
- exact source record URL;
- image URLs;
- residence, employment, or school location objects supplied by the source;
- primary city, county, state, ZIP, latitude, and longitude.

Empty fields are omitted. Filter discovery returns a different, source-appropriate row shape containing jurisdiction and radius options.

The `OUTPUT` record contains the operation status, structured errors, access diagnostics, requested/published item counts, and charge-limit information.

### Saved Task use cases

Three bounded Saved Tasks are recommended:

1. `nsopw-alabama-name-search` — demonstrate a source-native name and jurisdiction search.
2. `nsopw-zip-registry-search` — demonstrate a bounded ZIP-area lookup.
3. `nsopw-jurisdiction-directory` — discover current searchable jurisdictions before building a workflow.

The exact inputs and buyer use cases are documented in `SAVED_TASKS.md`.

### Proxy behavior

- `direct` — cheapest verified route and the recommended default.
- `auto` — currently starts with direct access.
- `apify` — Apify server/datacenter proxy diagnostics.
- `residential` — U.S. residential proxy diagnostics; more expensive.
- `special` — special Apify proxy diagnostics only; not recommended for routine runs.

The current official backend works without a browser. Paid proxies should only be used after reproducible direct failures.

### API and Dataset workflow

Start a run:

```bash
curl -X POST "https://api.apify.com/v2/acts/dromb~nsopw-offender-search/runs?token=YOUR_APIFY_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"operation":"search","firstName":"john","lastName":"smith","jurisdictions":["AL"],"limit":10,"proxy":"direct"}'
```

Then read the run's `defaultDatasetId` and request:

```bash
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=json&token=YOUR_APIFY_TOKEN"
```

Because this data is sensitive, no generic CRM or Telegram person-alert template is bundled. Integrations should include access control, purpose limitation, retention rules, and human verification against the official source.

### Responsible-use limitations

- NSOPW aggregates participating jurisdictions; coverage and availability vary.
- A jurisdiction may be offline, delayed, or return zero records.
- Names and aliases are not unique identifiers.
- A match should be verified at the linked official registry before action is taken.
- Do not use this Actor to harass, threaten, discriminate against, or unlawfully profile anyone.
- Do not treat the Dataset as a substitute for legally compliant screening procedures or use it to make decisions prohibited by applicable employment, housing, credit, insurance, privacy, or anti-discrimination law.
- Users are responsible for NSOPW terms, participating-registry terms, and applicable law.

# Actor input Schema

## `operation` (type: `string`):

Operation to perform: probe, search\_filters, search, or item.

## `firstName` (type: `string`):

First name for name search. Requires lastName.

## `lastName` (type: `string`):

Last name for name search. Requires firstName.

## `city` (type: `string`):

Optional city filter for name search.

## `county` (type: `string`):

Optional county filter for name search.

## `zip` (type: `array`):

ZIP code filter (up to 5 values).

## `jurisdictions` (type: `array`):

Jurisdiction codes, e.g. AL, NY, CHEROKEE.

## `latitude` (type: `number`):

Latitude for geographic search (-90 to 90).

## `longitude` (type: `number`):

Longitude for geographic search (-180 to 180).

## `distance` (type: `integer`):

Radius in miles for geographic search: 1, 2, or 3.

## `limit` (type: `integer`):

Maximum offenders to return (1-500).

## `includeQueryJurisdictions` (type: `boolean`):

Include full query.jurisdictions list in response.

## `includeJurisdictionStatus` (type: `boolean`):

Include jurisdiction\_status rows in response.

## `jurisdictionStatusNonZeroOnly` (type: `boolean`):

When jurisdiction\_status is included, keep only rows with records > 0.

## `refresh` (type: `boolean`):

Force refresh of cached filter metadata for search\_filters operation.

## `offenderUri` (type: `string`):

Exact offender URL returned by search (for item operation).

## `offenderId` (type: `string`):

Offender ID extracted from offender\_uri (for item operation).

## `proxy` (type: `string`):

Access route. Direct is the cheapest verified default. Apify uses server/datacenter proxies; residential uses a US residential route; special is diagnostic only.

## `proxyCountry` (type: `string`):

Two-letter country code for residential proxy mode.

## Actor input object example

```json
{
  "operation": "search_filters",
  "limit": 10,
  "includeQueryJurisdictions": false,
  "includeJurisdictionStatus": false,
  "jurisdictionStatusNonZeroOnly": true,
  "refresh": false,
  "proxy": "direct",
  "proxyCountry": "US"
}
```

# Actor output Schema

## `results` (type: `string`):

Normalized NSOPW registry records or filter metadata returned by the Actor.

## `summary` (type: `string`):

Operation status, errors, access route, and publication counts.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dromb/nsopw-offender-search").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("dromb/nsopw-offender-search").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call dromb/nsopw-offender-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=dromb/nsopw-offender-search",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2szf3FbVEnTaWEhLf/builds/8ik7yzUpl3YXVBJXE/openapi.json