Federal Rules Tracker API: Track US federal rules by term or agency — Federal Register

Name: Federal Rules Tracker API: Track US federal rules by term or agency — Federal Register
Creator: AnswerPool
License: https://www.usa.gov/government-works

Track US federal rules by term or agency — returns Federal Register rules and proposed rules with docket/RIN/CFR ids, effective and comment-close dates, deadline flags and day counts. Use instead of polling federalregister.gov.

Free — no key, no signup, rate-limited to 60 calls per minute per client.

How do you call it?

GET /v1/regs/rules — product id reg_rules. Over MCP, call answerpool_get with product_id=reg_rules.

curl "https://answerpool.io/v1/regs/rules?term=artificial+intelligence"

Live call: https://answerpool.io/v1/regs/rules?term=artificial+intelligence · JSON sample: /v1/samples/reg_rules

What does the answer look like?

A representative response, the same static sample served at /v1/samples/reg_rules.

`as_of`	2026-08-30T18:00:00Z
`total_matching`	14
`count`	1
`refresh_after`	2026-09-18T00:00:00.000Z

`documents`

document_number	title	type	action	agencies	publication_date	effective_on	comments_close_on	significant	abstract	docket_ids	regulation_id_numbers
2026-15872	Regulation Crypto Assets	Proposed Rule	Proposed rule	Securities and Exchange Commission	2026-08-21	—	2026-10-20	true	The Commission proposes a framework for crypto asset securities...	S7-12-26	3235-AN70

The same sample as raw JSON

{
 "as_of": "2026-08-30T18:00:00Z",
 "total_matching": 14,
 "count": 1,
 "documents": [
  {
   "document_number": "2026-15872",
   "title": "Regulation Crypto Assets",
   "type": "Proposed Rule",
   "action": "Proposed rule",
   "agencies": [
    "Securities and Exchange Commission"
   ],
   "publication_date": "2026-08-21",
   "effective_on": null,
   "comments_close_on": "2026-10-20",
   "significant": true,
   "abstract": "The Commission proposes a framework for crypto asset securities...",
   "docket_ids": [
    "S7-12-26"
   ],
   "regulation_id_numbers": [
    "3235-AN70"
   ],
   "cfr_references": [
    "17 CFR 230"
   ],
   "topics": [
    "securities"
   ],
   "url": "https://www.federalregister.gov/documents/2026/08/21/2026-15872",
   "flags": [
    "significant",
    "comments_close_soon"
   ],
   "days_to_comment_close": 51,
   "days_to_effective": null
  }
 ],
 "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 need current federal rulemaking activity for a topic or agency — new proposals, imminent effective dates, closing comment windows — as structured JSON in one call.

What you skip building

federalregister.gov API pagination and field selection
deadline math
significance filtering
agency slug lookup

When should you not use it?

You need full rule text analysis, public-comment contents (regulations.gov), state-level regulation, or legal advice.

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