# Contractor New License & Change Monitor (TX, VA, NV) (`scrapebench/contractor-license-change-monitor`) Actor

Newly licensed contractors and licence changes (status, expiry, address, phone, removals) in Texas, Virginia and Nevada since your last run, one row per event.

- **URL**: https://apify.com/scrapebench/contractor-license-change-monitor.md
- **Developed by:** [ScrapeBench](https://apify.com/scrapebench) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.01 / licence event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Contractor New License & Change Monitor (TX, VA, NV)

### Pain points

- A newly licensed contractor needs insurance, bonding, supplies and software in its first weeks, but the state boards publish a roster, not a list of who is new.
- Spotting a renewal, a lapse or a moved business means downloading tens of thousands of licences again and comparing them by hand.
- A monitor that goes quiet when a board's file fails to download looks exactly like a quiet week.

### What we solve

- Each run reads the whole contractor roster of Texas, Virginia and Nevada from the boards' own files and compares it with the roster it saw last time.
- You get one row per event: a new licence, a status change, a new expiry date (a renewal), a new address, a new phone, or a licence that left the current roster, with the licence attached.
- A board that does not answer in full is never compared: you get a free notice and your baseline stays as it was, so nothing is lost and nothing is invented.

### Summary

A scheduled feed of new contractor licences and licence changes for Texas (TDLR electrical, A/C, appliance installation, electrical sign and elevator contractors), Virginia (DPOR Class A, B and C contractors and residential tradesmen) and Nevada (NSCB, every classification). Every run reads each state's whole roster from the board's own published files, compares it with the roster this monitor saw on its last run, and returns one row per event with the licence attached: business name, licence number and type, trades, expiry, address, and phone (Texas, Nevada) or email (Virginia). The memory of the last roster lives in your own Apify account under a monitor ID you choose, so you can run several schedules side by side. The first run saves the baseline for free and already lists Virginia licences certified in the last 7 days; from the second run on you get every change. Filter by trade keyword, city or ZIP prefix, pick the event types you want, and pay only for the events delivered.

### Who it's for

- Insurance and bonding agents selling to newly licensed contractors
- Suppliers, distributors and software vendors prospecting new trade businesses
- Compliance teams watching renewals, lapses and moves across a contractor roster
- Data teams keeping a contractor database in sync with the state boards

### How to use

Set the input, run the actor, and collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API). Example input:

```json
{
  "states": [
    "VA"
  ],
  "tradeKeywords": [
    "roofing"
  ],
  "monitorId": "va-roofers-weekly",
  "maxResults": 100
}
```

See **Inputs** below for every available field.

### What you get

One row per record:

| Field | Description |
|---|---|
| `event` | new_license, status_change, expiry_change, address_change, phone_change or removed |
| `changed_field` | The licence field that moved, for a change event |
| `previous_value` | What the last run saw |
| `current_value` | What the board publishes now |
| `state` | TX, VA or NV |
| `license_number` | The board's licence number (Virginia: the full DPOR number, e.g. 2705203386) |
| `business_name` | Licensed business or licensee |
| `person_name` | Owner (Texas) or individual licensee (Virginia), where published |
| `license_type` | TDLR licence type, DPOR class, or Contractor (Nevada) |
| `trades` | DPOR specialties (Virginia) or NSCB classifications (Nevada) |
| `status` | Board status (Nevada); Current for a Virginia roster licence |
| `issue_date` | Certification date (Virginia) |
| `expiration_date` | Licence expiry, YYYY-MM-DD |
| `address` | Street address as the board publishes it |
| `city` | City |
| `zip_code` | ZIP code |
| `phone` | Business phone (Texas, Nevada) |
| `email` | Email (Virginia) |
| `monitor_id` | The monitor ID this run compared against |
| `source_url` | The board file or page the licence came from |

Sample:

```json
{
  "event": "new_license",
  "changed_field": null,
  "previous_value": null,
  "current_value": null,
  "state": "VA",
  "license_number": "2705203386",
  "business_name": "PROVIDENCE COMMERCIAL ROOFING LLC",
  "person_name": null,
  "license_type": "Class A Contractor",
  "trades": [
    "Roofing"
  ],
  "status": "Current",
  "issue_date": "2026-11-13",
  "expiration_date": "2028-11-30",
  "address": "6205 GRAND REUNION DR",
  "city": "HOSCHTON",
  "zip_code": "30548",
  "phone": null,
  "email": "jhuyge@providence-roof.com",
  "monitor_id": "va-roofers-weekly",
  "source_url": "https://www.dpor.virginia.gov/sites/default/files/Records%20and%20Documents/Regulant%20List/2705a__crnt.txt"
}
```

### Inputs

