# Texas PUC Docket & Filings Monitor (PUCT Interchange) (`texas-data-feeds/texas-puc-docket-monitor`) Actor

Daily index of new Public Utility Commission of Texas filings (rate cases, tariffs, projects) with keyword, party, item-type and docket filters. Metadata + links only.

- **URL**: https://apify.com/texas-data-feeds/texas-puc-docket-monitor.md
- **Developed by:** [Texas Data Feeds](https://apify.com/texas-data-feeds) (community)
- **Categories:** Developer tools, Lead generation, News
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

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

## Texas PUC Docket & Filings Monitor (PUCT Interchange)

Every new filing at the **Public Utility Commission of Texas** (rate cases, tariff revisions, CCN applications, rulemaking projects, and compliance reports for electric, water, and telecom utilities) delivered daily as clean JSON, CSV, or Excel. You can filter by keyword, filing party, item type, utility type, or the specific docket (control) numbers you watch. It's built for energy and water attorneys, retail electric providers, consultants, utilities tracking competitors, and trade press.

**Legal status (Scout review, 2026-11-04): CLEAR WITH CONDITIONS.** This actor indexes **metadata only** (docket number, item, type, date, party, description) and **links** to the official filing and document pages on PUCT Interchange. It never downloads, stores, or resells filed documents, which may contain third-party copyrighted material. It touches only public, non-confidential listings.

### Output (`record_type: puct_filing`)

`control_number`, `item_number`, `item_type`, `date_filed`, `utility_type_code` / `utility_type`, `filing_party`, `description`, `docket_url` (all items in the docket), `documents_url` (the item's document list on PUCT), `source_url`, `scraped_at`.
When the filters match nothing, the actor returns one `puct_no_match` record with the number of filings scanned, so scheduled runs never look broken.

### Input

| Field | Default | Meaning |
|---|---|---|
| `daysBack` | 1 | Used when `dateFrom` is empty |
| `dateFrom` / `dateTo` | — | YYYY-MM-DD; the window can be at most 31 days |
| `utilityType` | all | all, electric, water, telephone, or others |
| `keywords` | \[] | Matched against the description and party, e.g. `["rate case","tariff","solar"]` |
| `filingParties` | \[] | e.g. `["Oncor","CenterPoint"]` |
| `itemTypes` | \[] | e.g. `["TARF","PRJ"]` |
| `controlNumbers` | \[] | Docket numbers to watch |
| `maxPages`, `maxItems`, `requestDelaySecs` | 20, 0, 3 | Politeness and size limits |

Tests run on 2026-11-04:

- All filings for 11/3/2026 returned 238 items.
- Water tariffs (`TARF`) from 10/26 to 11/3 scanned 856 filings and returned 27 items.

### Data source & credit

- **Source: Public Utility Commission of Texas.** [PUCT Interchange Daily Filing Search](https://interchange.puc.texas.gov/search/daily/). The same listings are free to search at that link. Filings are public records under the Texas Public Information Act.
- **What you pay for:** daily automation, normalized fields, multi-filter alerting, and integrations (webhooks, Sheets, Slack). You are not paying for the documents, which stay free on PUCT's site.
- This actor is not affiliated with or endorsed by the PUCT. No agency logo is used.

### Pricing (pay-per-event, suggested)

- `apify-actor-start`: $0.005
- `result`: $0.002 per filing after your filters. A daily watch on a few keywords (about 5–30 hits) costs about $0.02–0.07/day.
- A full statewide day (about 240 filings) costs about $0.49.

### Etiquette

1–2 requests per run (robots check plus results, which arrive as one page even for a week). The actor enforces a minimum 3 s gap, an honest User-Agent, and backoff on 403/429. Schedule it at most a few times a day.

### Disclaimer

Provided "as is" with no warranty of accuracy, completeness, or timeliness. This is not an official PUCT record. Always rely on the official docket on PUCT Interchange for legal deadlines and filings.

### Run locally

`python3 -m venv .venv && .venv/bin/pip install -r requirements.txt jsonschema && .venv/bin/python validate.py`

# Actor input Schema

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

Days back (if no dateFrom)

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

Date filed from (YYYY-MM-DD)

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

Date filed to (YYYY-MM-DD)

## `utilityType` (type: `string`):

Utility type

## `keywords` (type: `array`):

Keywords (description or party)

## `filingParties` (type: `array`):

Filing party contains

## `itemTypes` (type: `array`):

Item types (e.g. TARF, PRJ, APPLICATION)

## `controlNumbers` (type: `array`):

Watch these control (docket) numbers

## `maxPages` (type: `integer`):

Max result pages

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

Max items (0 = no limit)

## `requestDelaySecs` (type: `integer`):

Delay between requests (s)

## Actor input object example

```json
{
  "daysBack": 1,
  "utilityType": "all",
  "keywords": [],
  "filingParties": [],
  "itemTypes": [],
  "controlNumbers": [],
  "maxPages": 20,
  "maxItems": 0,
  "requestDelaySecs": 3
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset with all output records

# 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("texas-data-feeds/texas-puc-docket-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("texas-data-feeds/texas-puc-docket-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 '{}' |
apify call texas-data-feeds/texas-puc-docket-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,texas-data-feeds/texas-puc-docket-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/vQ48c6xOgXqXgeziQ/builds/03QnVOixIcM9fBayh/openapi.json