# Federal Register Intelligence Normalizer (`wakey7dev/federal-register-normalizer`) Actor

Search and normalize US Federal Register documents — rules, proposed rules, notices, executive orders. Auto-categorizes by regulatory domain. Ideal for compliance teams, law firms, and policy analysts.

- **URL**: https://apify.com/wakey7dev/federal-register-normalizer.md
- **Developed by:** [Chris Wakefield](https://apify.com/wakey7dev) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## 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

![Chris The Dev](https://raw.githubusercontent.com/chriswakefield87/appstore-screenshot-translator/main/assets/actor-banner.png)

## Federal Register Intelligence Normalizer

Search, normalize, and categorize US Federal Register documents — rules, proposed rules, notices, and executive orders. Built for compliance teams, law firms, policy analysts, and regulatory affairs professionals.

### What it does

Pulls structured data from the Federal Register API (free, no key required) and normalizes it into clean, categorized records with:

- **Agency normalization** — consistent title-case agency names
- **Auto-categorization** — classifies documents into regulatory categories (Environmental, Healthcare, Financial, Technology, Labor, Energy, Transportation, Agriculture)
- **Keyword extraction** — identifies compliance-relevant terms (reporting, enforcement, certification, etc.)
- **Structured URLs** — HTML, PDF, and public inspection links for every document
- **Date filtering** — search by date range (last 30/90/365 days or custom range)

### Use cases

- **Compliance monitoring** — track new rules and proposed changes in your industry
- **Regulatory research** — search historical Federal Register actions by keyword, agency, or type
- **Legal intelligence** — identify upcoming regulatory changes before they take effect
- **Policy analysis** — categorize and trend regulatory activity across agencies

### Input

| Field | Type | Description |
|---|---|---|
| `searchTerm` | string | **Required.** Keyword or phrase to search (e.g., "environmental", "data privacy") |
| `documentType` | select | Filter by type: Final Rule, Proposed Rule, Notice, Presidential Document |
| `agency` | string | Filter by agency name (e.g., "Environmental Protection Agency") |
| `dateRange` | string | Date range: `last_30_days`, `last_90_days`, `last_year`, or `YYYY-MM-DD:YYYY-MM-DD` |
| `maxResults` | number | Max documents to return (1–200, default 20) |

### Output example

Each result contains:

```json
{
  "title": "Unleashing Unlicensed Spectrum for Direct-to-Device",
  "documentType": "Proposed Rule",
  "documentNumber": "2026-18282",
  "publicationDate": "2026-09-08",
  "agencies": ["Federal Communications Commission"],
  "abstract": "The FCC issues a Notice of Proposed Rulemaking...",
  "category": "Technology",
  "keywords": ["regulation", "standard", "requirement"],
  "urls": {
    "html": "https://www.federalregister.gov/documents/...",
    "pdf": "https://www.govinfo.gov/content/pkg/FR-.../pdf/...",
    "publicInspection": "https://public-inspection.federalregister.gov/..."
  }
}
```

### Data source

[Federal Register API v1](https://www.federalregister.gov/developers/documentation/api/v1) — official US government API. Free, no API key required. Updated daily with new publications.

### Pricing

$1.00 per 1,000 results via pay-per-event.

# Actor input Schema

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

Keyword or phrase to search in Federal Register documents (e.g., 'environmental', 'data privacy', 'cybersecurity')

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

Filter by document type

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

Filter by specific agency (e.g., 'Environmental Protection Agency', 'Federal Communications Commission')

## `dateRange` (type: `string`):

Publication date range (YYYY-MM-DD:YYYY-MM-DD or 'last\_30\_days', 'last\_90\_days', 'last\_year')

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

Maximum number of documents to return

## Actor input object example

```json
{
  "searchTerm": "environmental",
  "documentType": "",
  "dateRange": "last_30_days",
  "maxResults": 20
}
```

# Actor output Schema

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

Complete dataset of normalized Federal Register documents

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

Human-readable summary of search results

## `stats` (type: `string`):

Machine-readable statistics about the search

# 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": "environmental",
    "dateRange": "last_30_days"
};

// Run the Actor and wait for it to finish
const run = await client.actor("wakey7dev/federal-register-normalizer").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": "environmental",
    "dateRange": "last_30_days",
}

# Run the Actor and wait for it to finish
run = client.actor("wakey7dev/federal-register-normalizer").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": "environmental",
  "dateRange": "last_30_days"
}' |
apify call wakey7dev/federal-register-normalizer --silent --output-dataset

```

## MCP server setup

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

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/vGoBKGfJybARh7Ss5/builds/DHu1Gld6tWIwiIHNw/openapi.json