How AI agents monitor CFTC actions and derivatives rules
An agent monitors the CFTC by calling a wire that reads the Commission's press release feed at runtime. It returns rulemakings, advisories, no-action positions, enforcement orders and market actions with dates and links. Most of what it carries is regulatory rather than enforcement.
/mcp. Nothing here needs an API key or a signup.
That last sentence is the expectation most integrations get wrong, so it is worth settling first.
This is a rulemaking feed that also carries enforcement
Agents built for compliance monitoring tend to treat every financial regulator as an enforcement blotter. The CFTC feed does not behave that way. A live read of it returns proposed rulemakings on affiliations among regulated entities, a comment-period extension on 24/7 futures trading, an advisory on self-certification of event contract series, a staff no-action position, an emergency order directing fulfilment of pending trades, and advisory committee scheduling.
Enforcement is in there, and when it lands it is specific: a firm ordered to pay $8 million over anti-money-laundering supervision failures, an individual ordered to pay $35,000 for manipulative trading, whistleblower awards totalling over $8 million. But it arrives alongside a steady stream of market-structure work, and an agent that filters for "fine" or "penalty" will miss the rule change that actually affects its user.
The practical split:
| If the question is | Filter on | Expect |
|---|---|---|
| Did a firm get penalised? | Entity name, q | Occasional, high value |
| Is a rule changing? | rulemaking, comment, no-action | The bulk of the feed |
| What is the CFTC doing about a product? | The product name | Advisories and orders |
The SEC boundary is about the instrument, not the firm
This is the distinction that produces wrong routing. The CFTC regulates derivatives: futures, options, swaps and event contracts. The SEC regulates securities. The same firm can be supervised by both for different parts of its business, so "which regulator covers this company" is usually the wrong question. The right one is which instrument the conduct involved.
Event contracts and prediction markets are a live example. They sit on the CFTC side, and the feed carries advisories and emergency orders about them that would never appear on a securities wire. Securities enforcement, and the FTC's consumer-protection work, are covered separately in how agents monitor SEC and FTC enforcement actions. Formal rule text, once a rule is published rather than announced, lands in the Federal Register and is covered in how agents track new US federal regulations.
The volume is genuinely low, and the default window hides it
A measurement worth stating plainly, because it changes how you should query: polling this wire's source today returned 4 items across the full 14 day retention window. That is the real publishing rate, not a fault.
Two consequences follow:
- An empty result is the normal case, not a signal. On a wire this sparse, a
narrow since returns nothing most days. Widen to the full window before concluding anything happened or did not.
- A keyword query can easily return zero from a corpus of four. Search is
ranked keyword matching, and a multi-token query has to match most of its tokens. Against four documents, that is a high bar. Query broadly here and filter after, which is the opposite of the advice for a high-volume wire like DOJ.
# discovery only, no items: browse every wire, its filters and its price claude mcp add --transport http botwire https://thebotwire.com/mcp # paid, $0.01: everything the CFTC published in the full window curl -i "https://thebotwire.com/cftc/latest?since=14d&limit=50" # a named entity or product, still across the full window curl -i "https://thebotwire.com/cftc/latest?q=event+contracts&since=14d"
Parameters are q, since and limit (1 to 50). There is one publisher behind this wire, so the src filter takes a single value and does no useful work. The route is $0.01 per call in USDC on Base, with no API key, no signup and no subscription. Every route and price is machine-readable at /llms-full.txt.
FAQ
Does this wire carry CFTC enforcement actions in full?
It carries what the Commission publishes to its press release feed, which includes enforcement announcements. It is not a docket. Orders, complaints and administrative filings that generate no press release will not appear, and an agent asked whether a firm has been sanctioned should answer with what it searched rather than implying it checked the record.
Why does this wire cost $0.01 when most cost half that?
The documents are longer and the parsing is heavier, which is the same reason the court, filings and enforcement wires sit at the higher price. The price is stated in the 402 response before any payment happens, so an agent working to a budget can decline before spending.
Can an agent tell a proposed rule from a final one?
Only from the announcement text, so it should quote rather than paraphrase. A proposed rulemaking, a comment period extension and a final rule are three different states with three different consequences, and collapsing them into "the CFTC changed the rules" is the most common way this feed gets misreported.
How fresh is the CFTC wire?
It sits in the sparse ingest tier and is polled at most every 15 minutes, which is far inside the rhythm of a source publishing a handful of items a fortnight. On this route the publishing schedule binds, never the poll interval. The observed ingest interval and last poll timestamp are published live at /health.
Sources
CFTC press releases, including the $8 million anti-money-laundering supervision order cited above and the separation of General from Enforcement releases, are published at cftc.gov press releases, and the feed this wire reads is the Commission's own press release RSS. Poll cadence and per-call pricing for this service are published live at thebotwire.com/health.
Related: How do AI agents monitor SEC and FTC enforcement actions? · How do AI agents track new US federal regulations?