The Long-Tail Regulators: CFTC, FCC, FERC, DOE, and CPSC Guidance in One API

Five sector regulators publish the guidance their industries actually run on, and it is easy to miss in a general legal search. CFTC staff letters (947, 2008 to present), FCC declaratory rulings (174), FERC policy statements (82, since 1996), DOE appliance standards guidance and FAQs (60), and CPSC advisory opinions (305, 1973 to 2012) are each small enough to fall off a coverage roadmap and load-bearing enough that a compliance team in that sector can't work without them. They sit inside an AGENCY_GUIDANCE corpus of more than 50 named federal sources, each reachable with a single source= filter. This post gives the counts, the coverage windows, the citation form each one uses, and one honest sentence per source on who needs it.

Reviewed and corrected on 12 October 2026. This is general information, not legal advice. Counts come from our agency guidance coverage page, measured on 7 September 2026. We re-checked the DOE count (60) and the CPSC compliance guide count (34) against the live API on 12 October 2026; GET /us/statutes/coverage and that page are authoritative if a figure has moved.

TL;DR

• Six sector guidance sets, one filter. cftc_staff_letter (947), fcc_declaratory_ruling (174), ferc_policy_statement (82), doe_appliance_guidance (60), cpsc_advisory_opinion (305), and cpsc_secg (34).
• A larger source than any of these five is not a famous one. Social Security Administration Rulings, at 1,116 documents, outnumber each of the five sector regulators covered here.
• FERC Policy Statements are deliberately scoped. They are FERC's generally applicable interpretive vehicle, narrower on purpose than the docket-based eLibrary universe of case-specific orders.
• The CPSC advisory opinion set is a historical archive. It runs 1973 to 2012 and is labelled an archive. We label it rather than implying it is live.
• Small is the point. These sources are each too small to move a coverage headline, and they are the ones a derivatives lawyer or an energy regulatory team may touch every week.
• Unknown filter values fail loudly. A bad source code returns 422 with the full list of valid codes, so the API documents itself instead of returning zero results that look like a coverage gap.

The long tail of our federal agency guidance series.

For related coverage, see Federal Agency Guidance API: 53 Sub-Regulatory Sources in One Endpoint for the whole map, Banking and AML Guidance API: OCC, FDIC, Federal Reserve, and FinCEN in One Query for the prudential side of the CFTC's neighborhood, and HIPAA Guidance API: HHS OCR FAQs, Guidance, and Enforcement Actions.

Why nobody aggregates these

Coverage is easy to measure by volume. A source with a few dozen documents in it doesn't move a headline number, and it takes about as much work to ingest as one with tens of thousands.

So a small source is easy to leave off a coverage list, and the people who need it end up tracking it by hand, with lists of letter numbers and bookmarks to agency landing pages.

The counter-argument is straightforward. A corpus of under a thousand documents that a derivatives lawyer opens weekly is worth more per document than a million sections nobody queries. Coverage that matches a job isn't the same thing as coverage that is large.

The six at a glance

CFTC Staff Letters: 947 documents, 2008 to present

CFTC staff letters have a short but eventful history. The agency itself dates the CFTC to 1974, when the Commodity Futures Trading Commission Act created it, at a time when most futures trading was agricultural. The letters are what grew up around that statute as markets got stranger.

CFTC staff letters are how the Commission's divisions tell a market participant what they will and won't recommend enforcement on. The set covers three instrument types: no-action, exemptive, and interpretative letters.

That distinction isn't cosmetic. A no-action letter says staff won't recommend enforcement on facts as represented. An exemptive letter grants relief under a delegated authority. An interpretative letter states how staff reads a rule. Treating them as one undifferentiated pile is how people misread the scope of their own relief.

The query pattern that matters in practice is a topic, not a letter number. A swap dealer compliance lead doesn't search for a letter number. They search "what has staff said about Part 23 recordkeeping," and want the letters ranked, not a list of PDFs sorted by date.

A quick story: the letter that was withdrawn

