# Federal Register Notices & Consultations (`springlike_meadowland/federal-register-notices-scraper`) Actor

Search published US Federal Register notices, proposed rules, and rules by keyword, agency, and publication date. Export document numbers, agencies, abstracts, dockets, official dates, and source links.

- **URL**: https://apify.com/springlike\_meadowland/federal-register-notices-scraper.md
- **Developed by:** [Akshay Aggarwal](https://apify.com/springlike_meadowland) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 saved documents

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 Notices & Consultations

Turn published US Federal Register notices, proposed rules, or rules into a table your policy or compliance team can filter, export, and track. Search by keyword, agency, document type, and publication dates; each saved row links back to its source document and official PDF when available.

### Quick start

For a small set of Environmental Protection Agency proposed rules published in September 2026:

```json
{
  "agency": "environmental-protection-agency",
  "documentType": "PRORULE",
  "dateFrom": "2026-09-01",
  "dateTo": "2026-09-30",
  "maxDocuments": 5
}
```

The dataset contains one row per document. A representative source record is:

```json
{
  "document_number": "2026-19500",
  "title": "Public Water System Supervision Program Revision for the State of Arkansas",
  "type": "Proposed Rule",
  "agencies": ["Environmental Protection Agency"],
  "publication_date": "2026-09-23",
  "comments_close_date": "2026-10-23",
  "docket_ids": ["FRL-13495-01-R6"],
  "source_url": "https://www.federalregister.gov/api/v1/documents/2026-19500.json"
}
```

Rows also include an abstract and HTML/PDF links when the source provides them. `effective_date` and `comments_close_date` appear only when published in the API record; a missing date is not inferred. The `OUTPUT` record shows fetched, saved and skipped counts, source count, filters, and any limit or error.

### Search and coverage

- Source: the public [Federal Register documents API](https://www.federalregister.gov/developers/documentation/api/v1) for **published US Federal Register documents**. This Actor does not cover other countries, state registers, regulations.gov submissions, or unpublished public-inspection documents.
- `documentType`: `NOTICE` (default), `PRORULE` (Proposed Rule), or `RULE`. Run once per type when you need several types.
- `agency`: one Federal Register agency slug from an agency page URL, such as `environmental-protection-agency`.
- `dateFrom` and `dateTo`: inclusive **publication** dates, `YYYY-MM-DD`. They do not filter effective dates or comment deadlines.
- `maxDocuments`: 1–1,000 saved rows per run, default 10. Results follow the API's search order; searches and publication data can change. Check `OUTPUT.status` and `OUTPUT.limit_reason` before treating a dataset as complete.

### Usage and billing

The result unit is one **saved document**. Under pay-per-result pricing, only document rows written to the dataset count as result events; skipped records, errors and the `OUTPUT` summary are not result rows. A run can end with fewer rows than the requested cap if the source has fewer matches, a source error occurs, or the run's spending or request limit is reached. The `OUTPUT` record identifies partial runs and the number saved. Apify platform usage follows your account plan.

FederalRegister.gov's HTML rendering is an informational resource. For legal decisions, verify the linked official PDF and applicable current law. This Actor provides source fields; it does not interpret legal effect or infer deadlines.

# Actor input Schema

## `keyword` (type: `string`):

Optional full-text search term passed to the Federal Register documents API. Leave blank for the newest matching documents.

## `agency` (type: `string`):

Optional Federal Register agency slug, such as environmental-protection-agency. Use the slug from an agency page URL.

## `documentType` (type: `string`):

Choose notices, proposed rules (often open for comments), or published rules. One type per run.

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

Optional inclusive publication date in YYYY-MM-DD format. This filters publication date, not effective date or comment deadline.

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

Optional inclusive publication date in YYYY-MM-DD format. Must be on or after the start date.

## `maxDocuments` (type: `integer`):

Maximum saved document rows, from 1 to 1,000. Start with 10 for a sample. The OUTPUT record reports any limit or partial result.

## Actor input object example

```json
{
  "documentType": "NOTICE",
  "maxDocuments": 10
}
```

# Actor output Schema

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

One row per saved document, with dates, agencies, dockets and source links where published.

## `summary` (type: `string`):

Counts, filters, limits and any source error for this run.

# 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("springlike_meadowland/federal-register-notices-scraper").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("springlike_meadowland/federal-register-notices-scraper").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 springlike_meadowland/federal-register-notices-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,springlike_meadowland/federal-register-notices-scraper"
        }
    }
}
```

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/lTPa3TWay1yC6Gwor/builds/si1bRqNYQMKD4nVcl/openapi.json