> This is the Markdown form of https://fapd.info/sources/crs-reports.html. Content is licensed CC BY 4.0 > (credit "FAPD — Free Agentic Publication Digester"); quoted official government > text is public domain. For factual claims, cite the official source each item > links to. Canonical source: `sources/registry.yaml (id: crs-reports)` in https://github.com/davidkarnowski/free-agentic-publication-digester. # CRS Reports planned · Legislative · Tier 1 · API · Congressional Research Service Official site: https://crsreports.congress.gov/ · All sources: [sources.md](../sources.md) ## What this source is The Congressional Research Service provides nonpartisan policy and legal analysis to members and committees of Congress. New and updated CRS reports, released under 2018 appropriations law, typically several items per business day. **Model-written orientation** The Congressional Research Service provides nonpartisan policy and legal research to members and committees of Congress, publishing analysis on a wide range of legislative and policy topics. New and updated reports typically appear several times per business day. The Congressional Research Service (CRS) is the public policy research arm of the United States Congress, providing nonpartisan analysis, research, and legal interpretation to members of Congress and congressional committees. CRS is part of the Library of Congress and operates without partisan affiliation, serving members of both parties equally. The service employs subject-matter specialists, lawyers, analysts, and researchers with expertise spanning domestic policy, foreign affairs, economics, law, and other fields relevant to congressional work. CRS conducts research and analysis on a comprehensive range of topics including federal legislation and enacted laws, constitutional questions and legal interpretation, federal agency policies and programs, international affairs and diplomatic developments, domestic policy questions across all areas of federal responsibility, and economic and fiscal policy. Each report provides background, analysis of relevant facts and issues, legal context where applicable, and information relevant to congressional consideration. CRS reports are released publicly under the 2018 appropriations law, which requires CRS to make its research available to the public. CRS reports vary considerably in length and depth, ranging from brief issue summaries and fact sheets addressing specific current questions to comprehensive research products providing extensive background and analysis. Reports are updated regularly as circumstances change and new information becomes available. The service conducts research on request from congressional members and committees, and research priorities reflect current congressional interests and legislative activity. Readers will encounter authoritative nonpartisan analysis on topics ranging from pending legislation under congressional consideration to ongoing policy questions, constitutional issues, and international developments. New and updated reports are published frequently throughout the year, typically resulting in several new or revised items per business day. Readers can expect in-depth, balanced analysis designed to inform congressional decision-making and oversight. _Model-written orientation, generated 2026-08-04 by haiku, prompt version 1. It may draw on general knowledge of public institutions and is not official-record content._ ## Identity and registry record | Field | Value | |---|---| | Registry id | `crs-reports` | | Agency / parent organization | Congressional Research Service | | Branch | legislative | | Type | API | | Status | planned | | Tier | 1 | | URL (home) | https://crsreports.congress.gov/ | | URL (index) | https://api.congress.gov/v3/crsreport | | Registered | 2026-07-26 | | Registry notes | crsreports.congress.gov itself: HTTP 403 to honestly-identified automated client (WAF, probed 2026-07-26) and publishes no machine-access documentation — that path stays closed. Research 2026-07-28: the officially documented channel is the Congress.gov API crsreport endpoint (LoC GitHub docs, CRSReportEndpoint.md read): product IDs, pub/update dates, titles, authors, topics, summaries, and format-URL containers. Metadata + summaries alone are digest-worthy; whether the congress.gov-hosted full-text URLs fetch cleanly for our client needs probe. | ## How we ingest it | Term | Description | |---|---| | Channel | API | | Method | Would delta-sync the api.congress.gov crsreport endpoint (same api.data.gov key the pipeline already holds). | | Request budget | the agency class: at most 3,000 requests per day shared across every agency web source, counted from the fetch log (failed requests count too) | | Politeness | robots.txt is honored as observed — including each host's crawl-delay, exactly — and every request identifies itself as fapd/0.1 (Free Agentic Publication Digester; +https://fapd.info/bot.html; contact: hustleyourcity@gmail.com); a refusal is recorded, never evaded | | Capture and hash | captured raw content is hashed (SHA-256) into the day's committed provenance manifest, hash-chained day to day (PROVENANCE.md) | ## Ingestion health Not ingested: the registry status of this source is planned. ## Ingestion statistics These figures describe this project's ingestion of this source — items we recorded and requests we made — and nothing else. They are not a measurement of the publisher. Not ingested: the registry status of this source is planned. Ingestion statistics are measured for active sources only. ### All time - **Our requests to api.congress.gov, all time (since 2026-08-01):** 1,706 request(s) · 1,639 answered · 67 returned no content Request counts begin 2026-07-30, the day this service went into production; earlier development-machine traffic is excluded. Counts before 2026-08-03 include unmarked source-probe traffic; probes are labeled and excluded thereafter. ### Last 30 days, day by day Each day runs midnight to midnight on Eastern time (Washington, D.C.), the publication day the digests use; the stored request stamps remain UTC. | Day | Items ingested | Requests to api.congress.gov | Mean response time (ms) | |---|---|---|---| | 2026-08-31 | 0 | 26 | 314 | | 2026-09-01 | 0 | 26 | 946 | | 2026-09-02 | 0 | 26 | 499 | | 2026-09-03 | 0 | 26 | 539 | | 2026-09-04 | 0 | 26 | 361 | | 2026-09-05 | 0 | 33 | 418 | | 2026-09-06 | 0 | 27 | 306 | | 2026-09-07 | 0 | 26 | 296 | | 2026-09-08 | 0 | 26 | 310 | | 2026-09-09 | 0 | 26 | 318 | | 2026-09-10 | 0 | 25 | 336 | | 2026-09-11 | 0 | 26 | 315 | | 2026-09-12 | 0 | 29 | 436 | | 2026-09-13 | 0 | 26 | 294 | | 2026-09-14 | 0 | 30 | 464 | | 2026-09-15 | 0 | 26 | 317 | | 2026-09-16 | 0 | 26 | 342 | | 2026-09-17 | 0 | 26 | 447 | | 2026-09-18 | 0 | 26 | 465 | | 2026-09-19 | 0 | 26 | 295 | | 2026-09-20 | 0 | 26 | 318 | | 2026-09-21 | 0 | 28 | 368 | | 2026-09-22 | 0 | 26 | 296 | | 2026-09-23 | 0 | 25 | 319 | | 2026-09-24 | 0 | 25 | 320 | | 2026-09-25 | 0 | 26 | 358 | | 2026-09-26 | 0 | 26 | 717 | | 2026-09-27 | 0 | 27 | 354 | | 2026-09-28 | 0 | 29 | 991 | | 2026-09-29 | 0 | 9 | 267 |