Prediction Market Bots Get a CFTC Pass: What Is Allowed
Tools

Prediction Market Bots Get a CFTC Pass: What Is Allowed

· EdgeOutcome Team· prediction-markets, kalshi, cftc
Last updated

Two documents landed 24 hours apart last week, and they point in opposite directions. On September 17, 2026, the CFTC’s Market Participants Division issued Letter 26-25, a no-action position that lets the makers of “passive software” put a trading front end in front of US event-contract customers without registering as an introducing broker. On September 18, Missouri’s Attorney General sent cease-and-desist letters to six prediction market operators, Kalshi and Polymarket among them, ordering them to stop offering sports event contracts to Missouri residents 4.

So does a prediction market bot need a federal license now? The short answer is no, as long as your software never picks a side. Everything that follows is the definition of “picks a side.”

Key Takeaway: Letter 26-25 gives passive software providers a broad no-action position against introducing broker (IB) and associated person (AP) registration under Sections 4d(g) and 4k(1) of the Commodity Exchange Act. It covers front-end interfaces, market data, order submission to a registered venue, and even revenue sharing. It does not cover custody of user funds, express buy or sell signals, or any discretion over order routing and execution. It is a staff position, not a rule, and it holds until the Commission replaces it.

What CFTC Letter 26-25 Actually Changes

The Commission has tolerated trading front ends for two decades. The old technology service vendor letters, 06-29, 08-07, and 08-12, let vendors off the registration hook only if their customers already had an independent relationship with a futures commission merchant, if the platform produced no buy or sell signals, and if the vendor never recommended a particular broker.

Those guardrails made the letters nearly unusable for a modern consumer app.

The first crack came on March 17, 2026, when the Division issued Letter 26-09 to Phantom Technologies, Inc. Under Regulation 140.99(a)(2) only the named beneficiary can rely on a no-action letter, so Phantom’s relief was Phantom’s alone. Following that letter, the Division received inquiries from other similarly situated providers 1.

Letter 26-25 is the answer to those inquiries. It extends the same position to all providers of passive software, and it is explicit about one thing the press coverage got wrong: “For the avoidance of doubt, PSPs are not limited to providers of crypto asset related software” 1.

The relief is real but temporary and non-binding. It runs “until the effective date of a Commission rulemaking or guidance addressing the application of the IB registration requirement to software developers,” and the Division reserves the right to modify, suspend, or terminate it at discretion 1. Read it as a window, not a wall.

The Permission: What Counts as Covered Activity

The letter lists the activities a Passive Software Provider, or PSP, may perform. All of them are functional, not promotional.

Covered ActivityWhy it matters to a builder
Develop and distribute front-end interface softwareUsers review market data, aggregate position info, browse product offerings, and submit orders directly to a registrant
Route orders from the user’s deviceThe PSP’s software enables the user to transmit orders straight to the venue. The PSP has no affirmative involvement with any particular order
Revenue sharing with the venueA designated contract market, FCM, or IB may share a portion of relevant revenue for software distribution
Transaction-based fees charged to usersYou may charge users directly through your terms of use
Market your software and your venue relationshipsIncluding promoting the availability of particular derivatives contracts, such as event contracts and perpetual contracts
Introduce and solicit users toward specific registrantsProvided users face no contractual or operational restriction on reaching those venues directly

That last row is the part that would have failed under the old vendor letters, which required a pre-existing broker relationship. The letter closes that gap.

The Three Hard Limits

Here is where the line sits, in the Division’s own words. At no point may a covered PSP:

  1. Hold, control, or take custody of user assets. Positions are custodied at the clearing organization or an FCM member. The letter describes this as a “custodial” model consistent with exchange-traded derivatives.
  2. Generate express “buy” or “sell” signals.
  3. Exercise discretion with respect to the routing or execution of user orders.

If your software does any of those three things, Letter 26-25 does not describe you. A signal service that tells subscribers when to buy a market, or an automated strategy that picks the contract and fires the order, sits outside the Covered Activities.

That distinction cuts through most of what passes for a Kalshi tool in 2026. Our Kalshi trading bots comparison separates notification tools from execution tools; the CFTC has now drawn roughly the same line, from the other direction.

Expert insight: The CFTC did not legalize trading bots. It legalized dashboards with a checkout button. The moment your software decides which contract to trade, or at what price, you are back in registration territory, and no amount of “the user clicked confirm” changes that.

The 10 Conditions You Have to File

Relief is conditional, and the conditions are administrative rather than exotic. You file documents with the Division at [email protected] referencing the letter.

