# Federal Register Scraper API – US Rules & Notices (`fluyeporlaweb/federal-register-scraper`) Actor

Scrape US Federal Register documents via the official API: rules, proposed rules, notices. Title, agency, type, dates, PDF. No login.

- **URL**: https://apify.com/fluyeporlaweb/federal-register-scraper.md
- **Developed by:** [Pablo Navarro](https://apify.com/fluyeporlaweb) (community)
- **Categories:** Automation, Lead generation, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.20 / 1,000 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 Scraper API – US Rules & Notices

**Federal Register scraper** that returns **US Federal Register** documents (rules, proposed rules, notices and presidential documents) via the **official developer API**: title, agencies, type, dates, abstract and PDF/HTML links.

### What does it do?

- Document number, title and type.
- Agency names.
- Publication date and abstract.
- HTML and PDF links.

### Use cases

- **Compliance / legal ops**: watch new rules in your sector.
- **Lobbying and policy**: track proposed rules mentioning your keywords.
- **AI agents**: feed daily FR hits into a briefing bot.
- **Journalism**: source lists for regulatory stories.

### Input

| Field | Description |
|---|---|
| `query` | Full-text search. Empty = newest. Example: artificial intelligence |
| `documentTypes` | RULE, PRORULE, NOTICE, PRESDOCU… Empty = all. Example: RULE, NOTICE |
| `maxItems` | Example: 50 |

Example input:

```json
{
  "query": "artificial intelligence",
  "documentTypes": [],
  "maxItems": 25
}
```

### Output

Real output (first items of a run on 26 Oct 2026):

```json
[
  {
    "documentNumber": "2026-21884",
    "title": "Critical Material List; Addition of Helium",
    "type": "Notice",
    "agencies": [
      "Energy Department"
    ],
    "publicationDate": "2026-10-27",
    "abstract": "The United States (U.S.) Department of Energy (DOE) is issuing this notice to advise the public that DOE added helium to the DOE Critical Material List. This notice also provides the link to the assessment that forms the justification for including helium on the Critical Material List. Helium is non-substitutable for multiple critical energy functions, including: semiconductor manufacturing, leak testing natural gas infrastructure, and quantum computing, along with being essential to key medical/scientific applications. Demand for helium is also growing as it enables advanced semiconductor manufacturing, which is essential for SI and data center supply chains.",
    "htmlUrl": "https://www.federalregister.gov/documents/2026/10/27/2026-21884/critical-material-list-addition-of-helium",
    "pdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-10-27/pdf/2026-21884.pdf",
    "url": "https://www.federalregister.gov/documents/2026/10/27/2026-21884/critical-material-list-addition-of-helium"
  },
  {
    "documentNumber": "2026-21786",
    "title": "Outbound Investment Security Program Regulations",
    "type": "Proposed Rule",
    "agencies": [
      "Treasury Department",
      "Investment Security Office"
    ],
    "publicationDate": "2026-10-26",
    "abstract": "This proposed rule sets forth regulations that would implement Subtitle C of the Comprehensive Outbound Investment National Security Act, which is codified at Title VIII of the Defense Production Act. The proposed rule would require United States persons to provide notification to the U.S. Department of the Treasury regarding certain transactions involving foreign persons that are engaged in notifiable technologies; and prohibit United States persons from engaging in certain other transactions involving foreign persons that are engaged in prohibited technologies. Where consistent with Title VIII, the proposed rule incorporates certain definitions and concepts from the current regulations governing the Outbound Investment Security Program. The proposed rule also would add applicability dates to the regulations, such that those regulations would continue to apply to activities that occurred within the relevant timeframe.",
    "htmlUrl": "https://www.federalregister.gov/documents/2026/10/26/2026-21786/outbound-investment-security-program-regulations",
    "pdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-10-26/pdf/2026-21786.pdf",
    "url": "https://www.federalregister.gov/documents/2026/10/26/2026-21786/outbound-investment-security-program-regulations"
  }
]
```

Export the results as JSON, CSV or Excel, read them through the API, or send them to Google Sheets, Make, Zapier, n8n or webhooks. You can also run this Actor from AI agents through the Apify MCP server.

### Pricing

Pay per event: **$2.20 per 1,000 documents** plus $0.00005 per run start. There is no extra platform usage charge.

### FAQ

**Is scraping federalregister.gov HTML allowed?** Prefer the official API (this Actor). The site limits aggressive HTML scraping and points developers to the API.

**Are the texts public domain?** Federal government works are generally not subject to copyright under 17 U.S.C. § 105.

**Do I need a key?** No.

**Do I need a login or API key?** No. It uses the source's public API; you only need an Apify account.

**Can AI agents use it?** Yes. Call it through the Apify API, or from Claude, Cursor or any MCP client via the Apify MCP server.

### Data source and license

Source: [Federal Register API](https://www.federalregister.gov/developers/documentation/api/v1). US federal government works: [17 U.S.C. § 105](https://www.copyright.gov/title17/92chap1.html#105) (copyright protection not available for works of the United States Government). Agency abstracts/titles as published. Not affiliated with NARA/OFR.

This Actor is not affiliated with or endorsed by the data source. You are responsible for using the data in line with the source's license and terms.

# Actor input Schema

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

Full-text search. Empty = newest. Example: artificial intelligence

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

RULE, PRORULE, NOTICE, PRESDOCU… Empty = all. Example: RULE, NOTICE

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

Example: 50

## Actor input object example

```json
{
  "maxItems": 50
}
```

# Actor output Schema

## `items` (type: `string`):

No description

## `summary` (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("fluyeporlaweb/federal-register-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("fluyeporlaweb/federal-register-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 fluyeporlaweb/federal-register-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fluyeporlaweb/federal-register-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/z0W2cQ4noqhG2bVUM/builds/3MQwbg9CR8HJ5CfFn/openapi.json