One of the best-known no-action letter stories of the last decade is PredictIt. In October 2014 the CFTC's Division of Market Oversight issued Victoria University of Wellington a letter saying it would not recommend enforcement against the university's small political prediction market. Nearly eight years later, on August 4, 2022, the CFTC withdrew CFTC Letter No. 14-130, saying the university "has not operated its market in compliance with the terms of the letter," and set February 15, 2023 as the deadline to close out positions.

Traders took it to court. On July 21, 2023, in Clarke v. CFTC (No. 22-51124), the Fifth Circuit held that the withdrawal was likely arbitrary and capricious and sent the case back so the district court could enter a preliminary injunction. The same opinion, quoting the CFTC's rule at 17 C.F.R. 140.99(a)(2), lays out the ground rules: staff "will not recommend enforcement action," only the issuing division is bound, and "[o]nly the Beneficiary may rely upon the no-action letter." What happened afterwards isn't covered here, so check the docket before you cite the outcome.

When the news broke, one Hacker News commenter wrote that "relying on a No Action Letter always involves the risk that the view of the staff/Commission will change" (elliekelly, Hacker News, August 2022). Eight years of reliance, and the paper underneath it was still a staff position. That is why you read the whole letter, conditions included.

Who needs it, honestly: anyone whose registration status, relief, or reporting obligation rests on a staff position rather than on the text of a regulation. If you are reading the regulation text and stopping there, you are reading half of it.

FCC Declaratory Rulings: 174 documents

Declaratory rulings are how the FCC resolves a controversy or removes uncertainty about how its rules apply, without running a full rulemaking. They are cited by the FCC's own release number: a DA number when a Bureau releases the ruling (DA-20-670 in the corpus) and an FCC number when the full Commission does (FCC-22-85). Neither is a U.S.C. or C.F.R. shape, which trips up naive citation parsers.

The TCPA is the obvious reason to care. A large fraction of consent, revocation, and autodialer questions turn on an FCC declaratory ruling rather than on the TCPA statute itself, and the rulings interact with each other in ways that a statute-only search won't surface.

What the Supreme Court said in 2025

For years, some courts, the Ninth Circuit among them, treated a final FCC order as binding on district courts. In June 2025 the Supreme Court changed that. McLaughlin Chiropractic Associates v. McKesson started as a suit over unsolicited faxes, which carry statutory minimum damages of $500 per violation. While it was pending, the FCC issued a declaratory ruling that online fax services don't count as a "telephone facsimile machine," and the district court treated it as binding and decertified the class. The Supreme Court's holding, in the official opinion dated June 20, 2025: "The Hobbs Act does not preclude district courts in enforcement proceedings from independently assessing whether an agency's interpretation of the relevant statute is correct." District courts decide what the statute means themselves, while giving the agency's reading appropriate respect.

So a declaratory ruling is still evidence of what the agency thinks, and judges will read it. It just isn't the last word. Reading the ruling and the statute together is now the safer habit.

Developers have long had opinions on how far FCC readings stretch. When a federal appeals court struck down an FCC robocall rule in March 2018, one Hacker News commenter wrote: "I agree with the court's ruling. The rule, as written, is far too broad." (whack, Hacker News, March 2018).

Who needs it, honestly: TCPA defense counsel and any team building a consent or outbound-contact workflow that has to survive a class action.

FERC Policy Statements: 82 documents, since 1996

These are long documents. A policy statement isn't a one-page letter, and splitting long documents into passages is what makes semantic retrieval land on the relevant discussion instead of returning a very long PDF whole.

They are cited in the bound-volume FERC Reports form, such as 161 FERC ¶ 61,078 on a record we pulled on 12 October 2026, which is a paragraph-numbered citation into the Commission's own reporter series rather than a document number. Some records carry a docket-style citation instead (Docket No. PL06-1-000). If your citation parser only knows U.S.C. and C.F.R. shapes, it won't recognize a FERC cite at all.

Who needs it, honestly: energy regulatory practices and utility compliance teams who need the Commission's stated policy on a topic, as distinct from what it held on one set of facts.