#Condition
1The PSP, its principals, and anyone soliciting users are not subject to statutory disqualification
2Users receive and acknowledge disclosures on the PSP’s relationship with each registrant, including fees and conflicts of interest
3Users receive and acknowledge a risk disclosure under Reg 1.55(b), with a retained record of the acknowledgement
4Users are onboarded as direct members or customers and keep independent access to the registrant
5Policies and procedures for public communications and marketing that meet Commission and NFA rules as if the PSP were a registered IB
6No advertising or promotions that would require NFA pre-approval under Compliance Rule 2-29
7A written joint and several liability undertaking with each registrant, filed with the Division, plus consent to CFTC jurisdiction
8Records of compliance and regulated business kept per Reg 1.31
9Notice to the Division on insolvency or bankruptcy
10A filed notice agreeing to the conditions and consenting to CFTC jurisdiction, including a sovereign immunity waiver where applicable

Condition 7 is the expensive one. Joint and several liability means your venue relationship is no longer a commercial contract, it is a shared exposure. If your software violates the Act while acting for a registrant, the registrant is on the hook with you.

The Other Half: Missouri Names Six Operators

While the federal door opened for software, a state door closed for platforms. Missouri Attorney General Catherine Hanaway issued cease-and-desist letters to Polymarket, Kalshi, Crypto.com, Novig, Underdog, and Robinhood, finding that offering sports event contracts to Missourians is unlicensed sports wagering under state law 4.

Missourians approved Amendment 2 in 2024, placing sports betting oversight with the Missouri Gaming Commission, with a 10% tax on gross receipts and licensing requirements for mobile operators. The market launched December 1, 2025. The letter’s language is blunt: “Failure to comply will result in enforcement action by the State of Missouri,” and it accuses five of the six operators of permitting underage access or lacking adequate safeguards to prevent under-21 participation 4.

The substantive disagreement is preemption, and Missouri’s letter states a position rather than argues one. Our explainer on the prediction market crackdown covers the New York action and the CFTC’s emergency counter-order, and the Ninth Circuit ruling covers the tribal gaming argument that leaned the same way.

For anyone running software, the practical shape of 2026 is now clear: federal rules govern how you build, state rules govern who you can serve.

Enforcement Is the Third Rail

The same letter that protects passive software describes what happens to people who trade on information they should not have.

On August 28, 2026, the CFTC ordered Gabriel Perez, a White House teleprompter operator, to disgorge $107,539.02 and pay a $65,000 penalty, a total of $172,000, for trading presidential mention market contracts between December 2025 and February 2026 using advance knowledge of speeches. He received a three-year trading ban and a cooperation discount, and the CFTC credited KalshiEX for assistance 5.

That followed the July 31 order against former Congressman George Santos: $17,569.98 in disgorgement, a $17,500 penalty, and a three-year ban for trading the “Who will attend the State of the Union?” contract in February 2026 while posting materially misleading statements about his own plans 6. Kalshi went further and announced a lifetime ban against him in September.

The pattern matters for thin markets. Both cases involved contracts where one participant could move the price with a public statement, which is also the profile of the low-liquidity mention and district markets where automated flow is easiest to misread. Our work on how informed flow shows up in order data is the defensive read on the same signal.

What Prediction Market Bots Should Change This Week

Four steps, in order.

  1. Classify your software honestly. Passive front end, or signal generator, or discretionary executor. Write the answer down, because that sentence is your registration analysis.
  2. If you claim the no-action position, build the paper trail. Disclosures acknowledged, records retained, marketing policies written, undertakings filed. None of that can be done retroactively.
  3. Stop marketing signals as a passive tool. The letter removes signal generation from the safe harbor by name. Kalshi API documentation gaps are a technical annoyance; a signal marketed as automated advice is a regulatory one.
  4. Track state availability as an input, not an afterthought. If Missouri’s order holds, your user base in that state changes. A bot on infrastructure you run 24/7, like our Hermes cronjob setup, should log which venue it reached and when access changed.

The Bottom Line

Federal staff just made it easier to build a prediction market interface and harder to pretend that an automated strategy is one. The pass is broad, conditional, temporary, and revocable. The three hard limits are not.

If you want to see live order books rather than secondhand commentary, Kalshi’s sign-up is the fastest route to market access.

EdgeOutcome may earn a commission if you open an account through links on this page — including Kalshi or Polymarket. Nothing here is legal or investment advice, and we are not your counsel. Staff no-action letters bind only the issuing division, can be withdrawn, and turn on the specific facts presented. Consult a derivatives attorney before building or marketing software that touches regulated event contracts.

EdgeOutcome
EdgeOutcome Team

Data-driven prediction market analysis. EdgeOutcome helps traders find real edges on Kalshi and Polymarket — not hype, just numbers. More about us →