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.

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 1,500 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): 122 request(s) · 118 answered · 4 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

Requests per day to api.congress.gov: 122 requests over the last 5 days (peak 55 on 2026-08-02).
Requests per day to api.congress.gov: 122 requests over the last 5 days (peak 55 on 2026-08-02).
Dayrequests
2026-07-300
2026-07-310
2026-08-0146
2026-08-0255
2026-08-0321
Daily mean response time of api.congress.gov: between 274 and 620 ms across the last 5 days (days without a timed request are gaps, not zeroes).
Daily mean response time of api.congress.gov: between 274 and 620 ms across the last 5 days (days without a timed request are gaps, not zeroes).
Dayms
2026-07-30
2026-07-31
2026-08-01288
2026-08-02274
2026-08-03620