# Federal Register Monitor: New US Rules & Notices (`veridra/federal-register-monitor`) Actor Track new US federal rules, proposed rules, notices and executive orders from the official Federal Register API. Filter by agency, keyword and type; get comment deadlines, dockets and CFR parts. - **URL**: https://apify.com/veridra/federal-register-monitor.md - **Developed by:** [Veridra Computer Technology](https://apify.com/veridra) (community) - **Categories:** Business, News, AI - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.80 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 ### What does Federal Register Monitor do? **Federal Register Monitor** returns new documents from the official **Federal Register**, the daily journal of the US government: final rules, proposed rules, notices and presidential documents. Filter by agency, keyword and document type, and get each document's comment deadline, effective date, dockets, RINs and affected CFR parts. Schedule it daily with **Only new results** for a clean regulatory change feed. It collects data from **[Federal Register (Office of the Federal Register, National Archives, and the US Government Publishing Office)](https://www.federalregister.gov/developers/documentation/api/v1)** and returns clean, structured results you can download or pull through the **Apify API**. ### Why use Federal Register Monitor? - **Compliance and regulatory affairs:** see every new rule from the agencies that regulate you, the day it is published. - **Public comment tracking:** proposed rules come with their comment deadline and Regulations.gov link, so you never miss a window. - **Law firms, consultants and trade associations:** alert clients to rules that change their obligations, by keyword or CFR part. - **Policy research and journalism:** follow agencies, executive orders and significant rules over time. - **AI agents:** structured, official regulatory data with links to the published text and PDF. - Runs on the Apify platform: schedule runs, call it through the API, connect it to integrations, and get notified when a run fails. ### What data can Federal Register Monitor extract? | Field | Type | Description | | --- | --- | --- | | `documentNumber` | string | Federal Register document number, unique per document. | | `publicationDate` | string | Date the document was published (YYYY-MM-DD). | | `type` | string | Rule, Proposed Rule, Notice or Presidential Document. | | `subtype` | string | For presidential documents: Executive Order, Proclamation, Memorandum and similar. Empty for other types. | | `title` | string | Document title. | | `primaryAgency` | string | The first agency listed on the document. | | `agencies` | array | Every agency on the document, parent agencies included. | | `action` | string | The document's action line, for example Proposed rule or Final rule; delay of effective date. | | `abstract` | string | The document's summary. | | `commentsCloseOn` | string | Last day to submit comments (YYYY-MM-DD), for documents open for comment. | | `commentUrl` | string | Where to comment (usually Regulations.gov). | | `effectiveDate` | string | Date the rule takes effect (YYYY-MM-DD), when given. | | `docketIds` | array | Agency docket numbers. | | `regulationIdNumbers` | array | Regulation Identifier Numbers (RINs) linking to the Unified Agenda. | | `cfrReferences` | array | Code of Federal Regulations parts the document affects. | | `significant` | boolean | Whether the document is significant under Executive Order 12866. Empty when not stated. | | `citation` | string | Federal Register citation (volume FR page). | | `pages` | integer | Length of the document in Federal Register pages. | | `topics` | array | CFR index topics. | | `matchExcerpt` | string | The passage that matched your search term, when you searched. | | `htmlUrl` | string | The document on federalregister.gov. | | `pdfUrl` | string | Official PDF from govinfo.gov. | | `sourceUrl` | string | The document's record in the Federal Register API. | | `scrapedAt` | string | When this result was collected (UTC, ISO 8601). | ### How to use Federal Register Monitor 1. Open the actor and select **Try for free**. 2. Fill in **Search terms**, **Agencies**. The prefilled example works as a first test. 3. Set **Maximum results** to control how much data, and cost, a run produces. 4. Select **Start** and wait for the run to finish. 5. Download the results as JSON, CSV, Excel or HTML, or fetch them through the API. ### How much does it cost to use Federal Register Monitor? You pay per result: **$4.00 per 1,000 results** ($0.004 each), plus Apify's small start fee of $0.0001 per run. For example, 1,000 results cost about $4.00. You can set a maximum cost per run in the run options, and the actor stops cleanly when it is reached. Subscribers to Apify's paid plans pay less per result: 10% off on Bronze, 20% off on Silver and 30% off on Gold and higher plans. ### Get only new results Turn on **Only new results** and schedule the actor (for example daily) to use it as a monitor: each run skips what earlier runs already returned, so you get a feed of new records and pay only for those. The first run returns everything that matches. The memory lives in your own Apify account; give runs the same **Monitor name** to share it when you change other inputs. ### Use it from AI agents AI agents can find and run Federal Register Monitor as a tool through Apify's MCP server (mcp.apify.com) or the Apify API, and get the same structured results, billed per result. Without code, Apify's Zapier, Make and n8n integrations can start it and send each new result to a sheet, CRM or chat. ### Input See the **Input** tab for every option. The main fields: | Field | Type | Default | Description | | --- | --- | --- | --- | | `searchTerms` | array | \[] | Full-text search terms, one per line, for example PFAS or "artificial intelligence". A document matching any term is returned once. Leave empty for every document. | | `agencies` | array | \[] | Agency names or federalregister.gov slugs, for example Environmental Protection Agency, food-and-drug-administration or Department of the Treasury. Leave empty for all agencies. | | `documentTypes` | array | \["RULE", "PRORULE"] | Which kinds of documents to include. | | `significantOnly` | boolean | false | Only documents marked significant under Executive Order 12866 (major economic or policy impact). | | `daysBack` | integer | 7 | Documents published in this many days up to today. Ignored when a start date is set. | | `dateFrom` | string | "" | Only documents published on or after this date (YYYY-MM-DD). Leave empty to use Days back. | | `dateTo` | string | "" | Only documents published on or before this date (YYYY-MM-DD). Leave empty for today. | | `maxResults` | integer | 1000 | Stop after this many results. Each result costs $0.004, so this also caps the cost of a run. Use 0 for no limit. Keep it low for a first test. | | `onlyNew` | boolean | false | Monitoring mode: skip results this monitor returned in earlier runs, so a scheduled run returns, and bills, only what is new. The first run returns everything that matches. | | `monitorName` | string | "" | Runs with the same name share one memory of returned results, even if you change other inputs. Leave empty to keep a separate memory for each distinct input. | Example input: ```json { "daysBack": 14, "maxResults": 20 } ``` ### Output You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. Example items: ```json [ { "documentNumber": "C1-2026-12067", "publicationDate": "2026-10-19", "type": "Rule", "subtype": null, "title": "Fee Schedules; Fee Recovery for Fiscal Year 2026", "primaryAgency": "Nuclear Regulatory Commission", "agencies": [ "Nuclear Regulatory Commission" ], "action": null, "abstract": null, "commentsCloseOn": null, "commentUrl": null, "effectiveDate": null, "docketIds": [ "NRC-2023-0212" ], "regulationIdNumbers": [], "cfrReferences": [ "10 CFR 15", "10 CFR 170", "10 CFR 171" ], "significant": null, "citation": "91 FR 65941", "pages": 1, "topics": [], "matchExcerpt": null, "htmlUrl": "https://www.federalregister.gov/documents/2026/10/19/C1-2026-12067/fee-schedules-fee-recovery-for-fiscal-year-2026", "pdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-10-19/pdf/C1-2026-12067.pdf", "sourceUrl": "https://www.federalregister.gov/api/v1/documents/C1-2026-12067?publication_date=2026-10-19", "scrapedAt": "2026-10-19T18:39:59+00:00" }, { "documentNumber": "2026-21387", "publicationDate": "2026-10-19", "type": "Proposed Rule", "subtype": null, "title": "Airworthiness Directives; Airbus Helicopters", "primaryAgency": "Transportation Department", "agencies": [ "Transportation Department", "Federal Aviation Administration" ], "action": "Notice of proposed rulemaking (NPRM).", "abstract": "The FAA proposes to adopt a new airworthiness directive (AD) for all Airbus Helicopters Model AS350B3, AS355F, AS355F1, AS355F2, AS355N, AS355NP, EC130B4, and EC130T2 helicopters. This proposed AD was prompted by a report of the loss of the tightening torque between the upper ball bearing end and a main rotor (MR) servo-control. This proposed AD would require an inspection of the nut tightening torque of the upper ball bearing end of all the MR servo-controls and, depending on the results, corrective actions. The proposed AD would also require reporting the inspection results. The FAA is proposing this AD to address the unsafe condition on these products.", "commentsCloseOn": "2026-12-03", "commentUrl": "http://www.regulations.gov/commenton/FAA-2026-11814-0001", "effectiveDate": null, "docketIds": [ "Docket No. FAA-2026-11814", "Project Identifier MCAI-2026-00715-R" ], "regulationIdNumbers": [ "2120-AA64" ], "cfrReferences": [ "14 CFR 39" ], "significant": false, "citation": "91 FR 66019", "pages": 4, "topics": [ "Air transportation", "Aircraft", "Aviation safety", "Incorporation by reference", "Safety" ], "matchExcerpt": "The FAA proposes to adopt a new airworthiness directive (AD) for all Airbus Helicopters Model AS350B3, AS355F, AS355F1, AS355F2, AS355N, AS355NP, EC130B4, and EC130T2 helicopters. This proposed AD was prompted by a report of the loss of the tightening...", "htmlUrl": "https://www.federalregister.gov/documents/2026/10/19/2026-21387/airworthiness-directives-airbus-helicopters", "pdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-10-19/pdf/2026-21387.pdf", "sourceUrl": "https://www.federalregister.gov/api/v1/documents/2026-21387?publication_date=2026-10-19", "scrapedAt": "2026-10-19T18:39:59+00:00" } ] ``` ### Tips - Schedule a daily run with Days back = 3 and Only new results on: overlapping days catch late additions without paying twice. - Combine agencies with search terms to stay focused, for example Food and Drug Administration with "dietary supplement". - Add Notices only when you need them: they are most of the volume (meetings, information collections, permits). - Departments can be typed as they are usually written, for example Department of the Treasury or Department of Labor. - Schedule the actor to keep a dataset fresh, and use the API or integrations to send new results where you need them. ### FAQ, disclaimers, and support #### Where does the data come from? From Federal Register (Office of the Federal Register, National Archives, and the US Government Publishing Office) (www.federalregister.gov). Data is used under: Federal Register documents are works of the US Government and in the public domain (17 U.S.C. 105); the Federal Register API is offered for public use without a key. See the source's terms: https://www.federalregister.gov/developers/documentation/api/v1 #### Is it legal to use this data? This actor only collects publicly available data from Federal Register (Office of the Federal Register, National Archives, and the US Government Publishing Office) and does not collect personal data about private individuals. Check that your use complies with the source's terms and the laws that apply to you. This actor is not affiliated with or endorsed by Federal Register (Office of the Federal Register, National Archives, and the US Government Publishing Office). #### How fresh is the data? The actor queries the Federal Register API on every run. Documents appear on their publication date, usually early in the morning US Eastern time on business days. #### Does it return the full text? It returns the summary, action, dates, dockets, CFR parts and links to the full text on federalregister.gov and the official PDF on govinfo.gov. #### Can I search older documents? Yes. Set Published from and Published until to any period since 1994; long periods are fetched week by week. #### Is the data free to reuse? Yes. Federal Register documents are works of the US Government and in the public domain. #### Something is not working Open an issue in the **Issues** tab with your run link and we will look at it. For programmatic access, see the **API** tab. # Changelog This Actor's version history is a separate document: https://apify.com/veridra/federal-register-monitor/changelog.md # Actor input Schema ## `searchTerms` (type: `array`): Full-text search terms, one per line, for example PFAS or "artificial intelligence". A document matching any term is returned once. Leave empty for every document. ## `agencies` (type: `array`): Agency names or federalregister.gov slugs, for example Environmental Protection Agency, food-and-drug-administration or Department of the Treasury. Leave empty for all agencies. ## `documentTypes` (type: `array`): Which kinds of documents to include. ## `significantOnly` (type: `boolean`): Only documents marked significant under Executive Order 12866 (major economic or policy impact). ## `daysBack` (type: `integer`): Documents published in this many days up to today. Ignored when a start date is set. ## `dateFrom` (type: `string`): Only documents published on or after this date (YYYY-MM-DD). Leave empty to use Days back. ## `dateTo` (type: `string`): Only documents published on or before this date (YYYY-MM-DD). Leave empty for today. ## `maxResults` (type: `integer`): Stop after this many results. Each result costs $0.004, so this also caps the cost of a run. Use 0 for no limit. Keep it low for a first test. ## `onlyNew` (type: `boolean`): Monitoring mode: skip results this monitor returned in earlier runs, so a scheduled run returns, and bills, only what is new. The first run returns everything that matches. ## `monitorName` (type: `string`): Runs with the same name share one memory of returned results, even if you change other inputs. Leave empty to keep a separate memory for each distinct input. ## Actor input object example ```json { "searchTerms": [], "agencies": [], "documentTypes": [ "RULE", "PRORULE" ], "significantOnly": false, "daysBack": 14, "dateFrom": "", "dateTo": "", "maxResults": 20, "onlyNew": false, "monitorName": "" } ``` # Actor output Schema ## `dataset` (type: `string`): Dataset containing all results # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "daysBack": 14, "maxResults": 20 }; // Run the Actor and wait for it to finish const run = await client.actor("veridra/federal-register-monitor").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "daysBack": 14, "maxResults": 20, } # Run the Actor and wait for it to finish run = client.actor("veridra/federal-register-monitor").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 '{ "daysBack": 14, "maxResults": 20 }' | apify call veridra/federal-register-monitor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,veridra/federal-register-monitor" } } } ``` 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 ` 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/7FXzbuFJldiQY0nUp/builds/UYvkLsp5HMc3aa25U/openapi.json