# 🏛️ Federal Register Comment Deadline Monitor (`snuggly_beanie_970/federal-rule-comment-deadlines`) Actor

🏛️ Never miss a US federal public-comment window. 🎯 Monitor deadlines by agency, keyword, document type, significance and rolling date range. ✅ Official Federal Register API, CFR/docket metadata, PDF links and schedule-ready alerts.

- **URL**: https://apify.com/snuggly\_beanie\_970/federal-rule-comment-deadlines.md
- **Developed by:** [Ilia](https://apify.com/snuggly_beanie_970) (community)
- **Categories:** Business, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 comment deadlines

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 🏛️ Federal Register Comment Deadline Monitor

Automatically find US federal rules and notices whose public-comment periods are closing soon. Unlike a generic Federal Register scraper, this Actor produces a deadline-ready feed with rolling date windows, days remaining, agency identifiers, RINs, CFR references, citations, significance flags, and official source links.

Use it for regulatory intelligence, compliance calendars, public-policy research, trade associations, legal operations, journalism, and AI-agent workflows.

### Why use this Actor

- **Schedule-ready:** `daysAhead` automatically moves the search window every day; no dates need to be edited.
- **Deadline focused:** every paid row has a public-comment closing date.
- **Useful filters:** agency slugs, keywords, document types, and significant documents only.
- **Verification links:** records link to official FederalRegister.gov HTML, PDF, raw text, and JSON when available.
- **No proxy or external API subscription:** data comes from the official FederalRegister.gov API.

### Example input for daily monitoring

```json
{
  "daysAhead": 30,
  "includePastDays": 0,
  "query": "artificial intelligence",
  "agencies": [],
  "documentTypes": ["PRORULE", "NOTICE"],
  "significantOnly": false,
  "maxItems": 100
}
```

For a historical or fixed window, provide both `deadlineFrom` and `deadlineTo` in `YYYY-MM-DD` format. Fixed dates override the rolling window.

### 📤 Output fields

| Group | Fields |
| --- | --- |
| Deadline | `commentsCloseOn`, `daysRemaining`, `effectiveOn` |
| Document | `documentNumber`, `documentTitle`, `documentType`, `documentSubtype`, `publicationDate`, `action`, `abstract` |
| Regulatory identifiers | `citation`, `docketIds`, `regulationIdNumbers`, `cfrReferences`, `significant` |
| Classification | `agencies`, `agencySlugs`, `topics` |
| Official sources | `htmlUrl`, `pdfUrl`, `rawTextUrl`, `sourceJsonUrl` |

### Example output

```json
{
  "documentNumber": "2026-12345",
  "documentTitle": "Example proposed rule",
  "documentType": "Proposed Rule",
  "publicationDate": "2026-08-20",
  "commentsCloseOn": "2026-09-21",
  "daysRemaining": 22,
  "agencies": ["Example Agency"],
  "agencySlugs": ["example-agency"],
  "citation": "91 FR 12345",
  "cfrReferences": ["40 CFR 1"],
  "regulationIdNumbers": ["1234-AA00"],
  "significant": false,
  "docketIds": ["EXAMPLE-2026-0001"],
  "htmlUrl": "https://www.federalregister.gov/documents/...",
  "pdfUrl": "https://www.govinfo.gov/content/pkg/..."
}
```

The example shows the schema and is not a real regulatory document.

### Automation recipe

Create an Apify schedule that runs daily, keep `daysAhead` at 30, 60, or 90, and send the dataset to a webhook, Make, Zapier, Google Sheets, Airtable, Slack, email, or an MCP-compatible AI client. Use `documentNumber` as the stable deduplication key in the destination.

### 💰 Pricing

Pay per saved deadline. Filters run before charging, and `maxItems` limits the maximum number of paid rows. No proxy fee or external data subscription is required. The exact event price is shown in the Pricing tab.

### 🔎 Data notes

The source is the official FederalRegister.gov API, but agencies can correct or extend deadlines. Verify legally significant dates using the linked official document. This Actor supplies public regulatory data, not legal advice.

### Support

If a record is missing or malformed, open an issue and include the Federal Register document number. Never include API tokens or credentials.

### 📥 Complete input reference

| Field | Type | Default | Purpose |
|---|---|---:|---|
| `daysAhead` | integer | `30` | Rolling window from today. Ideal for schedules. Ignored when both fixed dates are provided. |
| `includePastDays` | integer | `0` | Also include deadlines from this many days before today. |
| `deadlineFrom` | string | — | Optional earliest closing date (YYYY-MM-DD). Provide together with Deadline to to override the rolling window. |
| `deadlineTo` | string | — | Optional latest closing date (YYYY-MM-DD). Maximum fixed range: 180 days. |
| `query` | string | — | Optional full-text query, for example artificial intelligence, banking, or emissions. |
| `agencies` | array | — | Optional Federal Register agency slugs, for example environmental-protection-agency. |
| `documentTypes` | array | `["PRORULE","NOTICE"]` | Optional values: RULE, PRORULE, NOTICE, PRESDOCU. |
| `significantOnly` | boolean | `false` | Return only documents marked significant by the Federal Register. |
| `maxItems` | integer | `100` | Maximum matching records written and charged. |

### 📤 Complete output reference

The default dataset is exportable as JSON, CSV, Excel, XML or RSS. Fields remain stable for scheduled runs and API integrations.

| Field | Type |
|---|---|
| `documentNumber` | string |
| `documentTitle` | string |
| `documentType` | string |
| `documentSubtype` | string |
| `publicationDate` | string |
| `commentsCloseOn` | string |
| `daysRemaining` | integer |
| `agencies` | array |
| `agencySlugs` | array |
| `abstract` | string |
| `action` | string |
| `effectiveOn` | string |
| `citation` | string |
| `cfrReferences` | array |
| `regulationIdNumbers` | array |
| `significant` | boolean |
| `docketIds` | array |
| `topics` | array |
| `htmlUrl` | string |
| `pdfUrl` | string |
| `rawTextUrl` | string |
| `sourceJsonUrl` | string |
| `source` | string |

### 🔌 API & integrations

Run this Actor from the Apify Console, API, CLI, MCP, Make, Zapier or n8n. Replace the Actor identifier and token in this template:

```bash
curl -X POST "https://api.apify.com/v2/acts/federal-rule-comment-deadlines/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Results are stored in the run's default dataset and can be forwarded with Apify webhooks or scheduled Tasks.

### 🔎 Search keywords

Federal Register Comment Deadline Monitor, federal, register, comment, deadline, monitor, rule, deadlines, Apify Actor, scraper API, structured data, scheduled monitor, automation.

# Actor input Schema

## `daysAhead` (type: `integer`):

Rolling window from today. Ideal for schedules. Ignored when both fixed dates are provided.

## `includePastDays` (type: `integer`):

Also include deadlines from this many days before today.

## `deadlineFrom` (type: `string`):

Optional earliest closing date (YYYY-MM-DD). Provide together with Deadline to to override the rolling window.

## `deadlineTo` (type: `string`):

Optional latest closing date (YYYY-MM-DD). Maximum fixed range: 180 days.

## `query` (type: `string`):

Optional full-text query, for example artificial intelligence, banking, or emissions.

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

Optional Federal Register agency slugs, for example environmental-protection-agency.

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

Optional values: RULE, PRORULE, NOTICE, PRESDOCU.

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

Return only documents marked significant by the Federal Register.

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

Maximum matching records written and charged.

## Actor input object example

```json
{
  "daysAhead": 30,
  "includePastDays": 0,
  "documentTypes": [
    "PRORULE",
    "NOTICE"
  ],
  "significantOnly": false,
  "maxItems": 100
}
```

# Actor output Schema

## `deadlines` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("snuggly_beanie_970/federal-rule-comment-deadlines").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("snuggly_beanie_970/federal-rule-comment-deadlines").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 snuggly_beanie_970/federal-rule-comment-deadlines --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snuggly_beanie_970/federal-rule-comment-deadlines"
        }
    }
}

```

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/pvufRLijjX7KvmrS2/builds/1VZy7fzXDELYsUTO1/openapi.json