| Field | Required | Type | Default | Description |
|---|---|---|---|---|
| `states` | no | array | `["VA"]` | Which state contractor rosters to watch: TX (TDLR contractor licences: electrical, A/C, appliance installation, electrical sign, elevator), VA (DPOR Class A/B/C contractors and residential tradesmen) and NV (NSCB, every classification). Leave empty for all three. Each state is read and compared on every run. |
| `state` | no | string | — | One state, TX, VA or NV. Kept for callers that send one value; combined with 'States'. |
| `events` | no | array | `[]` | Which events you want, any of: new_license, status_change, expiry_change, address_change, phone_change, removed (gone from the board's current-licence roster: lapsed, expired or revoked). Leave empty for all six. Only the events you pick are charged. |
| `tradeKeywords` | no | array | `[]` | Keep only licences whose licence type or trade contains one of these words, case-insensitive: e.g. roofing, electrical, HVAC, A/C, plumbing, Class A, C-2. Leave empty for every contractor. |
| `cities` | no | array | `[]` | Keep only licences whose business or mailing city is one of these (exact name, case does not matter). TX A/C contractors publish no address, so they never match a city or ZIP filter. |
| `zips` | no | array | `[]` | Keep only licences whose ZIP starts with one of these, e.g. 22 (northern Virginia) or 89501. |
| `issuedAfter` | no | string | — | Virginia publishes each licence's certification date, so the FIRST run of a monitor already lists Virginia licences certified since this date (default: the last 7 days). Texas and Nevada publish no issue date: their new licences start with the second run. |
| `monitorId` | no | string | `"default"` | Name of this monitor's memory of the rosters it last saw, kept in your own Apify account (key-value store 'contractor-license-change-monitor'). Use one ID per schedule; a new ID starts a fresh baseline. Filters can change freely under one ID: the memory always holds the whole state. |
| `maxResults` | no | integer | `1000` | A spend cap for the whole run, across states. Events past it are not lost: they stay pending and come in the next run. |

### Pricing (Pay Per Event)

You pay per result (`license-event`) — **no charge for empty runs**. Example: **100 licence events** at *$0.01/result* ≈ **$1.00**.

You pay per event delivered, nothing per run or per state. The first run of a monitor saves its baseline for free. A week with no change returns one free row saying so. Events over your maxResults or your maximum charge are not lost: they come in the next run.

### Use cases

- New-licence leads: a weekly list of contractors licensed since last week, by trade and area.
- Renewal and lapse watch: expiry changes show renewals; removals show licences that left the current roster.
- Address and phone hygiene: keep your CRM's contractor records in step with what the boards publish.
- Status alerts: Nevada licences that change status, as the board publishes it.

### Why this actor

- Three states, six event types, one row shape: new licences and changes in the same feed.
- Fails closed: a short or refused roster is never compared, so a download failure never shows up as thousands of removals.
- Nothing is lost: events past your cap stay pending for the next run, and the baseline always holds the whole state, so changing a filter never resets history.
- Pay per event only: no start fee and no per-state fee; baseline and empty runs are free.

### Limitations & updates

Covers TX (TDLR contractor licence types only, not individual electricians or other TDLR trades), VA (DPOR contractor files) and NV (NSCB). Texas publishes no licence status and Texas A/C contractors no address; Virginia publishes no phone. Events are what changed between two of your runs, so the first run is a baseline.

### FAQ

**Why does my first run return few or no events?**

A change needs something to compare with. The first run of a monitor ID saves the whole roster for free; from the second run on you get every change. Virginia publishes certification dates, so its new licences since issuedAfter (default: the last 7 days) are listed on the first run too.

**How often should I schedule it?**

Weekly suits most lead and compliance work; daily works too. Checked 2026-11-16: Virginia's files had been refreshed that morning, Texas's dataset was last republished on 2026-11-13, and Nevada's listing is live.

**What does 'removed' mean?**

The licence is no longer on the board's current-licence roster. Virginia and Nevada publish current licences only, so a removal usually means lapsed, expired or revoked. It is not a statement about why.

**Can I run several monitors?**

Yes. Each monitor ID keeps its own memory in a key-value store in your own Apify account. Filters can change freely under one ID.

**What if a board is down?**

That state is skipped with a free notice and its baseline is kept, so the next successful run reports everything that changed in between.

**Which states are next?**

Texas, Virginia and Nevada today. The monitor reads each board's whole roster on every run, so it covers states whose boards publish one.

### Which actor to choose

Part of the same suite — pick the one that fits your goal:

- **Texas Contractor Directory & Leads Scraper (TDLR)** — You want the whole current Texas list (or a lookup) once, not the changes.
- **Virginia Contractor License Lookup (DPOR Bulk)** — You want every current Virginia contractor by trade and area, or a name lookup.
- **Nevada Contractor License Lookup & Verify (NSCB)** — You want to verify a Nevada licence or export the current Nevada list.
- **Contractor License Expiration Monitor & Alerts (Notion)** — You watch a fixed list of your own contractors across 8 states, with alerts in Notion.

### Guides & use cases

Written up on **[scrapebench.dev](https://scrapebench.dev)** — the bench that runs and verifies this actor against the live source every night:

- **How-to:** [How to run Contractor New License & Change Monitor (TX, VA, NV)](https://scrapebench.dev/guides/how-to-contractor-license-change-monitor/)
- **Use case:** [A weekly list of newly licensed contractors in Texas, Virginia and Nevada](https://scrapebench.dev/use-cases/new-contractor-license-leads-weekly/)

More actors, coverage and nightly verification results: **[scrapebench.dev](https://scrapebench.dev)**

### Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the [MCP tab](https://apify.com/scrapebench/contractor-license-change-monitor/api/mcp) on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

> "Watch Virginia roofing contractors for me: run the contractor licence change monitor for VA with the trade keyword roofing and monitor ID va-roofers-weekly, and list the new licences it finds."

The first call saves the baseline and lists Virginia roofers certified in the last 7 days; call it again next week with the same monitor ID for every change. Runs started this way bill exactly like any other run.

### Data & lawful use

This actor collects publicly available information that the Texas Department of Licensing and Regulation (TDLR), the Virginia Department of Professional and Occupational Regulation (DPOR) and the Nevada State Contractors Board (NSCB) publishes for public
lookup — licence records, business listings and the contact details professionals list there.
Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any
names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the
controller of that data and we act only as your processor (Apify Standard Actor Contract).
You need a lawful basis for your use, must honour opt-out and deletion requests, and must
follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar).
Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or
for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and
don't sell or share them.

### Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by
the Texas Department of Licensing and Regulation (TDLR), the Virginia Department of Professional and Occupational Regulation (DPOR) and the Nevada State Contractors Board (NSCB). Names and marks are used only to describe the data source. Records are
provided as published by the source and may be out of date or incomplete. For anything
consequential (hiring, a permit, a legal decision), confirm the record with the issuing
agency. You are responsible for making sure your use complies with applicable law and the
source's terms.

### Need help?

Open an issue on this actor's **Issues** tab and we'll respond there. Bug reports, missing
fields and feature requests are all welcome. Guides and examples: [scrapebench.dev](https://scrapebench.dev).

If you are a person named in this data and want your record removed from our copy, email
apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: [Apify Console → Settings → Security → Share run data with developers](https://console.apify.com/settings/security). It lets us see exactly what went wrong and keep improving the actor.

If this actor saved you time, a short review on its Store page helps other buyers find it.

# Actor input Schema

## `states` (type: `array`):

Which state contractor rosters to watch: TX (TDLR contractor licences: electrical, A/C, appliance installation, electrical sign, elevator), VA (DPOR Class A/B/C contractors and residential tradesmen) and NV (NSCB, every classification). Leave empty for all three. Each state is read and compared on every run.

## `state` (type: `string`):

One state, TX, VA or NV. Kept for callers that send one value; combined with 'States'.

## `events` (type: `array`):

Which events you want, any of: new_license, status_change, expiry_change, address_change, phone_change, removed (gone from the board's current-licence roster: lapsed, expired or revoked). Leave empty for all six. Only the events you pick are charged.

## `tradeKeywords` (type: `array`):

Keep only licences whose licence type or trade contains one of these words, case-insensitive: e.g. roofing, electrical, HVAC, A/C, plumbing, Class A, C-2. Leave empty for every contractor.

## `cities` (type: `array`):

Keep only licences whose business or mailing city is one of these (exact name, case does not matter). TX A/C contractors publish no address, so they never match a city or ZIP filter.

## `zips` (type: `array`):

Keep only licences whose ZIP starts with one of these, e.g. 22 (northern Virginia) or 89501.

## `issuedAfter` (type: `string`):

Virginia publishes each licence's certification date, so the FIRST run of a monitor already lists Virginia licences certified since this date (default: the last 7 days). Texas and Nevada publish no issue date: their new licences start with the second run.

## `monitorId` (type: `string`):

Name of this monitor's memory of the rosters it last saw, kept in your own Apify account (key-value store 'contractor-license-change-monitor'). Use one ID per schedule; a new ID starts a fresh baseline. Filters can change freely under one ID: the memory always holds the whole state.

## `maxResults` (type: `integer`):

A spend cap for the whole run, across states. Events past it are not lost: they stay pending and come in the next run.

## Actor input object example

```json
{
  "states": [
    "VA"
  ],
  "events": [],
  "tradeKeywords": [],
  "cities": [],
  "zips": [],
  "monitorId": "default",
  "maxResults": 1000
}
```

# Actor output Schema

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

One row per event (new licence, status, expiry, address or phone change, removal), licence attached.

# 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 = {
    "states": [
        "VA"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapebench/contractor-license-change-monitor").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 = { "states": ["VA"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapebench/contractor-license-change-monitor").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "states": [
    "VA"
  ]
}' |
apify call scrapebench/contractor-license-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapebench/contractor-license-change-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2CFp5waAh78dBvP7h/builds/zljY8qYrkAdE97Q3Z/openapi.json
