Federal Register Monitor: US rules, proposed rules and notices

Get new US federal regulations as a clean table, straight from the official Federal Register API. You get one row per document: title, agencies, rule type, publication, effective and comment-deadline dates, affected CFR parts, RINs, docket numbers, abstract, and links to the official HTML, PDF and Regulations.gov comment page.

Filter by keyword, agency, CFR title/part, document type and open comment period, schedule it daily with "only new since last run", and you have a regulatory alert feed for your practice area. You pay only for the documents you receive.

Who uses it

• Compliance teams watch the agencies that regulate them (SEC, CFPB, FDA, EPA, OSHA, FAA…) and log every new rule into their obligations register.
• Lawyers and regulatory consultants track the CFR parts their clients live under (e.g. 21 CFR 820, 40 CFR 63, 12 CFR 1026) and get proposed rules while the comment period is still open.
• Trade associations and public-affairs teams catch proposed rules early enough to organise comment letters.
• Analysts and newsletters build a daily digest of significant (EO 12866) rules and executive orders.

What you get (one row per document)

Field	Example
title	Rescission of Rule 14a-8's Federal Regulation of Shareholder Proposals…
agencies	Securities and Exchange Commission
documentType / documentTypeCode	Proposed Rule / PRORULE
action	Proposed rule.
publicationDate	2026-09-21
effectiveDate	date the rule takes effect (mostly final rules)
commentsCloseDate	2026-11-20
commentPeriodOpen / commentDaysLeft	true / 58
cfrReferences	17 CFR 200; 17 CFR 229; 17 CFR 240
rins	3235-AN47
docketIds	Release No. 34-106383; File No. S7-2026-32
significant	true (EO 12866 significant)
pageCount / citation	64 / 91 FR 59904
abstract	Official summary of the document
datesText	"Comments should be received on or before November 20, 2026."
topics	Reporting and recordkeeping requirements; Securities
subtype, executiveOrderNumber, signingDate	Executive Order, 14431, 2026-09-18 (presidential documents)
htmlUrl, pdfUrl, commentUrl	federalregister.gov page, govinfo.gov PDF, Regulations.gov comment form

The rows are flat (lists are joined with ; ), so the table exports cleanly to Excel, CSV, Google Sheets or your database.

How to use it

1. Keywords (optional): any of the words or phrases matches, e.g. PFAS, artificial intelligence, anti-money laundering.
2. Agencies (optional): short names like EPA, SEC, FDA, CFPB, OSHA, full names, or the slug from federalregister.gov/agencies.
3. Document types: final rules and proposed rules by default. Add notices (guidance, meetings, petitions, information collections) or presidential documents (executive orders, proclamations, memoranda).
4. CFR title / part (optional): 40 CFR 60, 21 CFR Part 820, 12 CFR 1026, or just a title like 17.
5. Period: the last N days (default 7) or an exact date range.
6. Optional switches: only with an open comment period, only significant rules, only new since the last run.
7. Max documents caps how many rows (and charges) one run can produce.

Example: daily alert for a drug manufacturer

{
    "agencies": ["FDA"],
    "cfrReferences": ["21 CFR 312", "21 CFR 314", "21 CFR 601"],
    "documentTypes": ["RULE", "PRORULE", "NOTICE"],
    "daysBack": 3,
    "onlyNew": true
}

Example: open comment periods on AI and cybersecurity

{
    "keywords": ["artificial intelligence", "cybersecurity"],
    "documentTypes": ["PRORULE", "NOTICE"],
    "openForCommentOnly": true,
    "daysBack": 60
}

Schedule the Actor (Apify Schedules) daily and connect the dataset to email, Slack, Google Sheets or Zapier. With only new since the last run you receive, and pay for, each document once.

Pricing

Pay per event: you are charged per document delivered. Documents that are skipped or already delivered are not charged, and a run that finds nothing new charges no documents. The maximum cost per run you set in Apify is respected: the Actor stops before exceeding it.

Data source and good behaviour

• Data comes from the official Federal Register API (federalregister.gov/api/v1), published by the Office of the Federal Register (NARA) and the Government Publishing Office. No login, no API key, no scraping of web pages. The website asks automated clients to use this API.
• The Actor identifies itself with a clear User-Agent, pauses between requests and honours Retry-After. If the source refuses access, the run stops and says so. It never tries to work around blocking.
• Federal Register content is a US government work.
• Privacy: documents that are about named private individuals (e.g. DEA practitioner decisions, individual debarment orders) are skipped, and e-mail addresses and phone numbers are removed from text fields. The run summary shows how many documents were skipped.

Output and run summary

• Dataset: one row per document (table view "Documents").
• SUMMARY record in the key-value store: documents delivered, matches reported by the API, documents skipped (already delivered or about individuals), why the run stopped, warnings about ignored inputs, and the filters used.

FAQ

How fresh is the data? The Federal Register is published each federal business day, and documents appear in the API on the day of publication.

Can I search the full text? Yes. Keywords are searched in the full text of documents, not only in titles.

What if I mistype an agency or CFR part? Unrecognised values are listed as warnings and ignored. If none of the agencies or CFR references can be recognised, the run stops with a clear message instead of returning (and charging for) everything.

Is this legal advice? No. It is a data feed. Always rely on the official published document linked in each row.

Not affiliated with the Office of the Federal Register, NARA or GPO.