# Federal Register Monitor Pro (`red.cars/federal-register-monitor-pro`) Actor

Every new federal rule, proposed rule, notice, and executive order from the Federal Register as clean one-row-per-document output. Full-text search, agency filters, date windows, comment deadlines, and president and signing date on orders.

- **URL**: https://apify.com/red.cars/federal-register-monitor-pro.md
- **Developed by:** [AutomateLab](https://apify.com/red.cars) (community)
- **Categories:** News, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

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 Monitor Pro

Track every new federal rule, proposed rule, notice, and executive order from the U.S. Federal Register as clean, structured rows. Filter by document type, agency, and date window, search full text, and get comment deadlines so a public comment period never closes on you unnoticed.

**Why this one**: the only other Federal Register actors on Apify have one or two users each, no public reviews, and none updated this fall. Federal Register Monitor Pro covers all four document types with date windows, agency filtering, comment deadlines, CFR citations, docket IDs, and executive-order details.

### Features

- All four document types: final rules (RULE), proposed rules (PRORULE), notices (NOTICE), and presidential documents (PRESDOCU, including executive orders)
- Full-text search across titles and document text
- Agency filtering by slug: environmental-protection-agency, federal-communications-commission, food-and-drug-administration, and hundreds more
- Any date window, defaulting to the last 7 days
- Comment-deadline column so you can catch public comment periods before they close
- Executive-order details: president and signing date
- CFR citations, docket IDs, regulation ID numbers, and links to the HTML, PDF, and plain-text versions

### Input

| Field | Type | Description |
|---|---|---|
| documentTypes | array | RULE, PRORULE, NOTICE, PRESDOCU. Empty for all types. |
| searchTerm | string | Full-text search term. Empty for everything matching the other filters. |
| agencies | array | Agency slugs. Empty for all agencies. |
| dateFrom | string | YYYY-MM-DD. Empty defaults to the last 7 days. |
| dateTo | string | YYYY-MM-DD. Empty defaults to today. |
| limit | integer | Max documents per run, 1 to 5000. Default 50. |

### Output

Each row is one Federal Register document: documentNumber, title, type, publicationDate, citation, agencies, abstract, commentsCloseOn, htmlUrl, pdfUrl, bodyHtmlUrl, rawTextUrl, president, signingDate, docketIds, topics, cfrReferences, volume, startPage, endPage, commentDates, regulationIdNumbers, and significant.

### Pricing

Pay per event: $0.005 per run + $2.00 per 1,000 documents. You pay nothing for platform usage.

### Use cases

- Compliance and regulatory-affairs teams watching the agencies that matter to them
- Law firms and government-affairs shops tracking rulemaking on client issues
- Journalists and researchers covering federal policy
- Grant writers and contractors scanning for funding notices and open opportunities
- Policy analysts building feeds of executive orders and significant rules

### FAQ

**How current is the data?** Documents appear as the Federal Register publishes them, typically the morning of publication.

**Can I track a single agency?** Yes, pass one or more agency slugs and leave the search term empty.

**How do I track executive orders?** Set documentTypes to PRESDOCU. Rows include the president and signing date.

**What is commentsCloseOn?** The date the public comment period closes on documents accepting comments.

**Is there a cap?** Up to 5,000 documents per run.

# Actor input Schema

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

Which Federal Register document types to pull: RULE (final rules), PRORULE (proposed rules), NOTICE (notices), PRESDOCU (presidential documents including executive orders). Leave empty for all types.

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

Full-text search across titles and document text, e.g. artificial intelligence, data privacy, PFAS. Leave empty to pull everything matching the other filters.

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

Filter by agency slugs such as environmental-protection-agency, federal-communications-commission, food-and-drug-administration. Leave empty for all agencies.

## `dateFrom` (type: `string`):

Earliest publication date, YYYY-MM-DD. Leave empty to default to the last 7 days.

## `dateTo` (type: `string`):

Latest publication date, YYYY-MM-DD. Leave empty to default to today.

## `limit` (type: `integer`):

Hard cap on documents returned per run, 1 to 5000.

## Actor input object example

```json
{
  "documentTypes": [
    "RULE"
  ],
  "limit": 50
}
```

# Actor output Schema

## `results` (type: `string`):

Link to the dataset of Federal Register document records

# 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"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("red.cars/federal-register-monitor-pro").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"] }

# Run the Actor and wait for it to finish
run = client.actor("red.cars/federal-register-monitor-pro").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"
  ]
}' |
apify call red.cars/federal-register-monitor-pro --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,red.cars/federal-register-monitor-pro"
        }
    }
}
```

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/2ncwLMaFVgcKgMehI/builds/iODvLe27kalkEOPgz/openapi.json