Rule Impact Map API: Map a Federal Register rule to the public companies whose SEC filings
Map 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.
$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/rule — product id
impact_rule_companies. Over MCP, call answerpool_get with
product_id=impact_rule_companies.
curl "https://answerpool.io/v1/impact/rule?document_number=2026-12341"
# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/impact/rule?document_number=2026-12341"
Live call: https://answerpool.io/v1/impact/rule?document_number=2026-12341 · JSON sample: /v1/samples/impact_rule_companies
What does the answer look like?
A representative response, the same static sample served at /v1/samples/impact_rule_companies.
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 |
refresh_after | 2026-09-17T11:15:00.000Z |
companies
| cik | company | filings | forms | latest_filed | matched |
|---|---|---|---|---|---|
| 0000320193 | Apple Inc. | 3 | 10-K, 8-K | 2026-08-15 | 17 CFR 240, SEC-2026-001 |
The same sample as raw JSON
{
"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"
]
}
],
"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 hold a Federal Register document number and need the likely-affected issuer list.
What you skip building
- dual-corpus infrastructure
- EDGAR full-text query syntax
- identifier extraction
When should you not use it?
Legal determinations of exposure — citations indicate relevance, not obligation.
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