# Texas Workers' Comp Non-Subscriber & X-Date Lead Monitor (`zinky_atelier/tx-workers-comp-xdate-monitor`) Actor

Extract Texas Workers' Compensation Non-Subscriber employers (TDI DWC Form-005) with Parent + Multi-Location rollup grouping, upcoming Insurance X-Date expiration filters, recent-filing alerts, city/ZIP targeting, and stateful deduplication for commercial P\&C, OccAcc, and ERISA brokers.

- **URL**: https://apify.com/zinky_atelier/tx-workers-comp-xdate-monitor.md
- **Developed by:** [Travis Burrows](https://apify.com/zinky_atelier) (community)
- **Categories:** Lead generation, Business, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $14.00 / 1,000 employer coverage & x-date leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Texas Workers' Comp Non-Subscriber & Insurance X-Date Lead Monitor (TDI DWC Form-005)

Extract and enrich **Texas Workers' Compensation Non-Subscriber employers** directly from official **Texas Department of Insurance (TDI) Division of Workers' Compensation (DWC) Form-005** filings (`data.texas.gov` Socrata API)—purpose-built for **commercial P\&C insurance brokers, Occupational Accident (OccAcc) & ERISA non-subscriber benefit wholesalers, TPAs, PEOs, and RevOps/Clay outbound teams**.

Unlike raw state CSV exports that scatter multi-store corporations across thousands of disconnected rows, this Actor performs **Parent + Multi-Location Rollup Grouping**: every branch `Location` record, Texas operating city, 5-digit ZIP code, and subsidiary DBA name is aggregated onto a single clean `Parent` employer lead alongside **Insurance X-Date countdowns** (`daysUntilExpiration`, `xDateStatus`).

Zero headless browsers. Zero proxy overhead. Native `SEEN_FILINGS` deduplication for daily/weekly cron pipelines and MCP AI agents.

***

### Why Texas Non-Subscriber & X-Date Intelligence?

Texas is the **only US state** where private-sector employers can legally opt out of standard statutory Workers' Compensation coverage ("non-subscribers"). Under **Texas Labor Code §406.005**, every non-subscribing employer must file **DWC Form-005** reporting their non-coverage period (`start_date` to `end_date`) and covered Texas operating locations.

| Commercial Buyer Persona | Automated Revenue Workflow |
| :--- | :--- |
| **Commercial P\&C & Workers' Comp Brokers** | Pull multi-location employers (`minLocations: 2`) whose `coverageEndDate` (X-Date) expires in **60–90 days** (`expiringWithinDays: 90`) to pitch statutory WC conversion or competitive renewal quotes right before policy decisions. |
| **Occupational Accident (OccAcc), Stop-Loss & ERISA Benefit Plans** | Monitor newly opted-out employers (`filedWithinDays: 14`, `onlyNew: true`) every Monday morning to offer compliant Texas Non-Subscriber employee injury benefit plans & Employer's Liability coverage. |
| **PEOs, TPAs & Workplace Safety Consultants** | Target high-headcount multi-site retail, logistics, hospitality, construction, and healthcare chains operating across Houston, Dallas-Fort Worth, Austin, and San Antonio. |
| **Clay.com / Make / n8n / AI SDR Pipelines** | Enrich each Parent employer with `companyName`, `dbaNames`, `hqAddress`, `texasCities`, and `locationCount` directly into Apollo/Clay contact discovery and HubSpot/Salesforce sequences. |

***

### Key Differentiators

1. **Parent + Multi-Location Rollup Grouping:** Aggregates child `Location` rows onto each `Parent` filing—surfacing `locationCount`, `isMultiLocation`, `cities`, `texasCities`, `states`, `zipCodes`, and distinct subsidiary `dbaNames` (while even matching out-of-state corporate headquarters that operate Texas branches!).
2. **Insurance X-Date Expiration Windows (`expiringWithinDays`):** Filter directly on `end_date` and segment urgency automatically (`expiring_30d`, `expiring_60d`, `expiring_90d`, `active_future`, `expired`).
3. **Recent Non-Subscriber Filing Alerts (`filedWithinDays`):** Capture brand-new DWC Form-005 submissions by `filing_date_received`.
4. **Cross-Location City, ZIP & Keyword Targeting:** Searching `cities: ["Austin"]` or `zipCodes: ["78701"]` matches employers whether Austin is their Parent HQ **or** one of their branch locations—then rolls up the entire company.
5. **Stateful `SEEN_FILINGS` Delta Deduplication (`onlyNew: true`):** Remembers previously delivered `filingId` + `coverageEndDate` pairs in persistent Key-Value storage so scheduled runs only emit new or renewed filings.

***

### Transparent Pay-Per-Event (PPE) Pricing

This Actor uses Apify's Pay-Per-Event billing model—you only pay for rolled-up Parent employer leads actually emitted (duplicates skipped via `onlyNew: true` are **never** charged):

| Event Name | Trigger | Suggested Store Price |
| :--- | :--- | :--- |
| `actor-start` | Charged once when the Actor run initializes | `$0.05` / run |
| `employer-lead` | Charged per rolled-up Parent employer lead pushed to the dataset | `$0.02` / employer lead |

***

### Input Configuration Guide

#### 1. Upcoming 90-Day X-Date Renewal Pipeline (Multi-Location Accounts)

```json
{
  "expiringWithinDays": 90,
  "filedWithinDays": 0,
  "cities": ["Houston", "Dallas", "Austin", "San Antonio"],
  "minLocations": 2,
  "onlyNew": true,
  "maxItems": 200
}
```

#### 2. Weekly Newly Filed Non-Subscriber Alerts

```json
{
  "expiringWithinDays": 0,
  "filedWithinDays": 14,
  "onlyNew": true,
  "maxItems": 100
}
```

***

### Realistic Sample Output Record

```json
{
  "filingId": "13445",
  "companyName": "Sk Wireless Group Inc",
  "hqAddress": "5309 Middleton Dr",
  "hqCity": "Parker",
  "hqState": "TX",
  "hqZipCode": "75002-3727",
  "hqZip5": "75002",
  "filingDateReceived": "2025-11-19",
  "coverageStartDate": "2025-11-19",
  "coverageEndDate": "2026-11-18",
  "daysUntilExpiration": 4,
  "daysSinceFiled": 360,
  "xDateStatus": "expiring_30d",
  "locationCount": 7,
  "reportedLocationRecords": 7,
  "isMultiLocation": true,
  "cities": ["Parker", "San Antonio"],
  "texasCities": ["Parker", "San Antonio"],
  "states": ["TX"],
  "zipCodes": ["75002", "78218", "78237"],
  "dbaNames": [],
  "locations": [
    {
      "companyName": "Sk Wireless Group Inc",
      "address": "131 Historic Old Hwy 90",
      "city": "San Antonio",
      "state": "TX",
      "zipCode": "78237-1529",
      "startDate": "2025-11-19",
      "endDate": "2026-11-18"
    }
  ],
  "locationsTruncated": false,
  "sourceDatasetUrl": "https://data.texas.gov/resource/azae-8krr.json?filing_id=13445",
  "scrapedAt": "2026-11-14T04:25:00.000Z"
}
```

***

### Automated Daily / Weekly Scheduling (Clay, Make, n8n & MCP)

1. Save an Actor Task with `expiringWithinDays: 90` (or `filedWithinDays: 7`) and `onlyNew: true`.
2. Attach an **Apify Schedule** (`0 7 * * 1` — Mondays at 7:00 AM CT) and connect your Clay webhook, Make/n8n scenario, or Slack channel.
3. Inspect `RUN_SUMMARY` in the Default Key-Value Store after every run for exact audit counts (`candidateFilingsEvaluated`, `employersEmitted`, `skippedDuplicateCount`, and `ppeEventsCharged`).

***

### How Much Does It Cost? (Tiered Pay-Per-Event Pricing)

Skipped duplicate filings in `onlyNew: true` mode cost `$0`. Paid Apify tiers automatically unlock lower per-employer lead rates:

| Event | One-Time? | Free Plan | Bronze | Silver | Gold / Enterprise |
| :--- | :---: | :---: | :---: | :---: | :---: |
| `actor-start` | Yes | `$0.05` | `$0.05` | `$0.05` | `$0.05` |
| `employer-lead` *(Primary)* | No | `$0.02` | `$0.018` | `$0.016` | `$0.014` |

#### Clay, Make, n8n & AI Agent (`mcp.apify.com`) Chaining

- **Clay.com Commercial P\&C & PEO Outbound:** Pipe rolled-up Texas parent employers, location counts, NAICS codes, and upcoming 30/60/90-day Form-005 X-Dates into Clay to enrich CFO/HR contacts automatically.
- **AI Agents & MCP (`mcp.apify.com`):** Query live Texas TDI DWC non-subscriber filings by city, ZIP, or expiration window directly from MCP-compatible insurance workflows.

# Actor input Schema

## `expiringWithinDays` (type: `integer`):

Keep filings whose non-coverage period `end_date` (annual renewal / X-Date) falls between today and today + N days (e.g. 60, 90, or 120 days ahead of renewal). Set to 0 to disable X-Date window filtering.

## `filedWithinDays` (type: `integer`):

Keep filings where TDI received DWC Form-005 (`filing_date_received`) within the last N days (e.g. 14 or 30 days for daily/weekly newly opted-out employer alerts). Set to 0 to disable.

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

Optional list of cities (case-insensitive, e.g. \['Austin', 'Houston', 'Dallas']). Matches employers whose Parent HQ OR any operating Location is in these cities, then rolls up the entire multi-location employer.

## `zipCodes` (type: `array`):

Optional list of 5-digit ZIP codes (e.g. \['78701', '77002']). Matches both 5-digit and ZIP+4 records across Parent HQ and child Locations.

## `companyName` (type: `string`):

Optional case-insensitive keyword filter on Parent company name or subsidiary/location DBA name (e.g. 'CONSTRUCTION', 'LOGISTICS', 'HEALTHCARE').

## `minLocations` (type: `integer`):

Filter for larger commercial accounts by requiring at least N covered locations on the rolled-up Parent employer (set 2+ for multi-location chains only).

## `onlyNew` (type: `boolean`):

When enabled, tracks emitted `filingId` + `coverageEndDate` signatures in persistent Key-Value Store (`SEEN_FILINGS`) so scheduled daily/weekly runs only push unseen or renewed employer leads.

## `maxItems` (type: `integer`):

Maximum number of rolled-up Parent employer leads to emit in this run.

## `maxLocationsPerEmployer` (type: `integer`):

Caps the embedded `locations[]` detail array per output item to keep JSON payloads compact for mega-chains, while `locationCount`, `cities`, `texasCities`, and `zipCodes` always aggregate 100% of locations.

## `socrataAppToken` (type: `string`):

Optional Texas Open Data Portal `X-App-Token` for higher rate-limit pools on very large multi-thousand-record batch runs.

## Actor input object example

```json
{
  "expiringWithinDays": 90,
  "filedWithinDays": 0,
  "cities": [],
  "zipCodes": [],
  "minLocations": 1,
  "onlyNew": false,
  "maxItems": 50,
  "maxLocationsPerEmployer": 25
}
```

# Actor output Schema

## `employerLeads` (type: `string`):

Rolled-up Parent employer dataset with locationCount, cities, X-Date countdown, and subsidiary DBA names.

## `runSummary` (type: `string`):

JSON summary of query filters, upstream rows processed, deduplication skips, and PPE billing 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 = {
    "expiringWithinDays": 90,
    "filedWithinDays": 0,
    "cities": [],
    "zipCodes": [],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinky_atelier/tx-workers-comp-xdate-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 = {
    "expiringWithinDays": 90,
    "filedWithinDays": 0,
    "cities": [],
    "zipCodes": [],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("zinky_atelier/tx-workers-comp-xdate-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 '{
  "expiringWithinDays": 90,
  "filedWithinDays": 0,
  "cities": [],
  "zipCodes": [],
  "maxItems": 50
}' |
apify call zinky_atelier/tx-workers-comp-xdate-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zinky_atelier/tx-workers-comp-xdate-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/Kd7jt24wjQraHKLfq/builds/kHXdyjl007z6BznwN/openapi.json
