# Federal Register Rules and Notices Monitor (`transparent_meteorite/federal-register-rules-notices-monitor`) Actor

Federal Register monitor for new federal rules, proposed rules and regulatory notices from the free Federal Register API: agencies, effective and comment dates, abstract, CFR references, significance and an impact score. No login, no proxy, no personal data.

- **URL**: https://apify.com/transparent_meteorite/federal-register-rules-notices-monitor.md
- **Developed by:** [Detroit Web Agent - Open Data](https://apify.com/transparent_meteorite) (community)
- **Categories:** News, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 document rows

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

## Federal Register Rules and Notices Monitor

**Federal Register rules and notices monitor**: new US federal rules, proposed rules and notices from the free Federal Register API, one row each with agencies, effective and comment-close dates, abstract, CFR references, the significant-rule flag and an impact score.

Pull the newest US federal rules, proposed rules and notices into a clean table. Each row has the document number, title, type, agencies, publication, effective and comment-close dates, abstract, CFR references, the significant-rule flag, page count, HTML and PDF links, docket IDs and a simple impact and urgency score. Data comes from the free public Federal Register API. No login, no proxy, no personal data.

### What is Federal Register Rules and Notices Monitor?

Get new US federal rules, proposed rules and notices from the free Federal Register API: agencies, effective and comment dates, abstract, CFR references, significance and an impact score. No login, no proxy, no personal data. Run it from the Apify Console, the API or a schedule, and export the results as JSON, CSV, Excel or HTML.

### Why use it

- **Official source.** Data is the Federal Register as published through its public API.
- **One table.** Rules, proposed rules and notices in the same shape, with ISO dates.
- **Repeatable.** Fixed filters and a fixed score, so runs can be compared week to week.

### Output

One row per Federal Register document:

| Field | Meaning |
|---|---|
| `documentNumber` | The Federal Register document number. |
| `title`, `abstract` | Document title and the agency summary. |
| `documentType` | Rule, Proposed Rule or Notice. |
| `agencies` | Issuing agencies. |
| `publicationDate`, `effectiveDate`, `commentsCloseDate` | Key dates (ISO format). |
| `daysToCommentDeadline`, `daysToEffective` | Days from today (negative if past, empty if no date). |
| `cfrReferences` | Affected Code of Federal Regulations parts, for example `40 CFR 257`. |
| `significant` | Whether the document is flagged as a significant rule (true, false or empty when not stated). |
| `pageCount` | Pages in the Federal Register. |
| `htmlUrl`, `pdfUrl` | Links to the official page and PDF. |
| `docketIds` | Agency docket identifiers where given. |
| `impactScore` | 0 to 100, see below. |
| `scrapedAt` | When the run read the data. |

### Sample output

```json
{
  "documentNumber": "2026-21622",
  "title": "Coal Combustion Residuals; State Permit Program Approval",
  "documentType": "Rule",
  "agencies": ["Environmental Protection Agency"],
  "publicationDate": "2026-10-22",
  "effectiveDate": "2026-11-23",
  "commentsCloseDate": null,
  "cfrReferences": ["40 CFR 257"],
  "significant": null,
  "pageCount": 9,
  "docketIds": ["EPA-HQ-OLEM-2025-3325"],
  "impactScore": 0
}
```

### Input

| Field | What it does |
|---|---|
| `documentTypes` | `rule`, `proposed rule`, `notice`. Default: rule and proposed rule. |
| `daysBack` | Keep documents published in the last N days. Default 14. |
| `searchTerm` | Optional full-text search term. |
| `agencies` | Optional agency slugs, for example `environmental-protection-agency`. |
| `significantOnly` | Keep only documents marked significant. |
| `openCommentPeriodOnly` | Keep only documents whose comment period has not closed. |
| `minImpactScore` | Optional 0 to 100 threshold. |
| `maxItems` | Stop after this many rows (newest first). Default 100. |

Sample input:

```json
{
  "documentTypes": ["proposed rule"],
  "daysBack": 30,
  "searchTerm": "cybersecurity",
  "openCommentPeriodOnly": true,
  "maxItems": 50
}
```

### Pricing

Pay per event. You pay a small fixed amount per document row delivered, listed on the Pricing tab, plus a tiny start fee per run. You can set a maximum cost per run in the run options.

### What does this Actor do?

It reads the Federal Register documents endpoint (`federalregister.gov/api/v1/documents.json`) for the publication window you choose, merges the pages into one list and sorts it newest first. By default it returns final rules and proposed rules from the last 14 days. You can add notices, narrow by agency, search by term, keep only significant documents or only documents whose comment period is still open. The actor reports what the Federal Register publishes. It does not give legal advice.

**Run in 30 seconds**

1. Open the Actor and press **Try for free** (a free Apify account is enough).
2. Keep the prefilled input (rules and proposed rules, last 14 days) and press **Start**. A run takes under a minute.
3. Open the **Output** tab. Use the table view or download CSV, Excel or JSON.

### Use cases

- Send compliance, legal or government-affairs teams a weekly list of new rules and proposed rules that touch their sector.
- Track open comment periods and get the deadlines in a spreadsheet so nobody misses a chance to comment.
- Watch specific agencies or topics (a search term such as "emissions" or "drug pricing") and push matches into Slack, email or a ticket system with n8n, Make or Zapier.
- Build a regulatory newsletter, dashboard or research dataset on rulemaking volume by agency and CFR title.

### Impact score

A fixed rule of thumb, not an official rating: 40 if the document is flagged significant, plus up to 40 for an open comment deadline (40 when it closes today, falling to 0 at 30 days out), plus up to 15 for an effective date within the next 30 days, plus 5 for documents of 50 pages or more. Capped at 100. The same document gives the same score on the same day.

### Limits

- Covers documents published in the Federal Register. State rules and unpublished agency guidance are not included.
- Notices are numerous (hundreds per day); use `maxItems`, `agencies` or `searchTerm` to keep runs small.
- This is information, not legal advice.

### Related Actors

- [Developer Signals](https://apify.com/transparent_meteorite/developer-signals) tracks public developer activity signals for companies.
- [Website Tech Stack](https://apify.com/transparent_meteorite/website-tech-stack) detects which technologies a website runs on.
- [Sitemap Link Inventory](https://apify.com/transparent_meteorite/sitemap-link-inventory) lists every URL a site publishes in its sitemaps.
- [CFPB Consumer Complaints Monitor](https://apify.com/transparent_meteorite/cfpb-consumer-complaints-monitor): new consumer complaints by company, product and state from the CFPB database.
- [NPI New Provider Enrollment Monitor](https://apify.com/transparent_meteorite/npi-new-provider-enrollment-monitor): newly enrolled healthcare organizations from the NPPES NPI registry.

Found a bug or need a field? Open an issue on the Issues tab with the run URL.

### FAQ

**How fresh is the data?**
The Federal Register publishes each business day; new documents typically appear in the API the same day. Public inspection documents not yet published are not included.

**Why do I get fewer rows than maxItems?**
Only documents inside your window and matching your filters exist. Try a larger `daysBack` or remove filters.

**Is this an official government product?**
No. It is an independent tool that reads the public Federal Register API. Check federalregister.gov for the authoritative text.

**Did this actor do the job?** If it saved you time, a short honest review on the [Reviews tab](https://apify.com/transparent_meteorite/federal-register-rules-notices-monitor/reviews) helps other people judge it. If something was off, open an Issue on this page with the input you used. I read every one and fix real bugs, usually the same day.

**This Actor vs benthepythondev/federal-register-intelligence:** that one also tracks comment periods and agency activity in its own format. Choose this one for one flat table of rules, proposed rules and notices with ISO dates, CFR references, the significant-rule flag and a fixed impact and urgency score.

### Changelog

- 2026-10-22: Initial release.
- 2026-10-25: Documentation updated: README refreshed.
- 2026-10-25: Listing refresh: new Store icon, README reorganised (overview, data fields, pricing, FAQ) and changelog tab added. No code change.

# Changelog

This Actor's version history is a separate document: https://apify.com/transparent_meteorite/federal-register-rules-notices-monitor/changelog.md

# Actor input Schema

## `documentTypes` (type: `array`):

Which Federal Register document types to read. Leave empty for final rules and proposed rules.

## `daysBack` (type: `integer`):

Keep documents published in the last N days.

## `searchTerm` (type: `string`):

Optional full-text search, for example "cybersecurity" or "emissions".

## `agencies` (type: `array`):

Optional agency slugs from federalregister.gov/agencies, for example environmental-protection-agency or food-and-drug-administration.

## `significantOnly` (type: `boolean`):

Turn on to keep only documents the agency marks as significant.

## `openCommentPeriodOnly` (type: `boolean`):

Turn on to keep only documents whose public comment period has not closed yet.

## `minImpactScore` (type: `integer`):

Optional 0 to 100. Keep only rows at or above this score.

## `maxItems` (type: `integer`):

Stop after this many rows, newest first. You pay only for rows delivered.

## Actor input object example

```json
{
  "documentTypes": [
    "rule",
    "proposed rule"
  ],
  "daysBack": 14,
  "significantOnly": false,
  "openCommentPeriodOnly": false,
  "minImpactScore": 0,
  "maxItems": 100
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# 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 = {
    "documentTypes": [
        "rule",
        "proposed rule"
    ],
    "daysBack": 14,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("transparent_meteorite/federal-register-rules-notices-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 = {
    "documentTypes": [
        "rule",
        "proposed rule",
    ],
    "daysBack": 14,
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("transparent_meteorite/federal-register-rules-notices-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 '{
  "documentTypes": [
    "rule",
    "proposed rule"
  ],
  "daysBack": 14,
  "maxItems": 100
}' |
apify call transparent_meteorite/federal-register-rules-notices-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,transparent_meteorite/federal-register-rules-notices-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/DJsGSGpwQlVOgtgbm/builds/kVKPY1YvFMiFzbqc9/openapi.json