Federal Register Rule Change Watch

Run daily or weekly. Pay only for newly seen Federal Register rules or notices that match your keywords or agencies.

buyer wedge

Built for compliance teams, policy analysts, and industry associations who need a narrow regulatory-change feed—not another bulk document dump.

why it is different

• signal, not retrieval: unmatched Federal Register documents are omitted and free.
• agency filtering: exact or phrase match against issuing agency names.
• correction-aware: a materially changed source record emits SOURCE_CORRECTION once.
• replay-safe: stable event IDs and provider idempotency keys suppress duplicate charges.
• bounded spend: maxEvents and maxTotalChargeUsd cap each run before charging.
• audit evidence: every row includes the official document number, citation, source fingerprint, timestamp, and disclaimer.

price example: four new rules plus one material source correction cost $0.65; unmatched and unchanged documents cost $0.00.

source and scope

The Actor queries the official Federal Register API for RULE or NOTICE documents within a rolling publication-date window. No API key, browser, proxy, personal data, or AI inference is required. This Actor is an internal screening aid and emits new or corrected documents; it does not provide legal advice or claim regulatory interpretation.

matching

At least one watch term is required:

• keywords: phrase match against rule titles and abstracts
• agencies: exact or phrase match against issuing agency names
• documentTypes: optional filter (RULE for final/proposed rules, NOTICE for notices)

baselineMode=emit_matches returns matching documents in the initial lookback window. Use silent to establish state without emitting or charging initial matches. Reuse the same watchlistId, settings, and stateStoreName for scheduled monitoring.

output

Paid dataset rows are either:

• NEW_RULE — $0.15
• SOURCE_CORRECTION — $0.05

Unmatched documents, unchanged replays, silent baselines, malformed input, and failed source fetches are not paid events. A deterministic run report is stored as REPORT with source window, counts, receipts, state size, and claim scope.

operational note

If the Federal Register API returns an error or an unexpected response shape, the run fails before state is advanced or events are charged. Event settlement is fail-closed: an ambiguous prior settlement refuses another provider charge.

quick start

Start with a silent baseline so historical documents do not create paid events, then schedule the identical input daily or weekly.

{
  "watchlistId": "regulatory-watch-epa",
  "keywords": ["clean air act", "emission standards"],
  "agencies": ["EPA"],
  "documentTypes": ["RULE"],
  "lookbackDays": 14,
  "baselineMode": "silent",
  "maxEvents": 20,
  "maxTotalChargeUsd": 5,
  "stateStoreName": "regulatory-watch-epa-state"
}

After the baseline, keep watchlistId, watch terms, and stateStoreName stable. Route returned NEW_RULE rows to a compliance review queue. Confirm every action against the linked Federal Register source; this feed is deliberately not a legal-advice or regulatory-interpretation system.

Other focused monitors: FDA food recall matches, 8-K material events, and drug safety signals.