Regulation Radar API: Recent federal rules and proposed rules mapped to one public company — Federal Register

Recent 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.

$0.05 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/impact/company — product id impact_company_rules. Over MCP, call answerpool_get with product_id=impact_company_rules.

curl "https://answerpool.io/v1/impact/company?ticker=AAPL"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/impact/company?ticker=AAPL"

Live call: https://answerpool.io/v1/impact/company?ticker=AAPL · JSON sample: /v1/samples/impact_company_rules

What does the answer look like?

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

documents

{
 "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
  }
 ],
 "refresh_after": "2026-09-17T11:15:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15: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
• SEC EDGAR (US federal public domain) — upstream: https://efts.sec.gov

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 monitor one issuer and want its regulators' recent rulemaking.

What you skip building

• SIC lookups
• agency mapping
• Federal Register integration
• deadline math

When should you not use it?

Firm-specific legal exposure — the mapping is industry-level; pair with the citation views for company-specific evidence.

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