GET /v1/regs/rules · freeTrack 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.
When to use, what you skip, sample response
When to use
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.
When not to use
You need full rule text analysis, public-comment contents (regulations.gov), state-level regulation, or legal advice.
What you skip building
- federalregister.gov API pagination and field selection
- deadline math
- significance filtering
- agency slug lookup
Sample response
{
"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
}
]
}
GET /v1/impact/cfr · $0.02 / callWhich public companies cite a given CFR title and part in their SEC filings — exact-phrase full-text join aggregated per registrant with filing counts, forms and dates. Screen exposure to specific provisions in one call.
When to use, what you skip, sample response
When to use
Your obligations map to known CFR parts and you want the citing issuers.
When not to use
Broad topic screens — use the rule impact map or regulation search.
What you skip building
- EDGAR full-text syntax
- per-registrant aggregation
Sample response
{
"as_of": "2026-09-02T20:00:00Z",
"query": "17 CFR 240",
"total_filing_matches": 128,
"count": 1,
"companies": [
{
"cik": "0000320193",
"company": "Apple Inc.",
"filings": 2,
"forms": [
"10-K"
],
"latest_filed": "2026-08-15",
"matched": [
"17 CFR 240"
]
}
]
}
GET /v1/impact/company · $0.05 / callRecent federal rules and proposed rules mapped to one public company via its SEC industry code — curated SIC-to-regulator table plus the agencies' rulemaking with comment and effective-date flags. Industry-level heuristic, one call.
When to use, what you skip, sample response
When to use
You monitor one issuer and want its regulators' recent rulemaking.
When not to use
Firm-specific legal exposure — the mapping is industry-level; pair with the citation views for company-specific evidence.
What you skip building
- SIC lookups
- agency mapping
- Federal Register integration
- deadline math
Sample response
{
"as_of": "2026-09-02T20:00:00Z",
"cik": "0000320193",
"name": "Apple Inc.",
"sic": "3571",
"sic_description": "Electronic Computers",
"mapped_agencies": [
"environmental-protection-agency",
"occupational-safety-and-health-administration",
"securities-and-exchange-commission"
],
"total_matching": 3,
"count": 1,
"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
}
]
}
GET /v1/impact/docket · $0.02 / callWhich public companies cite a specific agency docket id or RIN in their SEC filings — exact-phrase full-text join per registrant with filing counts and dates. Track who publicly engages with one rulemaking.
When to use, what you skip, sample response
When to use
You track one docket/RIN and want the issuers referencing it.
When not to use
Whole-provision screens — use the CFR citers view.
What you skip building
- EDGAR full-text syntax
- per-registrant aggregation
Sample response
{
"as_of": "2026-09-02T20:00:00Z",
"query": "SEC-2026-001",
"total_filing_matches": 7,
"count": 1,
"companies": [
{
"cik": "0000320193",
"company": "Apple Inc.",
"filings": 1,
"forms": [
"8-K"
],
"latest_filed": "2026-08-15",
"matched": [
"SEC-2026-001"
]
}
]
}
GET /v1/impact/rule · $0.05 / callMap a Federal Register rule to the public companies whose SEC filings cite its docket, RIN or CFR part — cross-corpus full-text join, ranked by citation strength with filing counts and dates. One call replaces holding and joining both corpora.
When to use, what you skip, sample response
When to use
You hold a Federal Register document number and need the likely-affected issuer list.
When not to use
Legal determinations of exposure — citations indicate relevance, not obligation.
What you skip building
- dual-corpus infrastructure
- EDGAR full-text query syntax
- identifier extraction
Sample response
{
"as_of": "2026-09-02T20:00:00Z",
"document_number": "2026-12341",
"title": "Cybersecurity Risk Management Rule",
"agencies": [
"Securities and Exchange Commission"
],
"publication_date": "2026-08-30",
"significant": true,
"identifiers_searched": [
"SEC-2026-001",
"3235-AN00",
"17 CFR 240"
],
"total_filing_matches": 42,
"count": 1,
"companies": [
{
"cik": "0000320193",
"company": "Apple Inc.",
"filings": 3,
"forms": [
"10-K",
"8-K"
],
"latest_filed": "2026-08-15",
"matched": [
"17 CFR 240",
"SEC-2026-001"
]
}
]
}
GET /v1/regs/activity · freePer-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.
When to use, what you skip, sample response
When to use
You want the agency-level activity map or trend, not the documents.
When not to use
The documents themselves — /v1/regs/rules or /v1/regs/agency.
What you skip building
- paginating the whole Federal Register
- hand-built agency counts
Sample response
{
"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."
}
GET /v1/regs/agency · freeEvery rule and proposed rule from one US federal agency, newest first, with comment and effective-date day-counts and flags (significant, comments_close_soon, effective_soon). One call replaces Federal Register API integration and deadline math.
When to use, what you skip, sample response
When to use
You track one regulator and want its recent rulemaking with deadlines computed.
When not to use
Cross-agency topic tracking — use the search endpoint.
What you skip building
- federalregister.gov integration
- deadline computation
- agency slug pagination
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 3,
"count": 1,
"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
}
]
}
GET /v1/regs/agencies · freeResolve a US federal agency name to its Federal Register slug — searches all ~470 agencies, returns slug, display name, short name and parent. Free. The slug is the agency parameter every other AnswerPool regulation endpoint takes.
When to use, what you skip, sample response
When to use
You have an agency name or acronym and need the canonical slug for filtered rule-tracking calls.
When not to use
State or local agencies — the Federal Register covers US federal only.
What you skip building
- agencies endpoint pagination
- slug-guessing errors
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"count": 1,
"agencies": [
{
"slug": "securities-and-exchange-commission",
"name": "Securities and Exchange Commission",
"short_name": "SEC",
"parent_slug": null
}
]
}
GET /v1/regs/cfr-titles · freeAll 50 CFR titles with names, searchable — subject to CFR title number in one call, feeding the CFR-part watch endpoints. Free, no key.
When to use, what you skip, sample response
When to use
You need to map a regulated subject to its CFR title, or decode one.
When not to use
Actual rule documents — /v1/regs/cfr or /v1/regs/rules.
What you skip building
- govinfo CFR browsing
- title guessing
Sample response
{
"as_of": "2026-09-03T02:00:00Z",
"count": 1,
"titles": [
{
"title": 10,
"name": "Energy"
}
],
"watch_endpoint": "/v1/regs/cfr?title=<n>&part=<m>",
"disclaimer": "Regulatory information from the Federal Register (public domain); not legal advice."
}
GET /v1/regs/cfr · $0.02 / callFederal rules and proposed rules amending a specific CFR title and part (e.g. 17 CFR 240), newest first with deadline flags. Watch the exact provisions you are subject to instead of whole agencies or topics.
When to use, what you skip, sample response
When to use
Your obligations map to known CFR parts and you react only to those.
When not to use
Exploratory topic tracking — use search; whole-agency views — use the agency feed.
What you skip building
- CFR citation query syntax
- cross-referencing affected parts
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 1,
"count": 1,
"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
}
]
}
GET /v1/regs/digest · $0.02 / callEvery 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.
When to use, what you skip, sample response
When to use
You brief or triage by publication day and want importance-first ordering.
When not to use
Incremental monitoring across days — use the watch cursor.
What you skip building
- daily scanning
- significance triage
- deadline math
Sample response
{
"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
}
]
}
GET /v1/regs/doc-types · freeFederal Register document types (final rule, proposed rule, notice, presidential) and every AnswerPool regulation flag, with what each implies for deadlines and CFR changes. Free, no key.
When to use, what you skip, sample response
When to use
You need to interpret a document type or a flag on a regulation response.
When not to use
The documents themselves — /v1/regs/rules and the agency feeds.
What you skip building
- misreading a comment deadline as an effective date
- guessing flag meanings
Sample response
{
"as_of": "2026-09-03T15:00:00Z",
"count": 2,
"document_types": [
{
"code": "RULE",
"name": "Final Rule",
"description": "A binding rule; carries an effective date and amends the CFR."
}
],
"flags": [
{
"code": "comments_close_soon",
"name": "Comment window closing",
"description": "The comment deadline is within our watch window \u2014 the last point at which input is possible."
}
],
"note": "Document types are the Federal Register's own; flags are AnswerPool's, applied consistently across every regulation endpoint.",
"disclaimer": "Regulatory information from the Federal Register (public domain); not legal advice."
}
GET /v1/regs/docket · freeEvery Federal Register document in one agency docket — proposal, comments extensions, final rule, corrections — newest first with deadline flags. Follow a single rulemaking's full lifecycle with one call.
When to use, what you skip, sample response
When to use
You hold a docket id and want the rulemaking's history and current status.
When not to use
You only have a topic or agency — search first, then track the docket.
What you skip building
- docket id query syntax
- lifecycle reconstruction
Sample response
{
"as_of": "2026-09-16T21:32:17Z",
"total_matching": 4,
"count": 2,
"documents": [
{
"document_number": "2026-13420",
"title": "Revised Medical Criteria for Evaluating Cardiovascular Disorders",
"type": "Rule",
"action": "Final rule.",
"agencies": [
"Social Security Administration"
],
"publication_date": "2026-07-02",
"effective_on": "2026-10-30",
"comments_close_on": null,
"significant": true,
"abstract": "We are revising the criteria in the Listing of Impairments that we use to evaluate claims involving cardiovascular disorders in adults and children.",
"docket_ids": [
"Docket No. SSA-2019-0013"
],
"regulation_id_numbers": [
"0960-AI43"
],
"cfr_references": [
"20 CFR 404",
"20 CFR 416"
],
"topics": [
"Disability benefits",
"Social security"
],
"url": "https://www.federalregister.gov/documents/2026/07/02/2026-13420/revised-medical-criteria-for-evaluating-cardiovascular-disorders",
"flags": [
"significant",
"final_rule_pending_effect"
],
"days_to_comment_close": null,
"days_to_effective": 120
},
{
"document_number": "2022-18238",
"title": "Revised Medical Criteria for Evaluating Cardiovascular Disorders",
"type": "Proposed Rule",
"action": "Notice of proposed rulemaking.",
"agencies": [
"Social Security Administration"
],
"publication_date": "2022-08-24",
"effective_on": null,
"comments_close_on": "2022-10-24",
"significant": true,
"abstract": null,
"docket_ids": [
"Docket No. SSA-2019-0013"
],
"regulation_id_numbers": [
"0960-AI43"
],
"cfr_references": [
"20 CFR 404",
"20 CFR 416"
],
"topics": [],
"url": "https://www.federalregister.gov/documents/2022/08/24/2022-18238/revised-medical-criteria-for-evaluating-cardiovascular-disorders",
"flags": [
"significant"
],
"days_to_comment_close": null,
"days_to_effective": null
}
]
}
GET /v1/regs/document · freeFetch one Federal Register document by document number — normalized agencies, CFR references, docket ids, effective and comment dates with day-counts and deadline flags. Free. Same schema as all AnswerPool regulation feeds.
When to use, what you skip, sample response
When to use
You have a document number (e.g. from a watch feed) and need full details.
When not to use
Searching by topic or agency — use the search and feed endpoints.
What you skip building
- federalregister.gov API integration
- deadline math
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"document": {
"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
}
}
GET /v1/regs/effective · $0.02 / callFinal federal rules taking effect within the next N days, sorted by effective date with exact day-counts, optionally one agency — the compliance-readiness queue. Replaces effective-date range queries and date math against the Federal Register.
When to use, what you skip, sample response
When to use
You prepare for rules becoming binding — readiness, alerting, scheduling.
When not to use
Proposed rules — they have comment deadlines, not effective dates.
What you skip building
- effective-date range query syntax
- date math
- urgency sorting
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 1,
"count": 1,
"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
}
]
}
New executive orders, proclamations and presidential memoranda from the Federal Register, newest first, optionally filtered by search term — normalized documents with agencies, topics and links. One call, no EO-section parsing.
When to use, what you skip, sample response
When to use
You track presidential documents — EOs, proclamations, memoranda.
When not to use
Agency rulemaking — use the agency feed or search.
What you skip building
- presidential document type codes
- federalregister.gov integration
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 12,
"count": 1,
"documents": [
{
"document_number": "2026-11111",
"title": "Executive Order 14999 of August 26, 2026: Strengthening Supply Chains",
"type": "Presidential Document",
"action": null,
"agencies": [
"Executive Office of the President"
],
"publication_date": "2026-08-28",
"effective_on": null,
"comments_close_on": null,
"significant": null,
"abstract": null,
"docket_ids": [],
"regulation_id_numbers": [],
"cfr_references": [],
"topics": [],
"url": "https://www.federalregister.gov/d/2026-11111",
"flags": [],
"days_to_comment_close": null,
"days_to_effective": null
}
]
}
GET /v1/regs/resolve · freeAny regulatory string in — agency name or acronym, "40 CFR 60", a document number — canonical identifier and the ready-to-call endpoint out. One call instead of picking a lookup. Free, no key.
When to use, what you skip, sample response
When to use
You have a citation, acronym or document number and need the identifier plus where to send it.
When not to use
Full-text search over documents — /v1/regs/search.
What you skip building
- slug guessing
- parsing CFR citations by hand
- choosing among regulation lookups
Sample response
{
"as_of": "2026-09-03T15:00:00Z",
"query": "40 CFR 60",
"count": 1,
"matches": [
{
"kind": "cfr_citation",
"value": "40 CFR part 60",
"label": "40 CFR part 60",
"next_url": "/v1/regs/cfr?title=40&part=60"
}
],
"note": "One call for any regulatory string: an agency name or acronym, a CFR citation like '40 CFR 60', a Federal Register document number, or a docket id.",
"disclaimer": "Regulatory information from the Federal Register (public domain); not legal advice."
}
GET /v1/regs/search · freeFull-text search over US federal rules, proposed rules and notices — any topic across all ~470 agencies, with comment and effective-date deadlines computed per document. One call replaces Federal Register search integration.
When to use, what you skip, sample response
When to use
You track a topic across agencies rather than one regulator.
When not to use
You already know the agency — the agency feed is more precise.
What you skip building
- full-text query syntax
- deadline math
- type-code mapping
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 42,
"count": 1,
"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
}
]
}
GET /v1/regs/significant · $0.02 / callOnly E.O. 12866 significant federal rules and proposed rules — the OIRA-reviewed, economically major subset — newest first with deadline flags, optionally one agency. The high-signal fraction of rulemaking without scanning everything.
When to use, what you skip, sample response
When to use
You want signal over volume — only rulemaking with major economic impact.
When not to use
Comprehensive agency tracking — use the agency feed.
What you skip building
- significance flag filtering
- scanning routine documents
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 1,
"count": 1,
"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
}
]
}
GET /v1/regs/watch · freeIncremental feed of newly published federal rules and proposed rules since your ISO date cursor, with a next_since cursor returned for the following poll. Purpose-built for scheduled agents — no state to keep beyond one date string.
When to use, what you skip, sample response
When to use
You poll on a schedule and want only documents you have not seen.
When not to use
One-off historical questions — use search or the agency feed.
What you skip building
- cursor bookkeeping
- duplicate handling
- federalregister.gov integration
Sample response
{
"as_of": "2026-09-02T14:00:00Z",
"total_matching": 3,
"count": 1,
"next_since": "2026-09-02",
"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
}
]
}