US Federal Register Rule Event Watch avatar

US Federal Register Rule Event Watch

Pricing

from $3.40 / 1,000 rule event deltas

Go to Apify Store
US Federal Register Rule Event Watch

US Federal Register Rule Event Watch

Rules, proposed rules and notices as they publish in the Federal Register.

Pricing

from $3.40 / 1,000 rule event deltas

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

πŸ“š US Federal Register Rule Event Watch

Rules, proposed rules and notices as they publish in the Federal Register.

Output is one document_record row per result; billing is pay-per-event, the value event being one rule event delta (a $0.02 start fee per run, then $0.005 per rule event delta plus one $0.10 source check per run that reads the source). Source: www.federalregister.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

πŸ“Š Sample Output

US Federal Register Rule Event Watch sample output β€” a table of real rule event delta rows (document_number, title, doc_type, publication_date) from run Vm9w6QJeFahERdNi3 on build 0.1.19

Real rows from run Vm9w6QJeFahERdNi3 on build 0.1.19 (2026-09-17), the same input as the Quick start below β€” every value is as the source published it (emails masked, long text shortened):

document_numbertitledoc_typepublication_dateagency_names
2026-19084Airworthiness Directives; Airbus SAS AirplanesRule2026-09-17["Transportation Department", "Federal Aviation Administration"]
2026-19083Airworthiness Directives; The Boeing Company AirplanesRule2026-09-17["Transportation Department", "Federal Aviation Administration"]
2026-19082Airworthiness Directives; The Boeing Company AirplanesRule2026-09-17["Transportation Department", "Federal Aviation Administration"]
2026-19074Medical Devices; Exemption From Premarket Notification: Radiology CompRule2026-09-17["Health and Human Services Department", "Food and Drug Administration
2026-19071Partial Repeal of the Carbon Pollution Standards for Fossil Fuel-FiredRule2026-09-17["Environmental Protection Agency"]
2026-19065Revocation of Obsolete Rules Regarding Infant Bouncer Seats and StatioRule2026-09-17["Consumer Product Safety Commission"]
2026-19060Safety Zone; Key West Main Ship Channel, and Fleming Key Cut, Key WestRule2026-09-17["Homeland Security Department", "Coast Guard"]
2026-19056Special Local Regulation; Maumee River, Toledo, OHRule2026-09-17["Homeland Security Department", "Coast Guard"]

The run finished with the status message: NORMAL: emitted 10 item(s)

βœ… What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_key (string/null) β€” e.g. fr:2026-19084
  • document_number β€” e.g. 2026-19084
  • title β€” e.g. Airworthiness Directives; Airbus SAS Airplanes
  • doc_type β€” e.g. Rule
  • publication_date β€” e.g. 2026-09-17
  • agency_names β€” e.g. ["Transportation Department", "Federal Aviation Administration"]
  • source_url β€” e.g. https://www.federalregister.gov/documents/2026/09/17/2026-19084/airworthiness-di
  • record_type (string) β€” e.g. document_record
  • delta_type (string/null) β€” null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged β€” diagnostics never land in the paid dataset.

βš™οΈ Sample inputs

1. Quick start β€” the Store example (this is what the sample above came from)

{
"doc_types": [
"RULE"
],
"agencies": [],
"watch_mode": false,
"baseline_id": "default",
"max_items": 10
}

The sample run charged exactly: 1 Γ— $0.02 apify-actor-start + 1 Γ— $0.10 source-check + 0 Γ— $0.005 rule-event-delta = $0.12 on the Free tier β€” snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
"doc_types": [
"RULE"
],
"agencies": [],
"watch_mode": false,
"baseline_id": "default",
"max_items": 5
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
"doc_types": [
"RULE"
],
"agencies": [],
"watch_mode": true,
"baseline_id": "default",
"max_items": 10
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.005 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run Vm9w6QJeFahERdNi3, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_key": "fr:2026-19084",
"document_number": "2026-19084",
"title": "Airworthiness Directives; Airbus SAS Airplanes",
"doc_type": "Rule",
"publication_date": "2026-09-17",
"agency_names": [
"Transportation Department",
"Federal Aviation Administration"
],
"source_url": "https://www.federalregister.gov/documents/2026/09/17/2026-19084/airworthiness-directives-airbus-sas-airplanes",
"record_type": "document_record",
"schema_version": "1.0",
"output_mode": "preview",
"preview_cap": 25,
"preview_truncated": 0
}

πŸ”§ How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each rule event delta is charged at the moment it is pushed (rule-event-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

Source

Federal Register API v1 documents (public, logged-out)

Public, logged-out only β€” no API key, login, cookie or CAPTCHA.

Snapshot mode is a PREVIEW

watch_mode: false returns a preview only: at most 25 records, hard-capped in code regardless of max_items. Preview records carry output_mode: "preview" with preview_cap and preview_truncated. It charges no value event. This actor sells change detection, not bulk record export β€” use watch mode for the feed.

Watch semantics

The first watch run stores a private baseline and emits zero deltas. Later runs emit NEW / CHANGED / REMOVED keyed on the source-native id, with before / after and changed_fields.

Terminal states

NORMAL Β· SUCCEEDED-0: GENUINE_EMPTY Β· PARTIAL Β· BLOCKED. A zero with no evidence FAILS loud rather than exiting 0 quietly.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console β†’ Schedules β†’ Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

  • Daily β€” 0 7 * * * (07:00 UTC): catch changes within a day.
  • Weekly β€” 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console β†’ Integrations).

πŸ’° Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Source check (source-check)$0.10$0.09$0.08$0.07
Rule event delta (rule-event-delta)$0.005$0.0045$0.004$0.0034

Worked at the live Free-tier price (watch mode, one delta per change):

  • 8 rule event deltas: $0.02 start + $0.10 source check + 8 Γ— $0.005 = $0.16
  • 25 rule event deltas: $0.02 start + $0.10 source check + 25 Γ— $0.005 = $0.24
  • 200 rule event deltas: $0.02 start + $0.10 source check + 200 Γ— $0.005 = $1.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: emitted 10 item(s). max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

This actor reads public, logged-out pages and feeds published by www.federalregister.gov. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.federalregister.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event β€” retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to max_items (default 200); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other public records lookups actors?
A: Same output shape and billing model; this one covers www.federalregister.gov. The siblings under Related Actors cover the other sources or slices β€” run several on one schedule for a combined feed.

πŸ†˜ Troubleshooting

  • Run FAILED with BLOCKED β†’ the source refused the request or changed its page shape β†’ nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED β†’ your cap (max_items) was reached β†’ raise it for a bigger run.
  • Input validation error on start β†’ a field is outside the schema's allowed values β†’ start from the Quick start block and change one field at a time.
  • Run TIMED-OUT β†’ a very wide request on a slow day β†’ raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • First watch run shows no deltas β†’ expected: it seeds the baseline; changes appear from the second run.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab β€” every one is read.