# Federal Register Rules & Notices Tracker (`calculating_kitchen_h0b/federal-register-tracker`) Actor

- **URL**: https://apify.com/calculating_kitchen_h0b/federal-register-tracker.md
- **Developed by:** [Andres Barcelo](https://apify.com/calculating_kitchen_h0b) (community)
- **Categories:** Other
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 federal register 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 Rules & Notices Tracker

Search and monitor the **U.S. Federal Register**: final rules, proposed rules, agency notices and presidential documents (executive orders, proclamations) from every federal agency, as clean, flat JSON/CSV/Excel records. Data comes straight from the official federalregister.gov API (Office of the Federal Register, NARA).

Built for regulatory-affairs and compliance teams, policy analysts, lobbyists and government-relations firms, law firms, trade associations, journalists, researchers, investors and AI agents that need to know *what the government just changed*.

### What you can do

- **Monitor new regulations** by keyword (e.g. "artificial intelligence", "PFAS", "tariff", "cybersecurity", "crypto").
- **Track an agency** (EPA, FDA, SEC, DOE, FTC, FCC...) by agency slug.
- **Find rules open for public comment** with comment deadlines and Regulations.gov links.
- **Filter by type**: final rules, proposed rules, notices, presidential documents.
- **Only significant rules** (Executive Order 12866).
- **Run on a schedule** with *Published within (days)* and send results to Slack, email, Google Sheets, webhooks or your database via Apify integrations.

### Output (one record per document)

`documentNumber`, `title`, `type`, `subtype`, `publicationDate`, `agencies`, `agencySlugs`, `action`, `abstract`, `dates`, `effectiveOn`, `commentsCloseOn`, `commentUrl`, `regulationsGovUrl`, `citation`, `cfrReferences`, `docketIds`, `regulationIdNumbers`, `significant`, `topics`, `pageLength`, `executiveOrderNumber`, `signingDate`, `correctionOf`, `htmlUrl`, `pdfUrl`.

### Example input

```json
{ "searchTerm": "artificial intelligence", "documentTypes": ["RULE", "PRORULE"], "publishedWithinDays": 90, "maxResults": 100 }
```

### Pricing

Pay per result: **$2 per 1,000 documents**. No subscription.

### Data source

Official public Federal Register API (federalregister.gov/developers/documentation/api/v1). No login or API key needed. Only public regulatory documents are returned. This Actor is not affiliated with or endorsed by the Office of the Federal Register or any U.S. government agency. Not legal advice; always verify against the official publication.

# Actor input Schema

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

Full-text search, e.g. artificial intelligence, PFAS, tariff, cybersecurity

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

Agency slugs from federalregister.gov, e.g. environmental-protection-agency, food-and-drug-administration, securities-and-exchange-commission, energy-department

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

RULE = final rules, PRORULE = proposed rules, NOTICE = notices, PRESDOCU = presidential documents (executive orders etc.). Empty = all.

## `publishedWithinDays` (type: `integer`):

Only documents published in the last N days (ideal for scheduled monitoring)

## `publishedFrom` (type: `string`):

Optional exact start date; overrides 'Published within'

## `publishedTo` (type: `string`):

Optional end date

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

Only documents flagged as significant under Executive Order 12866

## `openForCommentOnly` (type: `boolean`):

Only documents whose comment period has not yet closed

## `maxResults` (type: `integer`):

Maximum documents to return

## Actor input object example

```json
{
  "searchTerm": "artificial intelligence",
  "publishedWithinDays": 30,
  "significantOnly": false,
  "openForCommentOnly": false,
  "maxResults": 200
}
```

# Actor output Schema

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

Documents in the default dataset (overview view).

# 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 = {
    "searchTerm": "artificial intelligence"
};

// Run the Actor and wait for it to finish
const run = await client.actor("calculating_kitchen_h0b/federal-register-tracker").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 = { "searchTerm": "artificial intelligence" }

# Run the Actor and wait for it to finish
run = client.actor("calculating_kitchen_h0b/federal-register-tracker").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 '{
  "searchTerm": "artificial intelligence"
}' |
apify call calculating_kitchen_h0b/federal-register-tracker --silent --output-dataset

```

## MCP server setup

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

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/UKSIKz2XrLofC8exR/builds/SZjcxmd1ykOeHAISu/openapi.json