# USDA FSIS MPI Est# Portfolio Status Monitor (`plym-actor-factory/us-fsis-mpi-est-status-monitor`) Actor

Watch FSIS establishment numbers and emit typed APPEARED/DROPPED\_OR\_INACTIVE/ACTIVITIES\_CHANGED/SIZE\_CHANGED/GRANT\_DATE\_CHANGED events from the official USDA FSIS MPI Directory JSON API/CSV. Not nationwide leads dump; not recall feed; not HTML scrape.

- **URL**: https://apify.com/plym-actor-factory/us-fsis-mpi-est-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** AI, Automation, 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 fsis mpi est# 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

## USDA FSIS MPI Establishment Number Portfolio Status Event Monitor

Watch a book of **FSIS establishment numbers** and emit typed directory status/activity events when the official **USDA FSIS Meat, Poultry and Egg Product Inspection (MPI) Directory** shows an establishment **appearing**, **leaving the active directory** (inactive/drop), or **materially changing activities / size / grant\_date**.

**Not** a nationwide FSIS leads dump. **Not** an FSIS recall ticker. **Not** HTML scrape of the FSIS map UI. **Not** unpaid food-safety SaaS scrape.

### Coverage honesty (Est# matching + directory cadence)

- **Source:** Official FSIS MPI Directory JSON `https://www.fsis.usda.gov/fsis/api/establishments/mpi` (primary). Documented CSV alternate supported as optional fallback. Optional inactive MPI CSV used best-effort for drop confirmation (often Akamai-gated from some egress).
- **Keys:** Prefer exact `establishment_number` match; `establishment_id` is a secondary key.
- **Cadence:** MPI publish is typically **weekly** (not intra-day). Absence from the active directory should be cross-checked against inactive-file semantics when available — this Actor states that honestly in event summaries.
- **Fields:** Activities, size, and grant\_date are mapped faithfully from FSIS directory fields (no invented statuses).

### Events

| Event | When |
|-------|------|
| `FSIS_EST_APPEARED` | Watched Est# missing → present on active directory |
| `FSIS_EST_DROPPED_OR_INACTIVE` | Watched Est# present → missing (optionally confirmed on inactive file) |
| `FSIS_ACTIVITIES_CHANGED` | Activities fingerprint changed while still present |
| `FSIS_SIZE_CHANGED` | Size field changed while still present |
| `FSIS_GRANT_DATE_CHANGED` | Grant date changed while still present |
| `RUN_STATUS` | Non-billable health row every successful run |

First observation of an Est# stores a **baseline only** (no product charge).

### Modes

- **`sourceMode=fixture`** (default): Store health / CI. With `emitFixtureDemoEvents=false` (default) emits **only** `RUN_STATUS` / `FIXTURE_HEALTH` → **0** product charges.
- **`sourceMode=live`**: Official FSIS MPI JSON API (**no API key**). One directory pull, then in-memory filter to the watchlist — does **not** bill national rows.

### Pricing (Model A)

- `fsis-mpi-est-status-event-delivered` @ **$0.02** / unique delivered event
- `apify-actor-start` @ **$0.00005**
- Quiet books ≈ $0 product charge

### Input

See `.actor/input_schema.json`. Primary field: `establishmentNumbers`. Optional `establishmentIds`, `signalGroups`: `directory`, `activities`, `size`, `grant_date`.

### Legal

**GREEN** — USDA/FSIS MPI Directory published for public reuse. Cite FSIS + retrieval date. Default product fields = establishment\_number + establishment\_id + name + activities/size/grant\_date + address (business facility data; no consumer PII).

### A1b wedge

Establishment-number watchlist × scheduled official MPI API/CSV snapshot diff → typed directory status/activity events only for the book. Existing Store shelf is FSIS leads dump / recall scrapers (wrong job). See `opportunity/reports/phase3-a1b-next3-v11.md` (#1 PASS → build #29).

### Private

`isPublic` must remain **false** for this launch.

# Actor input Schema

## `establishmentNumbers` (type: `array`):

FSIS establishment numbers (e.g. M123+P123) to monitor against the official USDA FSIS MPI Directory. Invalid entries are skipped with no charge. Not a nationwide dump — only Est#s on the book are evaluated.

## `establishmentIds` (type: `array`):

Optional secondary FSIS establishment\_id keys merged into the watchlist.

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

Which change groups to evaluate: directory (APPEARED/DROPPED\_OR\_INACTIVE), activities, size, grant\_date. Default: all.

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

Wall-clock budget for the run (directory fetch + 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 establishment snapshots and seen event\_uids from the default Key-Value Store.

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

fixture = local/CI / Apify Store daily auto-test default (no network; emits RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official FSIS MPI Directory JSON API (no API key).

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

When sourceMode=fixture, if true push fabricated change events from local fixtures (unit/local demos only). Default false so Store daily auto-tests never emit fake FSIS events or charge fsis-mpi-est-status-event-delivered. Production: leave false and use sourceMode=live. SAMPLE rows only: demo events use placeholder entities (never real companies/IDs), are flagged sample=true / isSample=true, and are NEVER charged.

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

Optional as\_of label for events / RUN\_STATUS. Defaults to LatestMPIActiveDate from the directory when present.

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

Optional soft budget hint for delivered change events. Platform ACTOR\_MAX\_TOTAL\_CHARGE\_USD also applies when set.

## `mpiApiUrl` (type: `string`):

Optional override for the official FSIS MPI establishments JSON API. Default: https://www.fsis.usda.gov/fsis/api/establishments/mpi

## `inactiveCsvUrl` (type: `string`):

Optional inactive-establishments CSV for drop confirmation (best-effort; often Akamai-gated).

## Actor input object example

```json
{
  "establishmentNumbers": [
    "M13561+P13561",
    "M7067+P7067",
    "M1633+P17764+V1633"
  ],
  "signalGroups": [
    "directory",
    "activities",
    "size",
    "grant_date"
  ],
  "maxRunSeconds": 55,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

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

JSON summary: delivered, charged, runStatus, checkpoint, stats, FSIS MPI 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-fsis-mpi-est-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-fsis-mpi-est-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-fsis-mpi-est-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-fsis-mpi-est-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/qhJlFuel2fLtyxhQH/builds/Ik1WPkONEWUwRVsa0/openapi.json