# Federal Register — Multi-Query Document Export (`jpmarketdata/federal-register-multi-query-document-export`) Actor Search US Federal Register publications by terms, agencies, dates, type and CFR. Export unique document identities, abstracts, dates, references and official links with bounded coverage. - **URL**: https://apify.com/jpmarketdata/federal-register-multi-query-document-export.md - **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community) - **Categories:** News, Automation, Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $1.50 / 1,000 unique document exporteds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. 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 ## Federal Register — Multi-Query Document Export Export regulatory publication records for recurring policy and industry research from the documented Federal Register API. Search by terms, agencies, document type, inclusive publication dates and optional CFR title/part. Each unique document includes sanitized abstract/action, agency identities, publication/effective/comment dates, citations, docket/RIN/CFR references and official PDF links. **Price:** $0.0015 per unique delivered document. No start, query, duplicate, failure or empty-search charge. An optional Apify maximum charge reduces the global delivered-document cap. This independent Actor is not affiliated with NARA, OFR or any government agency. ### Input `searchTerms`: 0–5 native full-text terms, defaults to emissions. Empty means filter-only browsing and requires agency, type, an explicit date bound or CFR filter; it has no fallback search term. `agencies`: up to5 official slugs (empty=all); `documentTypes`: RULE, PRORULE, NOTICE, PRESDOCU (empty=all). `publicationFrom` and `publicationTo` accept optional inclusive YYYY-MM-DD dates; empty upper date resolves to UTC today and future dates are rejected. `cfrTitle`:0 disables,1–50 selects a title; `cfrPart` optional numeric part requires title. `maxDocuments`:1–500 **global** unique delivered cap; default20. Source order is newest publication first. These native searches do not guarantee topic relevance beyond the source index. Example: `{"searchTerms":["emissions"],"agencies":["environmental-protection-agency"],"documentTypes":["RULE"],"publicationFrom":"2025-01-01","maxDocuments":20}`. ### Output One federal_document row per unique document, with matchedQueries across visited pages. The schema defines every column. Null dates/abstract/action mean the source omitted a value. A CFR reference part is null when the source cites only a title/chapter; no part is invented. `COVERAGE` in key-value storage records each query total, visited pages, stop reason, unvisited searches, global limits and whether complete; `SUMMARY` reconciles delivered rows and request counts. Coverage is not billed or placed in the dataset. Agent use: export EPA emissions publications in a date window with citation/agency/PDF for a human policy review. Schedule runs and compare identities outside the Actor; it stores no cross-run history and sends no alerts. ### Limits 5 searches,500 unique rows,page50,30 wire requests including robots/redirects,180seconds acquisition,300second cloud timeout,256MB. Native API caps searchable paging at2000 results per term. Global or event cap can stop a search and leave later terms unvisited; KVS coverage records this. Data can change while paging; source count changes are recorded and duplicates removed, without claiming immutable/exhaustive corpus snapshots. Acquisition completes before <=50-row charged SDK batches. SDK delivery is not a full-run transaction and has no rollback guarantee. Any required source failure, invalid body, auth/rate-limit/timeout fails before paid output; genuine all-zero matches also fail with coverage and no charge. No browser, proxy, API key or paid external service. Publication fields are informational API renditions. Official PDF links support checking original publications. Source-reported dates are not legal-effect, compliance or currently-open-deadline judgments; verify subsequent amendments/corrections and agency instructions for decisions. No sanction/KYB screening, full-text downloads or legal interpretation. ### Privacy Only public publication/organization metadata and source links. Email/phone patterns are removed from title/abstract/action/identifiers. No contacts, authors, comments, accounts, credentials, raw JSON, personal records or PDF text. Robots-disallowed private/UI paths are not requested. No official seals/logos. # Actor input Schema ## `searchTerms` (type: `array`): Zero to five native full-text terms. Empty means filter-only browse and requires an agency, type, explicit date, or CFR selector; no fallback term. Global cap may leave later searches unvisited. ## `agencies` (type: `array`): Optional native agency slugs, such as environmental-protection-agency. One global filter applies to every search. ## `documentTypes` (type: `array`): Native type codes: RULE, PRORULE, NOTICE or PRESDOCU. Empty selects all. ## `publicationFrom` (type: `string`): Optional inclusive YYYY-MM-DD publication date; empty means no lower bound. ## `publicationTo` (type: `string`): Optional inclusive YYYY-MM-DD date. Empty resolves to UTC today. Future dates are rejected so scheduled future documents are excluded. ## `cfrTitle` (type: `integer`): Optional CFR title 1–50. Zero disables CFR filtering. ## `cfrPart` (type: `string`): Optional numeric CFR part, requires cfrTitle. Empty disables part filter. ## `maxDocuments` (type: `integer`): One global delivered and billed document cap across all searches: 1–500; default20. It is not a per-search cap. ## Actor input object example ```json { "searchTerms": [ "emissions" ], "agencies": [], "documentTypes": [], "publicationFrom": "", "publicationTo": "", "cfrTitle": 0, "cfrPart": "", "maxDocuments": 20 } ``` # Actor output Schema ## `results` (type: `string`): Unique publication rows, charged once per identity. Coverage lives in KVS. # 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 = { "searchTerms": [ "emissions" ] }; // Run the Actor and wait for it to finish const run = await client.actor("jpmarketdata/federal-register-multi-query-document-export").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 = { "searchTerms": ["emissions"] } # Run the Actor and wait for it to finish run = client.actor("jpmarketdata/federal-register-multi-query-document-export").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 '{ "searchTerms": [ "emissions" ] }' | apify call jpmarketdata/federal-register-multi-query-document-export --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/federal-register-multi-query-document-export" } } } ``` 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/dDOX1GYN5EJ08zomf/builds/8JFJc4pNl2mQTJCPk/openapi.json