# California DIR Public Works & Prevailing Wage Leads (`zinky_atelier/ca-dir-public-works-leads`) Actor

Extract newly awarded California DIR Public Works projects (PWC-100) and registered Prevailing Wage contractors (PWCR) with contract values, awarding agency emails, contractor emails, business phones, and trade crafts via lightweight HTTP/JSON.

- **URL**: https://apify.com/zinky_atelier/ca-dir-public-works-leads.md
- **Developed by:** [Travis Burrows](https://apify.com/zinky_atelier) (community)
- **Categories:** Lead generation, Business, Real estate
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 public works project 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

## California DIR Public Works Projects (PWC-100) & Prevailing Wage Contractors (PWCR) Leads

Extract newly awarded **California Public Works projects (`PWC-100`)** and active **Prevailing Wage Registered Contractors (`PWCR`)** directly from the official California Department of Industrial Relations (DIR) ServiceNow Portal—complete with **contract dollar values, awarding body agency filer emails, contractor emails, business phone numbers, DBA names, and registered trade crafts**.

Built with **pure HTTP/JSON** (`256 MB` RAM, zero headless browsers, zero residential proxy costs) for **daily scheduled delta feeds** (`onlyNew: true`), **Clay / Make / n8n B2B outbound pipelines**, and **AI MCP agents**.

***

### Why California DIR PWC-100 & PWCR Data?

Under California Labor Code § 1773.3, public agencies (school districts, universities, cities, counties, water districts, transit authorities, and Caltrans) must file a **PWC-100 Project Award Notice** with DIR within 30 days of contract award, and every prime or subcontractor bidding or working on public works over $25,000 ($15,000 for maintenance) must hold an active **PWCR Registration**.

| B2B Buyer Persona | Automated Workflow |
| :--- | :--- |
| **Equipment Rental, Materials & Site Services** | Schedule daily `mode: "projects"` runs filtered by California `county` (`Los Angeles`, `San Diego`, `Orange`, `Santa Clara`) and `onlyNew: true` to alert reps as soon as public works contracts are awarded. |
| **Surety Bond, Commercial Insurance & Prevailing Wage Payroll/Compliance SaaS** | Schedule daily `mode: "contractors"` runs with `daysBack: 7` and `onlyNew: true` to capture newly registered PWCR contractors with **direct email, phone, president name, business structure, and trade crafts**. |
| **Specialty Subcontractors (Solar, Electrical, Roofing, HVAC, Concrete)** | Filter `keyword: "solar"` or `"roofing"` across `660,000+` DIR project filings and `140,000+` PWCR contractors into Clay, HubSpot, or Salesforce. |
| **AI Agents via Apify MCP (`mcp.apify.com`)** | Instantly verify a contractor's PWCR registration status, expiration date, and registered crafts or research public agency capital spending. |

***

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

You only pay for records actually emitted to your dataset. Previously seen records skipped via `onlyNew: true` are **never billed**.

| Event Name | Trigger | Description |
| :--- | :--- | :--- |
| `actor-start` | Once per run | Base initialization & CA DIR ServiceNow session bootstrap. |
| `project-lead` | Per emitted project | Charged for each normalized PWC-100 Public Works project record written to the dataset. |
| `contractor-record` | Per emitted contractor | Charged for each normalized PWCR Prevailing Wage contractor record written to the dataset. |

***

### Input Guide

| Parameter | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `mode` | `'projects' \| 'contractors' \| 'both'` | `'both'` | Extract awarded `PWC-100` projects, registered `PWCR` contractors, or both. |
| `keyword` | `string` | `""` | Trade, scope, or company keyword (e.g. `"solar"`, `"electric"`, `"roofing"`, `"HVAC"`). |
| `county` | `string` | `""` | California county filter for PWC-100 projects (e.g. `"Los Angeles"`, `"San Diego"`). |
| `city` | `string` | `""` | Job site city (projects) or mailing/physical city (contractors). |
| `zipCode` | `string` | `""` | 5-digit ZIP code filter for projects and contractors. |
| `status` | `string` | `'active_approved'` | `'active_approved'`, `'approved'`, `'pending'`, `'completed_or_expired'`, or `'all'`. |
| `daysBack` | `integer` | `0` | Rolling recency window in days (e.g. `7` or `30` for scheduled monitoring). |
| `dateFrom` / `dateTo` | `string` | `""` | Explicit ISO `YYYY-MM-DD` date bounds. |
| `onlyNew` | `boolean` | `false` | Stateful deduplication via persistent KV record `SEEN_RECORDS` across scheduled runs. |
| `maxItems` | `integer` | `20` | Maximum total items to emit (`1`–`5000`). |

#### Copy-Paste Example Input (Daily Scheduled Lead Feed)

```json
{
  "mode": "both",
  "keyword": "electric",
  "county": "Los Angeles",
  "status": "active_approved",
  "daysBack": 30,
  "onlyNew": true,
  "maxItems": 100
}
```

***

### Sample Output Records

#### 1. Awarded Public Works Project (`recordType: "project"`)

```json
{
  "recordType": "project",
  "recordKey": "project:20260663525",
  "sourceId": "20260663525",
  "sysId": "814dfc29c3e017100c17b7ff05013122",
  "title": "Emergency Repairs to Building 114",
  "status": "Approved",
  "statusCode": "20",
  "streetAddress": "Kearney Research and Extension Center, 9240 S Riverbend Ave",
  "city": "Parlier",
  "county": "Fresno",
  "state": "CA",
  "zipCode": "93648",
  "projectNumber": "7632 KREC",
  "contractNumber": "7632-A KREC",
  "description": "7632-A KREC, Emergency Repairs to Building 114",
  "projectType": "Design",
  "awardingBody": "University of California ANR",
  "filerContactEmail": "vkovacevic@ucanr.edu",
  "totalCostUsd": 145000,
  "contractAmountUsd": 49500,
  "estimatedTotalCostUsd": 0,
  "awardDate": "2026-10-27",
  "contractDate": "2026-11-08",
  "firstAdvertisedBidDate": "2026-10-05",
  "startDate": null,
  "estimatedStartDate": "2026-11-10",
  "endDate": null,
  "estimatedEndDate": "2027-02-05",
  "associatedPla": false,
  "operateLcp": false,
  "filedAt": "2026-11-13T18:23:50Z",
  "pwcrNumber": null,
  "legalName": null,
  "doingBusinessAs": null,
  "presidentName": null,
  "businessStructure": null,
  "email": null,
  "businessPhone": null,
  "cslbLicense": null,
  "caSosEntityNumber": null,
  "crafts": [],
  "registrationStartDate": null,
  "registrationEndDate": null,
  "physicalAddress": null,
  "portalUrl": "https://services.dir.ca.gov/pw?id=dir_public_form&table=x_cdoi2_csm_portal_project&sys_id=814dfc29c3e017100c17b7ff05013122",
  "scrapedAt": "2026-11-14T04:20:00.000Z"
}
```

#### 2. Registered Prevailing Wage Contractor (`recordType: "contractor"`)

```json
{
  "recordType": "contractor",
  "recordKey": "contractor:2000039379",
  "sourceId": "2000039379",
  "sysId": "527bc86947205b508a1ad69b416d43c2",
  "title": "MWG Electric",
  "status": "DIR Approved",
  "statusCode": "dir_approved",
  "streetAddress": "18400 Beach Blvd",
  "city": "Huntington Beach",
  "county": null,
  "state": "CA",
  "zipCode": "92648",
  "projectNumber": null,
  "contractNumber": null,
  "description": null,
  "projectType": null,
  "awardingBody": null,
  "filerContactEmail": null,
  "totalCostUsd": null,
  "contractAmountUsd": null,
  "estimatedTotalCostUsd": null,
  "awardDate": null,
  "contractDate": null,
  "firstAdvertisedBidDate": null,
  "startDate": null,
  "estimatedStartDate": null,
  "endDate": null,
  "estimatedEndDate": null,
  "associatedPla": null,
  "operateLcp": null,
  "filedAt": null,
  "pwcrNumber": "2000039379",
  "legalName": "Mike W. Gilday",
  "doingBusinessAs": "MWG Electric",
  "presidentName": "Mike W. Gilday",
  "businessStructure": "Sole Proprietorship",
  "email": "accounting@mwgelectric.com",
  "businessPhone": "(909) 912-4297",
  "cslbLicense": "1098412",
  "caSosEntityNumber": null,
  "crafts": ["Electrician"],
  "registrationStartDate": "2026-11-13",
  "registrationEndDate": "2027-06-30",
  "physicalAddress": "18400 Beach Blvd, Huntington Beach, CA, 92648",
  "portalUrl": "https://services.dir.ca.gov/pw?id=dir_public_form&table=x_cdoi2_csm_portal_customer_account_lookup&sys_id=527bc86947205b508a1ad69b416d43c2",
  "scrapedAt": "2026-11-14T04:20:00.000Z"
}
```

***

### Zero-Touch Scheduled Automation (Clay / Make / n8n / Slack)

1. Save a Task in Apify Console with `onlyNew: true`, `daysBack: 14`, and your target `mode`, `county`, or `keyword`.
2. Attach an **Apify Schedule** (e.g. `0 6 * * 1-5` — weekdays at 6:00 AM PT) and a **Webhook** pointing to Clay, Make, n8n, or Slack.
3. Inspect `RUN_SUMMARY` in the Default Key-Value Store for full telemetry (`upstreamMatchingProjects`, `upstreamMatchingContractors`, `skippedDuplicateCount`, and `ppeEventsCharged`).

***

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

Zero monthly subscription—pay only for new records emitted (`$0` for skipped duplicates in `onlyNew: true` mode), with automatic Apify tier discounts:

| Event | One-Time? | Free Plan | Bronze | Silver | Gold / Enterprise |
| :--- | :---: | :---: | :---: | :---: | :---: |
| `actor-start` | Yes | `$0.02` | `$0.02` | `$0.02` | `$0.02` |
| `project-lead` *(Primary)* | No | `$0.03` | `$0.027` | `$0.024` | `$0.02` |
| `contractor-record` | No | `$0.015` | `$0.0135` | `$0.012` | `$0.01` |

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

- **Clay.com / Outbound CRM:** Stream PWC-100 project awards and PWCR contractor emails/phones into Clay, Smartlead, or HubSpot for surety bond, equipment rental, and prevailing-wage payroll outreach.
- **AI Agents & MCP (`mcp.apify.com`):** Let autonomous GTM agents search California public works awards and active CSLB/PWCR contractors in real time via JSON/CSV or MCP tool calls.

# Actor input Schema

## `mode` (type: `string`):

Choose whether to extract awarded PWC-100 Public Works projects ('projects'), registered PWCR Prevailing Wage contractors ('contractors'), or both in a single run ('both').

## `keyword` (type: `string`):

Optional trade, scope, company, or craft keyword (e.g. 'solar', 'roofing', 'electric', 'HVAC', 'paving'). Matches project name/description/number or contractor legal name/DBA/crafts.

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

Optional California county name for PWC-100 projects (e.g. 'Los Angeles', 'San Diego', 'Orange', 'Santa Clara', 'Sacramento').

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

Optional city name filter applied to project job site city or contractor mailing/physical city (e.g. 'San Jose', 'Fresno', 'Huntington Beach').

## `zipCode` (type: `string`):

Optional 5-digit ZIP code filter applied to project job site ZIP or contractor mailing/physical ZIP.

## `status` (type: `string`):

Filter by DIR record lifecycle status: 'active_approved' (Approved/Active PWC-100 projects & DIR Approved PWCR contractors), 'approved', 'pending', 'completed_or_expired', or 'all'.

## `daysBack` (type: `integer`):

When > 0 (e.g. 7 or 30), keeps only PWC-100 projects filed/awarded or PWCR contractors registered within the last N days. Leave 0 to return newest matching records without a rolling window.

## `dateFrom` (type: `string`):

Optional lower-bound ISO date (YYYY-MM-DD) applied to project filing/award date or contractor registration start date.

## `dateTo` (type: `string`):

Optional upper-bound ISO date (YYYY-MM-DD) applied to project filing/award date or contractor registration start date.

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

When enabled, tracks emitted project & contractor IDs in persistent Key-Value Store record `SEEN_RECORDS` so daily/hourly scheduled runs emit and bill only brand-new leads.

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

Maximum total records to emit in this run (split across projects and contractors when mode='both').

## Actor input object example

```json
{
  "mode": "both",
  "keyword": "",
  "status": "active_approved",
  "daysBack": 30,
  "onlyNew": false,
  "maxItems": 50
}
```

# Actor output Schema

## `leads` (type: `string`):

Normalized dataset of awarded PWC-100 projects and registered PWCR prevailing-wage contractors.

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

JSON summary of extraction counts, upstream matches, skipped duplicates, and PPE events charged.

## `seenRecords` (type: `string`):

Snapshot of seen record IDs used for delta deduplication across scheduled runs.

# 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 = {
    "mode": "both",
    "keyword": "",
    "daysBack": 30,
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinky_atelier/ca-dir-public-works-leads").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 = {
    "mode": "both",
    "keyword": "",
    "daysBack": 30,
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("zinky_atelier/ca-dir-public-works-leads").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 '{
  "mode": "both",
  "keyword": "",
  "daysBack": 30,
  "maxItems": 50
}' |
apify call zinky_atelier/ca-dir-public-works-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zinky_atelier/ca-dir-public-works-leads"
        }
    }
}
```

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/wrBe314Xm6Fmfw5Fd/builds/D10UvRdMwpc973qoe/openapi.json
