# Texas TCEQ Industrial Air Quality Permit Leads (NSR & Title V) (`zinky_atelier/tceq-air-quality-permit-leads`) Actor

Extract pending and completed Texas industrial Air Quality Permit filings (NSR Construction, PBR, Standard Permits, and Title V Operating Permits) from the official TCEQ Air Permits IMS database—enriched with facility technical names, equipment rules, fees, and review milestones.

- **URL**: https://apify.com/zinky_atelier/tceq-air-quality-permit-leads.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 $28.00 / 1,000 tceq air permit 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 TCEQ Industrial Air Quality Permit Leads (NSR & Title V)

Extract newly filed and completed **Texas industrial Air Quality Permits**—including **New Source Review (NSR)** construction permits, **Permits by Rule (PBR)**, **Standard Permits**, and **Title V Federal Operating Permits (SOP / GOP)**—directly from the official Texas Commission on Environmental Quality (TCEQ) Air Permits IMS database.

Built with pure lightweight HTTP (`256 MB` RAM, zero headless browsers, zero residential proxy overhead) for **daily scheduled B2B lead pipelines** (`onlyNew: true`), **Clay / Make / n8n enrichment**, and **AI MCP agents**.

***

### Why Texas Air Quality Permits Are High-Intent Industrial Leads

Before any chemical plant, refinery, LNG terminal, data center backup generator fleet, concrete batch plant, coating facility, or midstream compressor station in Texas can install or modify emission-producing equipment, it must submit an **NSR or Title V Air Permit application** to TCEQ—months before equipment commissioning.

Unlike raw search tables that only show generic labels like `"PBR NEW REGISTRATION"`, this Actor optionally enriches every project's official **TCEQ Project Report** (`enrichProjectDetails: true`) to uncover:

- **Actual Facility / Plant Technical Name** (`siteName`, e.g., `EXXONMOBIL CHEMICAL BAYTOWN CHEMICAL PLANT`)
- **Equipment & Unit Rule Descriptions** (`unitRules`, e.g., `BOILERS, HEATERS, AND OTHER COMBUSTION DEVICES`, `SURFACE COAT FACILITY`, `DRY ABRASIVE CLEANING`)
- **TCEQ Identifiers** (`cnNumber`, `regulatedEntityNumber` RN, `accountNumber`, `permitNumber`, `projectNumber`)
- **Application Fee Amounts Paid** (`feeAmountPaid`) & **Assigned Review Engineers / Milestones** (`primaryReviewer`, `assignedStaff`, `trackingMilestones`)

| B2B Buyer Persona | Automated Workflow |
| :--- | :--- |
| **Air Pollution Control, Scrubber, Thermal Oxidizer & CEMS Vendors** | Trigger daily Slack/CRM alerts on `INITIAL` and `AMEND` NSR filings across Gulf Coast & Permian counties (`HARRIS`, `JEFFERSON`, `BRAZORIA`, `NUECES`, `MIDLAND`, `ECTOR`). |
| **Stack Testing, LDAR & Environmental Engineering Consultants** | Track `PENDING` and newly `COMPLETE` NSR & Title V permits with equipment rule breakdowns (`106.261`, `106.262`, `106.183`, `116.110`). |
| **Industrial EPCs, Mechanical Subcontractors & Power/Generator Suppliers** | Enrich newly registered industrial sites in Clay.com using company `legalName`, `physicalLocation`, and `siteName`. |
| **Commercial Environmental & Energy Insurance Brokers** | Monitor facility expansions and Title V operating permit renewals across all 254 Texas counties. |

***

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

| Event Name | When Charged | Description |
| :--- | :--- | :--- |
| `actor-start` | Once per run | Base run initialization and TCEQ session setup. |
| `permit-lead` | Per emitted dataset item | Charged **only** for net-new leads pushed to your dataset (skipped duplicates under `onlyNew: true` are **never** charged). |

***

### Input Parameters

