CRS Reports

planned Legislative · Tier 1 · API · Congressional Research Service

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

Registry id
crs-reports
Agency / parent organization
Congressional Research Service
Branch
legislative
Type
API
Status
planned
Tier
1
URL (home)
https://crsreports.congress.gov/ (opens in a new tab)
URL (index)
https://api.congress.gov/v3/crsreport (opens in a new tab)
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

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 sources the pipeline reads.

All time

Our requests to api.congress.gov, all time (since 2026-08-01): 1,707 request(s) · 1,640 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.

Requests per day to api.congress.gov: 782 requests over the last 30 days (peak 33 on 2026-09-05).
Requests per day to api.congress.gov: 782 requests over the last 30 days (peak 33 on 2026-09-05).
Dayrequests
2026-08-3126
2026-09-0126
2026-09-0226
2026-09-0326
2026-09-0426
2026-09-0533
2026-09-0627
2026-09-0726
2026-09-0826
2026-09-0926
2026-09-1025
2026-09-1126
2026-09-1229
2026-09-1326
2026-09-1430
2026-09-1526
2026-09-1626
2026-09-1726
2026-09-1826
2026-09-1926
2026-09-2026
2026-09-2128
2026-09-2226
2026-09-2325
2026-09-2425
2026-09-2526
2026-09-2626
2026-09-2727
2026-09-2829
2026-09-2910
Daily mean response time of api.congress.gov: between 268 and 991 ms across the last 30 days (days without a timed request are gaps, not zeroes).
Daily mean response time of api.congress.gov: between 268 and 991 ms across the last 30 days (days without a timed request are gaps, not zeroes).
Dayms
2026-08-31314
2026-09-01946
2026-09-02499
2026-09-03539
2026-09-04361
2026-09-05418
2026-09-06306
2026-09-07296
2026-09-08310
2026-09-09318
2026-09-10336
2026-09-11315
2026-09-12436
2026-09-13294
2026-09-14464
2026-09-15317
2026-09-16342
2026-09-17447
2026-09-18465
2026-09-19295
2026-09-20318
2026-09-21368
2026-09-22296
2026-09-23319
2026-09-24320
2026-09-25358
2026-09-26717
2026-09-27354
2026-09-28991
2026-09-29268