Industry Regulation & Deadline Radar

Find US Federal Register regulatory documents by industry keyword, agency, document type, publication date, effective date and comment deadline. Export one normalized JSON/CSV row per unique document, with original action wording, docket IDs and official PDF links.

Pricing

$0.01 per successfully saved unique document ($10 per 1,000), per run. No startup fee, date-level fee, API-request fee or retry fee. Standard Actor run platform usage is included in this event price. Apify account/subscription and post-run storage/export charges, if applicable, are governed by Apify separately. Separate runs are separate purchases.

A document with five dates is one result. Repeated source records and restored results in the same run are not billed again. A durable billing intent plus document-based idempotency protects against duplicate charges after ambiguous network responses; an uncertain charge is never retried after resurrection. In that rare case a saved result may be delivered without a confirmed charge.

Quick start

{"keywords":["compliance"],"documentTypes":["RULE","PRORULE","NOTICE"],"maxResults":10}

This example uses no API key, login, proxy subscription or paid LLM. It searches the current source, so its documents change over time. To monitor your industry, replace the keyword with terms such as solar, cybersecurity, medical devices or food labeling; schedule runs in Apify Console.

Inputs

• keywords: array of full-text search expressions. Entries are searched independently and merged (OR), with document ID deduplication. An empty array searches all documents.
• agencies: official Federal Register slugs, OR within the array. The agency array is validated against the official agencies endpoint. For example: environmental-protection-agency. Other filters combine with AND. Exact source agency matches are checked locally.
• documentTypes: RULE, PRORULE, NOTICE, PRESDOCU, CORRECT. RULE includes final/interim rules; the original action remains available. Modern corrections, postponements, extensions and withdrawals are separate change_types flags on the original document type. CORRECT is a legacy source type; do not use it alone to find modern corrections.
• publicationDateFrom/To, effectiveDateFrom/To, commentDeadlineFrom/To: inclusive, real YYYY-MM-DD dates. Missing structured dates do not match date-filtered searches. Reversed or invalid ranges fail before source requests.
• maxResults: 1–1,000, default 10. maxCostUsd: 0–10, default 10. The lower result count allowed by these and Apify's maximum run spend wins; amounts are floored to complete $0.01 results.
• pageSize: 1–100 (default 20). maxPages: 1–50, global across keywords. maxScanDocuments: 1–5,000. maxRunSeconds: 10–240. These protect time and cost.
• includeBodyDates: default true. Inspect compliance-related body paragraphs where available; otherwise the result identifies DATES-only scope and any retrieval warning.

Output and date meaning

The default Dataset supports JSON, CSV and Apify integrations. The run output also links to JSON/CSV and SUMMARY; key-value records OUTPUT and OUTPUT_CSV provide reusable exports.

Core fields: document_id, title, agency (array), document_type, publication_date, effective_date, comment_deadline, action, docket_ids, source_url and official_pdf_url.

Dates come from distinct source metadata fields: publication_date, effective_on and comments_close_on. Unknown values stay null. We never calculate an absolute deadline from a relative phrase such as “30 days after publication.”

Additional fields:

• document_stage: broad source stage (final_rule for the source Rule type, proposed_rule, notice, etc.). It does not convert a proposal into an adopted obligation. Read action for interim, direct final or other subtype wording.
• change_types: correction, postponement, extension and withdrawal flags when explicitly signaled by the title/action or correction metadata. These are not consolidated legislative history.
• dates_text: original DATES section text.
• date_mentions: explicit full English month/day/year dates, each with date_text, section, evidence and source_url. Unclassified mentions are not labeled as obligations.
• additional_compliance_dates: conservatively recognized compliance, reporting and applicability date statements, each with a label and evidence. These are source-stated candidates, not independently verified current obligations. Labels and temporal_role distinguish proposed/conditional, historical, superseded and replacement dates; legal_stage retains the source stage. Group-specific dates keep their complete source sentence. Historical citations and ambiguous transitions are not promoted into deadlines.
• unresolved_date_statements: relative, indefinite or unannounced dates preserved as text.
• correction_of/corrections, interpretation_notes, date_extraction_scope and fetched_at retain context and provenance.

Multiple dates remain nested in their document row. Primary dates reflect API metadata, even if a postponement document's metadata retains an earlier date. For such documents, consult the action, DATES evidence and official PDF. This Actor does not silently resolve contradictions, amend other documents or infer the current consolidated deadline.

Limits, completeness and errors

Source requests use 20-second timeouts, up to two retries for network/429/5xx failures and bounded exponential delay. Invalid requests fail without retry. Pagination follows official next_page_url including its cursor; cycles and unsafe off-source URLs are rejected. IDs deduplicate overlapping pages and keyword searches.

SUMMARY reports pages, scans, document failures, body failures, stop_reason and complete. Reaching any user, page, scan, time or spend limit is a partial search. A result cap is not proof that every matching regulation was found. The official source also limits broad searches: use narrow publication-date windows and separate runs for larger coverage. Dataset writes/charges are not blindly retried.

Body extraction recognizes explicit English calendar dates and selected compliance wording, not every possible date or obligation. No extraction of legal requirements from tables, scans, incorporated documents or linked third-party sites is promised. Agency-slug local verification can narrow parent-agency searches to documents actually listing that agency.

Sources and permitted use

• Official API documentation
• Published document search
• Official agency list
• Developer resources and usage restrictions
• Legal status

FederalRegister.gov is operated by OFR/NARA and GPO, but its XML/HTML rendition is an informational resource, not the official legal edition. The official_pdf_url points to the published govinfo.gov PDF, not a public-inspection draft. Verify reliance against the official edition.

The API is public and requires no key. Republishers may not use official NARA/OFR logos or seals. This product uses no government logos, implies no endorsement and exports document metadata with short contextual date evidence rather than repackaging complete third-party works.

This is a regulatory discovery aid, not legal advice or a guarantee that all obligations, amendments or deadlines have been identified.