Weekly pipeline

How it works

A weekly digest of material changes in the USDA FSIS MPI establishment directory — immutable snapshots, before/after evidence, disclosed limits.

Weekly collection healthy · last run Aug 24, 2026

Live backend stats · stats.json

Audience

Who it's for

Vendor research and sales-ops teams who sell into USDA FSIS-inspected meat and poultry plants — packaging, processing equipment, sanitation, refrigeration, labeling, and food-safety software.

You get

A weekly CSV + email of material directory changes with before/after evidence and optional vendor-fit tags (heuristics, not purchase intent).

You don't get

A scraped lead list, a CRM, or a claim that a plant is buying. See accuracy limitations.

Delivery

What you get each week

After FSIS publishes an updated establishment directory, you receive adds, removals, and meaningful field updates — each with archived before/after values and a content hash for the official file used.

Pipeline

Five steps. Every publish.

  1. Fetch

    Download the full establishment list from the official FSIS MPI API. Failed or partial downloads are rejected — never treated as empty.

  2. Archive

    Store an immutable snapshot with a SHA256 content hash. Each file is dated and never overwritten.

  3. Normalize

    Canonicalize establishment identities, activities, and addresses so diffs are comparable week over week.

  4. Diff

    Generate typed change events with materiality scoring and optional vendor-fit tags.

  5. Deliver

    Email + CSV report to subscribers. Accuracy limitations always disclosed.

What it is

  • SourceUSDA FSIS MPI
  • CadenceWeekly
  • CoverageFederal MPI
  • EvidenceSHA256 + diff

What it isn't

  • Purchase intentNo
  • State-only plantsNo
  • Real-timeNo
  • Credit / financialNo

Live snapshot provenance

From our most recent successful collect — not simulated data

  • Fetched (UTC)2026-08-21T18:36:28.042Z
  • Establishments7,235
  • States & territories56
  • Change events vs prior0
  • Very Small / Small / Large2,978 / 2,915 / 518
  • API fields mapped20 (0 unmapped)
  • Duplicate establishment IDs0
  • Pipeline tests44 passing
  • Content SHA256 c4b0bc29b554d23cb60fc04f05a5f0966b59ada105607bb66b86618ee432990e

Why zero changes? One baseline snapshot on file. Weekly diffs start after the next official FSIS publish. · Live stats JSON

Change types we detect

  • AddedNew establishment in directory
  • RemovedNo longer listed (may be admin)
  • ReinstatedReturned after removal
  • Field updatesName, address, size, activities, species

Removals need review. A directory removal does not always mean a plant closed — it can reflect grant changes, consolidation, or FSIS corrections.

Safety guards

  • Failed fetchFail-closed — no alert
  • Partial payloadRejected
  • Abnormal mass removalBlocked
  • Schema driftFingerprint alarm
Support