| Parameter | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `counties` | `string[]` | `["HARRIS"]` | Texas county names (e.g., `["HARRIS", "JEFFERSON", "MIDLAND", "TRAVIS"]`) or `["ANY"]` for statewide queries. |
| `programAreas` | `string[]` | `["NSR"]` | `"NSR"` (Construction, PBR, Standard Permits) and/or `"TITLEV"` (Federal Operating Permits). |
| `statuses` | `string[]` | `["PENDING"]` | `"PENDING"` (active applications under review) and/or `"COMPLETE"` (completed permit actions). |
| `companyName` | `string` | `""` | Optional company/customer name prefix (e.g., `"EXXON"`, `"EQUISTAR"`). |
| `permitType` | `string` | `""` | Optional permit type filter (e.g., `"CONSTRUCT"`, `"PBR"`, `"STDPMT"`, `"SOP"`). |
| `projectType` | `string` | `""` | Optional action type filter (e.g., `"INITIAL"`, `"AMEND"`, `"REVISION"`, `"RENEWAL"`). |
| `receivedWithinDays` | `integer` | `0` | Keep only filings received within the last `N` days (`0` returns all matching pending filings). |
| `enrichProjectDetails` | `boolean` | `true` | Fetch each project's TCEQ Project Report for plant technical name, air account ID, fees, staff, and unit rules. |
| `onlyNew` | `boolean` | `false` | Deduplicate across scheduled runs via persistent `SEEN_PROJECTS` Key-Value Store state. |
| `maxItems` | `integer` | `25` | Maximum permit leads to emit per run (`1`–`5000`). |

***

### Example Input (Daily Gulf Coast & Permian Lead Feed)

```json
{
  "counties": ["HARRIS", "JEFFERSON", "BRAZORIA", "MIDLAND"],
  "programAreas": ["NSR", "TITLEV"],
  "statuses": ["PENDING"],
  "receivedWithinDays": 14,
  "enrichProjectDetails": true,
  "onlyNew": true,
  "maxItems": 100
}
```

### Example Output Record

```json
{
  "projectKey": "NSR:417365:185926",
  "programArea": "NSR",
  "rawProgramCode": "NSR",
  "projectNumber": "417365",
  "permitNumber": "185926",
  "permitType": "PBR",
  "permitStatus": "PENDING",
  "projectType": "INITIAL",
  "projectStatus": "PENDING",
  "projectName": "PBR NEW REGISTRATION",
  "siteName": "EXXONMOBIL CHEMICAL BAYTOWN CHEMICAL PLANT",
  "customerName": "EXXON MOBIL CORPORATION",
  "legalName": "Exxon Mobil Corporation",
  "cnNumber": "CN600123939",
  "regulatedEntityNumber": "RN102574803",
  "accountNumber": "HG0229F",
  "physicalLocation": "5000 BAYWAY DR",
  "city": "BAYTOWN",
  "county": "HARRIS",
  "region": "REGION 12 - HOUSTON",
  "state": "TX",
  "receivedDate": "2026-11-13",
  "completeDate": null,
  "renewalDate": null,
  "issuedDate": null,
  "rules": ["106.261", "106.262"],
  "detailEnriched": true,
  "primaryReviewer": "REVIEW ENG: TEAM LEADER, RR",
  "technicalContact": null,
  "assignedStaff": ["REVIEW ENG: TEAM LEADER, RR"],
  "feeAmountPaid": 450,
  "unitRules": [
    {
      "unitDescription": "FACILITIES (EMISSION AND DISTANCE LIMITATIONS)",
      "ruleCode": "106.262",
      "approved": true
    }
  ],
  "trackingMilestones": [],
  "projectReportUrl": "https://www2.tceq.texas.gov/airperm/index.cfm?fuseaction=airpermits.project_report&proj_id=417365",
  "scrapedAt": "2026-11-14T04:25:00.000Z"
}
```

***

### Automated Scheduling & Webhook Integration (Clay / Make / n8n)

1. Create a saved **Apify Task** with your target `counties`, `programAreas: ["NSR", "TITLEV"]`, `statuses: ["PENDING"]`, and `onlyNew: true`.
2. Attach an **Apify Schedule** (e.g., `0 7 * * 1-5` every weekday morning) and connect a **Webhook** to Clay, Make, n8n, Slack, or HubSpot.
3. Every run checks `SEEN_PROJECTS` in persistent Key-Value storage—emitting and billing **only** when brand-new Texas air permit filings appear.

***

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

