Rulemaking Digest API: Every federal rule and proposed rule published on one date, significant — Federal Register

Every federal rule and proposed rule published on one date, significant documents sorted first, with deadline flags and day-counts — optionally one agency. One call gives a briefing agent the whole day's rulemaking, pre-triaged.

$0.02 per call — pay with prepaid card credits (Authorization: Bearer ck_live_…, packs from $1) or with USDC over x402: call it, get 402 with the price, retry signed. Failed calls are never charged.

How do you call it?

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

curl "https://answerpool.io/v1/regs/digest?agency=securities-and-exchange-commission"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/regs/digest?agency=securities-and-exchange-commission"

Live call: https://answerpool.io/v1/regs/digest?agency=securities-and-exchange-commission · JSON sample: /v1/samples/reg_daily_digest

What does the answer look like?

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

documents

{
 "as_of": "2026-09-02T14:00:00Z",
 "total_matching": 3,
 "count": 2,
 "documents": [
  {
   "document_number": "2026-12341",
   "title": "Cybersecurity Risk Management Rule",
   "type": "Rule",
   "action": "Final rule.",
   "agencies": [
    "Securities and Exchange Commission"
   ],
   "publication_date": "2026-08-30",
   "effective_on": "2026-09-12",
   "comments_close_on": null,
   "significant": true,
   "abstract": "Requires registrants to disclose material cybersecurity incidents.",
   "docket_ids": [
    "SEC-2026-001"
   ],
   "regulation_id_numbers": [
    "3235-AN00"
   ],
   "cfr_references": [
    "17 CFR 240"
   ],
   "topics": [
    "Securities"
   ],
   "url": "https://www.federalregister.gov/d/2026-12341",
   "flags": [
    "significant",
    "effective_soon",
    "final_rule_pending_effect"
   ],
   "days_to_comment_close": null,
   "days_to_effective": 10
  },
  {
   "document_number": "2026-12343",
   "title": "Technical Corrections",
   "type": "Rule",
   "action": "Final rule; correction.",
   "agencies": [
    "Securities and Exchange Commission"
   ],
   "publication_date": "2026-08-30",
   "effective_on": "2026-08-28",
   "comments_close_on": null,
   "significant": null,
   "abstract": null,
   "docket_ids": [],
   "regulation_id_numbers": [],
   "cfr_references": [],
   "topics": [],
   "url": "https://www.federalregister.gov/d/2026-12343",
   "flags": [],
   "days_to_comment_close": null,
   "days_to_effective": -5
  }
 ],
 "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 brief or triage by publication day and want importance-first ordering.

What you skip building

• daily scanning
• significance triage
• deadline math

When should you not use it?

Incremental monitoring across days — use the watch cursor.

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