# EPA PPIS Registration Number Status Monitor (`plym-actor-factory/us-epa-ppis-registration-number-status-monitor`) Actor

Watch EPA pesticide Registration Numbers and emit typed ACTIVE/CANCELLED/APPEARED/DROPPED events from the official weekly PPIS XML zip. Not Safer Choice twin; not TSCA Inventory twin; not TRI twin; not a national PPIS dump billed as rows.

- **URL**: https://apify.com/plym-actor-factory/us-epa-ppis-registration-number-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 ppis registration 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

## EPA PPIS Registration Number Status Monitor

Watch a **book of EPA pesticide Registration Numbers** and emit typed portfolio events when a product flips between published **PPIS ACTIVE ↔ CANCELLED** lists (or appears/drops), using the official weekly EPA PPIS XML zip.

**Not** a Safer Choice twin. **Not** a TSCA Inventory CASRN twin. **Not** a TRI facility twin. **Not** a national PPIS dump billed as rows.

### What you get

| Event | Meaning |
|-------|---------|
| `PPIS_ACTIVE` | Watched Reg. No. moved onto the published Section 3 ACTIVE XML |
| `PPIS_CANCELLED` | Watched Reg. No. moved onto the published CANCELLED XML |
| `APPEARED` / `DROPPED` | Present ↔ absent on the published ACTIVE/CANCELLED files |
| `SIGNALWORD_CHANGED` / `RUP_CHANGED` | Optional attribute group |
| `RUN_STATUS` | Non-billable health row (always on success) |

### Source

- Official EPA PPIS XML zip: https://www3.epa.gov/pesticides/PPISdata/PPIS-XML.zip
- Download page: https://www.epa.gov/ingredients-used-pesticide-products/ppis-download-product-information-data
- Cadence: weekly (EPA uploads Monday evenings)
- No API key. Optional `includeSection24c` for FIFRA 24(c) SLN numbers.

### Pricing (PPE)

- Charge event: `ppis-registration-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 Registration Number watchlist.

### Limitations (honest)

- Published PPIS ACTIVE/CANCELLED membership only — not full OPP docket mailers, not label PDF OCR, not state 24(c) unless enabled.
- Weekly lag vs EPA Monday upload.
- First observation per Reg. No. stores baseline only (no charge).

### Legal

EPA public PPIS data. Cite EPA PPIS + retrieval date. Default product fields are public registration identity data.

# Actor input Schema

## `registrationNumbers` (type: `array`):

EPA pesticide Registration Numbers to monitor against official weekly PPIS Section 3 ACTIVE/CANCELLED XML (e.g. 3-24 or 000003-00024). Exact match after normalize. Invalid entries skipped with no charge. Not a national PPIS dump bill.

## `epaRegNumbers` (type: `array`):

Optional alias for registrationNumbers — same EPA Reg. No. keys, merged into the watchlist.

## `includeSection24c` (type: `boolean`):

If true, also parse SEC24C ACTIVE/CANCELLED XML entries (state Special Local Need numbers). Default false — Section 3 federal products only.

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

Which change groups to evaluate: directory (APPEARED/DROPPED), status (ACTIVE↔CANCELLED), attributes (signal word / RUP). Default: directory+status.

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

Wall-clock budget (PPIS XML zip download + stream parse + watchlist diff).

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

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

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

If true, resume Registration Number 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 EPA weekly PPIS XML zip (no API key).

## `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 PPIS events or charge ppis-registration-status-event-delivered.

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

Optional as\_of label for events / RUN\_STATUS. Defaults to date inferred from PPIS XML filename when present (e.g. 09-21-2026 → 2026-09-21).

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

Optional soft budget hint for delivered change events.

## `ppisXmlZipUrl` (type: `string`):

Optional override for the official EPA PPIS-XML.zip URL.

## Actor input object example

```json
{
  "registrationNumbers": [
    "3-24",
    "3-18",
    "1-8512"
  ],
  "includeSection24c": false,
  "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, PPIS Registration Number 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-epa-ppis-registration-number-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-epa-ppis-registration-number-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-epa-ppis-registration-number-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-epa-ppis-registration-number-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/MdQ2v0FEA28vDbFeQ/builds/rsVViFbNVaoXbeYcn/openapi.json