Zero monthly subscription—skipped duplicates in `onlyNew: true` mode are never charged, and paid Apify tiers unlock automatic volume discounts:

| Event | One-Time? | Free Plan | Bronze | Silver | Gold / Enterprise |
| :--- | :---: | :---: | :---: | :---: | :---: |
| `actor-start` | Yes | `$0.02` | `$0.02` | `$0.02` | `$0.02` |
| `permit-lead` *(Primary)* | No | `$0.04` | `$0.036` | `$0.032` | `$0.028` |

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

- **Clay.com Industrial Account Enrichment:** Chain `customerName` and `siteName` into Clay to identify EHS directors, plant managers, and EPC leads on newly filed Texas NSR and Title V air permits.
- **AI Agents & MCP (`mcp.apify.com`):** Query pending Texas industrial air permits, generator banks, and chemical plant expansions in structured JSON/CSV or via MCP tool calling.

# Actor input Schema

## `counties` (type: `array`):

One or more Texas county names (e.g. \['HARRIS', 'JEFFERSON', 'MIDLAND', 'TRAVIS']) or \['ANY'] for statewide search.

## `programAreas` (type: `array`):

TCEQ air permit program areas to query: 'NSR' (New Source Review construction, PBR, Standard Permits) and/or 'TITLEV' (Title V Federal Operating Permits).

## `statuses` (type: `array`):

Filter by TCEQ project review status ('PENDING' for active applications under review, 'COMPLETE' for completed permit actions).

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

Optional company/customer name prefix filter (e.g. 'EXXON', 'EQUISTAR', 'ENTERPRISE').

## `permitType` (type: `string`):

Optional permit type code (e.g. 'CONSTRUCT', 'PBR', 'STDPMT', 'FLEXIBLE G' for NSR; 'SOP', 'GOP', 'TOP' for Title V).

## `projectType` (type: `string`):

Optional project action type (e.g. 'INITIAL', 'AMEND', 'REVISION', 'RENEWAL').

## `receivedWithinDays` (type: `integer`):

Restrict to permit applications received by TCEQ within the last N days. Set to 0 to return all matching projects (note: COMPLETE queries automatically default to 90 days when left at 0 unless overridden via dateFrom/dateTo).

## `enrichProjectDetails` (type: `boolean`):

Fetch each project's official TCEQ Project Report page to extract facility technical name, air account ID, assigned review engineers, fee amounts paid, equipment unit rules, and tracking milestones.

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

Persist seen project keys in Key-Value Store ('SEEN_PROJECTS') so scheduled daily/hourly runs only emit and charge for brand-new permit filings.

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

Maximum total number of permit lead records to emit in this run.

## Actor input object example

```json
{
  "counties": [
    "HARRIS",
    "JEFFERSON"
  ],
  "programAreas": [
    "NSR",
    "TITLEV"
  ],
  "statuses": [
    "PENDING"
  ],
  "receivedWithinDays": 0,
  "enrichProjectDetails": true,
  "onlyNew": false,
  "maxItems": 25
}
```

# Actor output Schema

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

Normalized dataset of pending and completed NSR & Title V air quality permit filings.

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

JSON summary of counties, program areas, statuses queried, deduplicated counts, and PPE event charges.

# 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 = {
    "counties": [
        "HARRIS",
        "JEFFERSON"
    ],
    "programAreas": [
        "NSR",
        "TITLEV"
    ],
    "statuses": [
        "PENDING"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinky_atelier/tceq-air-quality-permit-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 = {
    "counties": [
        "HARRIS",
        "JEFFERSON",
    ],
    "programAreas": [
        "NSR",
        "TITLEV",
    ],
    "statuses": ["PENDING"],
}

# Run the Actor and wait for it to finish
run = client.actor("zinky_atelier/tceq-air-quality-permit-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 '{
  "counties": [
    "HARRIS",
    "JEFFERSON"
  ],
  "programAreas": [
    "NSR",
    "TITLEV"
  ],
  "statuses": [
    "PENDING"
  ]
}' |
apify call zinky_atelier/tceq-air-quality-permit-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zinky_atelier/tceq-air-quality-permit-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/I9Ulydhv3iGHWWSF9/builds/8jbCUVvNXVHPwcZua/openapi.json