DOE Appliance Standards Guidance and FAQs: 60 documents

The Department of Energy's appliance and equipment standards program publishes guidance and FAQs that answer the questions a manufacturer actually has: which test procedure applies, how a certification report should read, what happens on a product redesign.

Draft guidance is deliberately excluded from this set. Draft guidance is a proposal, and serving it next to final guidance with no distinction is how a compliance team ends up citing something that never took effect. If you need drafts, check DOE's own site. The exclusion is a scoping choice, and our coverage page lists this source as "Draft guidance excluded".

Who needs it, honestly: appliance and equipment manufacturers, and the product compliance consultants who file certification reports on their behalf.

CPSC: 305 advisory opinions plus 34 compliance guides

Two different sets with two different jobs.

CPSC OGC Advisory Opinions, 305 documents, 1973 to 2012. Congress created the CPSC in the Consumer Product Safety Act of 1972 (Pub. L. 92-573, Oct. 27, 1972), whose stated purposes include protecting "the public against unreasonable risks of injury associated with consumer products" (15 U.S.C. 2051(b)(1)). These are the Office of General Counsel's answers on how the Consumer Product Safety Act and its related statutes apply to specific products and situations. The set is a historical archive: our coverage page labels it "1973-2012, archive". That doesn't make it useless. Agency position history is exactly what you want when arguing that a long-standing interpretation should control, and it is exactly the kind of thing that quietly disappears from the open web.

CPSC Small Entity Compliance Guides, 34 documents. These are the plain-language explainers CPSC publishes alongside a rule so a small manufacturer can understand the obligation without reading the rule text cold. They are a natural first read on a CPSC rule.

The one nobody expects: SSA Rulings at 1,116

Social Security Administration Rulings are larger than any of the five sector regulators above, at 1,116 documents.

SSA's own FOIA rule says they are "binding on all components of SSA" (20 C.F.R. 402.160). They matter in disability and benefits cases.

That gap is the whole thesis of this post in one line. Document count and practitioner importance are barely correlated.

Citation forms vary more than people expect

Half the work in a guidance corpus is that no two agencies cite the same way. Real forms from the corpus:

A parser that only handles X U.S.C. Y and X C.F.R. Y recognizes none of the above, which is a whole problem of its own. That is why the corpus stores a stable actId per document and why hand-built ids usually 404: the id comes from a search or resolve response, never from a caller's guess.

How you actually query it

One search endpoint on the Vaquill AI corpus, scoped by corpus and source.

POST /api/v1/us/statutes/search
Authorization: Bearer vq_key_...
Content-Type: application/json

{
  "query": "no-action relief for commodity pool operator registration",
  "corpusType": "AGENCY_GUIDANCE",
  "source": "cftc_staff_letter",
  "matchType": "any",
  "limit": 20
}

Behaviors worth knowing before you build on it:

• Search costs 4 credits per call, and paging is cut from one ranking, so a later page costs no more than the first and results never repeat or go missing between pages.
• Unknown filter values return 422, not an empty result set. The source filter's error message lists every valid code, so a typo teaches you the vocabulary instead of looking like a coverage gap.
• A request rejected with a 422 is not charged.
• Results carry the official source URL for the agency's own copy wherever we hold one, so verification can end at the regulator rather than at us.
• corpusType accepts a single value or a list, so a guidance search can be widened to sit alongside the CFR in one ranked query when the question spans both.

Knowing when one of these changes

Guidance changes without ceremony. An agency posts a new letter, retires an old FAQ, or quietly restyles a page, and nothing tells you.

That is what GET /boards is for. It costs nothing, and each watchable source it returns arrives with a cadence and a lastRetrievedAt. You can create a watch, list the changes it captured, and pull a per-section diff for a specific change. Cadence is set per board, so read it from the response before deciding how often to expect a signal. The alerts documentation has the watch and diff mechanics.

What is deliberately out of scope

Two limits worth stating so nobody builds on an assumption.

