# CARB LCFS Fuel Pathway Portfolio Status Monitor (`plym-actor-factory/us-carb-lcfs-fuel-pathway-status-monitor`) Actor

Watch CARB LCFS fuel pathway IDs and emit typed CERTIFIED/RETIRED/APPEARED/DROPPED/CI events from the official Current Fuel Pathways spreadsheet. Pay only for unique pathway status events on your book — not an ENERGY STAR or GHGRP twin billed as rows.

- **URL**: https://apify.com/plym-actor-factory/us-carb-lcfs-fuel-pathway-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** Automation, AI, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 lcfs pathway status event 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?

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

## CARB LCFS Fuel Pathway Portfolio Status Monitor

Watch a **book of CARB LCFS fuel pathway IDs** (App/Pathway #) and emit typed portfolio events when a pathway **appears/drops** on the certified table, is marked **RETIRED**, or has a material **CI / classification / FPC** change — using the official CARB Current Fuel Pathways spreadsheet.

**Not** an ENERGY STAR twin. **Not** an EPA GHGRP twin. **Not** a national LCFS dump billed as rows.

### Who this is for

- LCFS fuel producers / marketers tracking counterparty pathway books
- Pathway consultants and CI desks monitoring certified-table membership and CI flips
- Compliance / credit desks that need Slack/JSON when a watched pathway retires or drops

### What you get

| Event | Meaning |
|-------|---------|
| `PATHWAY_CERTIFIED` | Watched pathway is CERTIFIED on the published table |
| `PATHWAY_RETIRED` | Watched pathway marked RETIRED (or dropped after certified) |
| `APPEARED` / `DROPPED` | Present ↔ absent directory membership signals |
| `CI_CHANGED` / `CLASS_CHANGED` / `FPC_CHANGED` / `FUEL_TYPE_CHANGED` | Optional attribute group |
| `RUN_STATUS` | Non-billable health row (always on success) |

### Source

- Official CARB Current Fuel Pathways spreadsheet: `https://ww2.arb.ca.gov/sites/default/files/classic/fuels/lcfs/fuelpathways/current-pathways_all.xlsx`
- Page: https://ww2.arb.ca.gov/resources/documents/lcfs-pathway-certified-carbon-intensities
- No API key. Live mode downloads the official workbook and diffs **only** watched pathway IDs — not a national dump bill.
- CARB CDN can be flaky (intermittent 503); the Actor retries with backoff.

### Pricing (PPE)

- Charge event: `lcfs-pathway-status-event-delivered`
- Target: **$0.02 / event** (~$20 / 1k) — configure on Apify after private push
- `RUN_STATUS`, baselines, duplicates, filtered rows: **$0**

### Default input (Store-safe)

`sourceMode=fixture` (default) succeeds with a non-billable `RUN_STATUS` and **does not** emit fabricated product events unless `emitFixtureDemoEvents=true`.

Production: set `sourceMode=live` and provide your pathway-ID watchlist.

#### PRODUCTION USE example

```json
{
  "pathwayIds": ["T1N-1734", "A016601", "B005001"],
  "sourceMode": "live",
  "signalGroups": ["directory", "status"],
  "resumeFromCheckpoint": true,
  "maxRunSeconds": 180,
  "maxEvents": 500
}
```

### Limitations (honest)

- Published **certified-table membership/fields** only — not LRT-CBTS account actions, not Executive Officer dockets beyond the workbook.
- CARB CDN may return HTTP 503; Actor retries/backoff. Workbook refresh lag vs administrative actions is possible.
- Lookup-table rows with App/Pathway # = `None` are indexed by Current Certified FPC when present.
- First observation per pathway stores baseline only (no charge).

### Legal

CARB public LCFS pathway certified carbon intensities table. Cite CARB + retrieval date. Default product fields are public pathway identity (App/Pathway #, FPC, class, CI, fuel type, company/facility).

# Actor input Schema

## `pathwayIds` (type: `array`):

CARB LCFS App/Pathway # values to monitor against the official Current Fuel Pathways spreadsheet (e.g. T1N-1734, A016601, B005001). Exact match after normalize. Invalid entries skipped with no charge. Not a national LCFS dump bill.

## `fuelPathwayIds` (type: `array`):

Optional alias for pathwayIds — same App/Pathway # keys, merged into the watchlist.

## `fuelPathwayCodes` (type: `array`):

Optional Current Certified Fuel Pathway Codes (FPC) merged into the watchlist (matched against the FPC column when App/Pathway # is absent).

## `signalGroups` (type: `array`):

Which change groups to evaluate: directory (APPEARED/DROPPED), status (PATHWAY\_CERTIFIED / PATHWAY\_RETIRED), attributes (CI / class / FPC / fuel type). Default: directory+status.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget (xlsx download+parse + diff). Raise if CARB CDN is slow/503.

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (does not include RUN\_STATUS).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume pathway snapshots and seen event\_uids from the default Key-Value Store.

## `sourceMode` (type: `string`):

fixture = Store/CI health default (no network; RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official CARB Current Fuel Pathways xlsx (no API key; retry/backoff on CDN 503).

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, if true push fabricated change events from local fixtures. Default false so Store daily auto-tests never emit fake LCFS events or charge lcfs-pathway-status-event-delivered.

## `asOfHint` (type: `string`):

Optional as\_of label for events / RUN\_STATUS. Defaults to workbook Last Updated / Last-Modified when live.

## `maxTotalChargeUsd` (type: `number`):

Optional soft budget hint for delivered change events.

## `pathwaysXlsxUrl` (type: `string`):

Optional override for the official CARB current-pathways\_all.xlsx URL.

## Actor input object example

```json
{
  "pathwayIds": [
    "T1N-1734",
    "A016601",
    "B005001"
  ],
  "signalGroups": [
    "directory",
    "status"
  ],
  "maxRunSeconds": 180,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, LCFS pathway coverage limits

# 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("plym-actor-factory/us-carb-lcfs-fuel-pathway-status-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("plym-actor-factory/us-carb-lcfs-fuel-pathway-status-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 plym-actor-factory/us-carb-lcfs-fuel-pathway-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/us-carb-lcfs-fuel-pathway-status-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/ocGom1PCLx4mfqWGG/builds/xitIbxsz7TSAM1hXj/openapi.json