# State PUC Rate Case Tracker (Oregon + Texas) (`kevinserver24/puc-rate-case-tracker`) Actor

Currently open electric and gas utility rate-case dockets from Oregon and Texas, classified out of thousands of raw filings per state and normalized into one schema. Fetched live on every run. Charged only per docket delivered.

- **URL**: https://apify.com/kevinserver24/puc-rate-case-tracker.md
- **Developed by:** [Kevin](https://apify.com/kevinserver24) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$100.00 / 1,000 docket delivereds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## State PUC Rate Case Tracker (Oregon + Texas)

*An independent tool. It is not affiliated with, endorsed by, or operated by
the Oregon Public Utility Commission or the Public Utility Commission of
Texas. Both commissions publish their docket records as a matter of public
record (Oregon: ORS Chapter 192; Texas: Texas Government Code Chapter 552,
the "Open Records Act," cited on the PUCT's own privacy page). This Actor
reads each commission's public docket-search system and reports what it
returns, classified and reshaped into one schema.*

**Live per run, not a cache.** Every run fetches both states' docket search
systems fresh — a rate case moves through filing, hearing and order over
months, and a snapshot taken once goes stale as soon as the next filing
lands.

***

### Why this exists

Oregon's own "open dockets" search returns **over 3,000 rows** — but only a
small fraction are actual rate cases. 62% are routine tariff "advice"
filings and another 8% are miscellaneous administrative dockets, both
technically "open" and neither a rate case a consultant or law firm cares
about. Texas has no equivalent flag at all: its docket search returns every
filing in a date window, mixing real company rate cases with recurring
agency compliance buckets filed under names like "PUC RATE REGULATION" that
are not a company at all. This Actor filters both down to genuine electric
and gas rate/tariff proceedings — Oregon by its own docket-type code (`UE`,
`UG`), Texas by a classifier built and tested against real filing captions —
so you get a short, current list instead of thousands of rows to sort
through by hand, or two different state portals to check separately.

### What you get per row

| Field | Meaning |
|---|---|
| `state` | `OR` or `TX` |
| `commission` | The full commission name |
| `docket_number` | The state's own docket/control number |
| `case_type`, `case_type_label` | `ue`/`ug` (Oregon) or `rate_case` (Texas), with a human-readable label |
| `case_title` | The docket's own filed caption |
| `utility` | The utility company that filed |
| `filed_date` | When the docket was opened, where the source provides it |
| `order_date`, `final_order_number` | Oregon only — populated once a final order issues; always `null` for a currently open docket, since an open docket by definition has none yet |
| `filing_count_recent` | Texas only — how many filings landed on this docket within the search window |
| `is_closed` | `false` for every Oregon row (this Actor only asks Oregon for OPEN dockets), `null` for Texas (its search carries no open/closed flag at all) |
| `source_url` | A direct link to the commission's own record, to verify |
| `charged` | Whether this row cost you anything |
| `not_charged_reason` | Why it did not, in plain English |

### The billing rule, stated plainly

One event: **docket delivered**, charged once per unique docket in the
result. A docket that shows up again on a later run (because a new filing
landed on it) is charged again — the same way a news feed charges again for
a story that develops further, not a duplicate of the first charge.

### Coverage — read this before you rely on it

**v1 covers two states: Oregon (electric and gas rate cases, `UE`/`UG`) and
Texas (electric and gas, keyword-classified).** Texas Water utilities are
deliberately excluded: several rate-case filers there are individuals doing
business under a company name, and this Actor does not emit a docket if the
filer's name could be a natural person's. Pennsylvania, Hawaii and other
states are not yet covered — Hawaii's docket search in particular requires a
full browser to render at all. `SUMMARY.json` in the run's key-value store
reports exactly which states were requested and which were actually fetched
on that run.

***

### Input

```json
{
  "states": ["OR", "TX"]
}
```

Leave `states` empty to check both. Invalid or unsupported codes are
ignored; if nothing valid is given, both supported states are checked.

### Output

```json
{
  "state": "OR",
  "commission": "Oregon Public Utility Commission",
  "docket_number": "UE 473",
  "case_type": "ue",
  "case_type_label": "electric rate/tariff case",
  "case_title": "PORTLAND GENERAL ELECTRIC COMPANY REQUEST FOR A GENERAL RATE REVISION",
  "utility": "PORTLAND GENERAL ELECTRIC COMPANY",
  "filed_date": "8/4/2026",
  "order_date": null,
  "final_order_number": null,
  "filing_count_recent": null,
  "is_closed": false,
  "source_url": "https://apps.puc.state.or.us/edockets/docket.asp?DocketID=25142",
  "charged": true,
  "not_charged_reason": ""
}
```

A `SUMMARY.json` lands in the key-value store with which states were
requested and fetched, how many dockets were found, and a breakdown of
charged vs. free rows.

# Actor input Schema

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

Which state PUC to check for currently open electric/gas rate-case dockets. Leave empty to check both. More states are planned -- see the README for coverage and why only two exist today.

## Actor input object example

```json
{
  "states": [
    "OR",
    "TX"
  ]
}
```

# Actor output Schema

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

One row per docket: state, commission, docket number, case type, filing utility, filed date, and a link back to the commission's own record.

## `resultsCsv` (type: `string`):

The same rows as a spreadsheet.

## `summary` (type: `string`):

Which states were requested and actually fetched, how many dockets were found, charged and free.

# 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": [
        "OR",
        "TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kevinserver24/puc-rate-case-tracker").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": [
        "OR",
        "TX",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("kevinserver24/puc-rate-case-tracker").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": [
    "OR",
    "TX"
  ]
}' |
apify call kevinserver24/puc-rate-case-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kevinserver24/puc-rate-case-tracker"
        }
    }
}

```

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/7Fwu7tP4OxFEryl0l/builds/4HfDAmr3wy9buXFgX/openapi.json