Earlier text is a reconstruction. A document comes back at its current text by default. Pass asOf=YYYY-MM-DD to the section body endpoint and an earlier text is rebuilt from the change history we have recorded for it, with an asOf block that reports which version you got and whether the answer rests on when capture began (isBounded). Before capture began the answer can come back unavailable. Around that sit amendment history, a lastAmendedYear where the publisher credits one, yearFrom and yearTo currency filters, and diffs on watched boards. Verify a reconstructed text against the agency's own copy before you cite it.

Draft and case-specific material is excluded by design. DOE draft guidance is out, and FERC's docket-based case-specific orders are out. Both exclusions are scoping decisions, and the DOE one is stated on our agency guidance coverage page rather than discovered by a caller.

The design argument

A legal data corpus assembled by volume optimizes for the obvious sources. The US Code, the CFR, and the Federal Register are the natural starting points.

The differentiator sits in the tail. Eighty-two FERC policy statements and thirty-four CPSC compliance guides are small beside a general research product and close to essential to the specialists whose job depends on them. Building for the tail means accepting a per-source cost that never pays back on document count.

It pays back on whether a specialist can do their whole job in one place. That is the bet, and the counts above are the evidence for how far along it is.

FAQ

Is there an API for CFTC no-action letters?

Yes. CFTC staff letters are served under corpusType=AGENCY_GUIDANCE with source=cftc_staff_letter, covering 947 documents from 2008 to present across no-action, exemptive, and interpretative letters. A topic query is usually more useful than searching by letter number.

How do I search FCC declaratory rulings programmatically?

Filter a search on source=fcc_declaratory_ruling, which covers 174 rulings. Note that they are cited by FCC release number (DA- for a Bureau, FCC- for the full Commission), so a citation parser built only for U.S.C. and C.F.R. shapes won't recognize them. Take the stable actId off the search response rather than constructing one.

Do FERC policy statements include docket orders?

No. Policy statements are FERC's generally applicable interpretive vehicle, and the set here is 82 documents since 1996. The docket-based eLibrary universe of case-specific orders is a separate and much larger corpus that is deliberately out of scope.

Are the CPSC advisory opinions still being updated?

No. The 305 Office of General Counsel advisory opinions span 1973 to 2012 and are labelled an archive. They are useful as evidence of the agency's position over time, and they should not be treated as a statement of current CPSC views without checking the current rule text.

Why is DOE draft guidance excluded?

Because a draft is a proposal, and serving drafts next to final guidance with no distinction invites someone to cite something that never took effect. The 60 documents in doe_appliance_guidance are final guidance and FAQs. Drafts remain available on DOE's own site.

Which guidance source is bigger than the sector regulators covered here?

Social Security Administration Rulings, at 1,116 documents. They outnumber each of the sector regulators covered here, and they are not a source most people think of first.

How often does agency guidance refresh?

It depends on the source. The AGENCY_GUIDANCE corpus holds more than 96,000 documents across 53 named sources, and each watchable one reports its own cadence on the free GET /boards call, alongside lastRetrievedAt. Read the two together before you decide a quiet period means nothing changed.

Can I get the version of a guidance document as it read on a past date?

Partly. The section body endpoint takes asOf=YYYY-MM-DD. Each guidance document is held at one current text, so an earlier version is rebuilt from the change history we have recorded, and the asOf block says whether it was reconstructed or unavailable and whether isBounded applies. It is a reconstruction from recorded changes and makes no promise of a published archive. Alongside it sit amendment history, a lastAmendedYear where the publisher credits one, yearFrom and yearTo currency filters, and per-document diffs on watched boards.

How much does a guidance search cost?

A search call costs 4 credits, and paging is cut from a single ranking so a later page costs the same as the first. Failed calls aren't charged. Pricing details are in the credits and pricing explainer.

Priyansh Khodiyar

Co-Founder & CTO

Priyansh leads engineering and AI at Vaquill AI: the pipelines that pull statutes, regulations and court rules from every US jurisdiction's official publisher, and the REST API, MCP server and open dataset that serve them.