Regulatory Activity API: Per-agency Federal Register volume with prior-window change
Per-agency Federal Register volume with prior-window change and doc-type totals — which regulators are accelerating, in one call instead of a pagination crawl. Free, no key.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/regs/activity — product id
reg_activity. Over MCP, call answerpool_get with
product_id=reg_activity.
curl "https://answerpool.io/v1/regs/activity?days=90"Live call: https://answerpool.io/v1/regs/activity?days=90 · JSON sample: /v1/samples/reg_activity
What does the answer look like?
A representative response, the same static sample served at /v1/samples/reg_activity.
as_of | 2026-09-03T02:00:00Z |
|---|---|
window_days | 90 |
total_documents | 6949 |
by_type.NOTICE | 5492 |
by_type.RULE | 926 |
by_type.PRORULE | 465 |
by_type.PRESDOCU | 66 |
disclaimer | Regulatory information from the Federal Register (public domain); not legal advice. |
refresh_after | 2026-09-18T00:00:00.000Z |
agencies
| slug | name | documents | prior_window | change_pct |
|---|---|---|---|---|
| commerce-department | Commerce Department | 765 | 690 | 10.9 |
The same sample as raw JSON
{
"as_of": "2026-09-03T02:00:00Z",
"window_days": 90,
"total_documents": 6949,
"by_type": {
"NOTICE": 5492,
"RULE": 926,
"PRORULE": 465,
"PRESDOCU": 66
},
"agencies": [
{
"slug": "commerce-department",
"name": "Commerce Department",
"documents": 765,
"prior_window": 690,
"change_pct": 10.9
}
],
"disclaimer": "Regulatory information from the Federal Register (public domain); not legal advice.",
"refresh_after": "2026-09-18T00:00:00.000Z"
}How fresh is it, and where does the data come from?
The fastest source behind this answer can change daily, so every response carries a refresh_after timestamp — right now it would be 2026-09-18T00:00:00.000Z. Schedule the next call on that value rather than on a guess.
- Federal Register (US federal public domain) — upstream:
https://www.federalregister.gov/api/v1
Method version 0.1.0 ·
serving cache 1 day ·
every response carries a result_id you can resolve at
/v1/provenance.
When should you use it?
You want the agency-level activity map or trend, not the documents.
What you skip building
- paginating the whole Federal Register
- hand-built agency counts
When should you not use it?
The documents themselves — /v1/regs/rules or /v1/regs/agency.
Where else can you find this?
- Catalog entry (JSON, free)
- OpenAPI schema — input and output types, prices, the 402 flow
- llms.txt — every product in one plain-text document