ChatGPT Apps SDK Monetization: Digital Goods Still Off-Limits

What happened

OpenAI has opened ChatGPT to third-party app submissions. Developers building with its Apps SDK, however, are finding that the payment options described in developer sessions don't line up with what they can actually ship. The friction is clearest for anyone hoping to sell digital products or services.

The confusion comes from an OpenAI developer session. A company representative, identified by attendees as Corey, described several ways to monetize a ChatGPT app 1. One was an authentication flow: after a user installs and connects an app, the developer can require a login to their own platform and handle sign-ups and payments there 1. Another was a more native-feeling checkout button that opens an external link, ideally deep-linking to a final checkout step 1. OpenAI supplies a redirect URL so the user can be sent back into ChatGPT to continue 1. The representative also said OpenAI's agentic commerce protocol and Instant Checkout are being opened to more apps and builders 1.

A developer replying in the same OpenAI community thread gave a blunter answer. Currently, apps that monetize any digital products or services cannot be submitted, the developer wrote, and pointed to OpenAI's documentation as the basis 3. That developer guessed OpenAI wants a revenue share on usage or subscriptions and hasn't yet built the machinery to collect it 3.

Why the gap matters

The mismatch matters because of how OpenAI has framed the platform. VentureBeat's coverage of DevDay 2025 described the Apps SDK, together with Agent Kit, as turning ChatGPT from a chatbot into a platform, even "the new app store" 4. Weeks earlier, OpenAI had added support for the Model Context Protocol (MCP) in ChatGPT's developer mode. VentureBeat called that feature powerful but dangerous, because it lets developers connect external servers directly 4.

App stores live or die on whether developers can earn money in them. The external-checkout path OpenAI described is workable in principle 1. But if the submission rules exclude digital goods 3, the developers most suited to a conversational interface are boxed in: software tools, content services, and subscription products. Selling physical goods or routing users to existing accounts appears to fit the current rules better than selling something consumed inside the chat itself.

The two accounts don't strictly contradict each other. The session described mechanisms that exist or are planned 1, while the forum reply describes what review will accept today 3. The practical reading is that the plumbing for monetization is being built faster than the policy allowing developers to use it for digital goods.

The platform-cut question

The forum developer's theory, that OpenAI is holding back until it can take a percentage 3, is speculation. It is plausible speculation, though, and it echoes the history of mobile app stores, where platform owners fought hard over in-app payments for digital goods. The phrasing in the developer session supports a reading that OpenAI wants a native commerce layer of its own. That layer is the agentic commerce protocol and Instant Checkout it says it is expanding 1. A native rail would give OpenAI a natural point at which to collect fees, much as Apple and Google do.

As analysis rather than established fact, a likely trajectory is this: digital-goods sales stay restricted or confined to external flows until OpenAI's in-chat checkout is broadly available, then become allowed on terms that favor the native option.

The bigger argument about apps inside AI

The Hacker News discussion of the submission launch moved past payment mechanics into a more basic question about who owns the user 2. One commenter argued that model providers will eventually just sell "enterprise-grade intelligence" as a utility, much as power companies sell electricity, and are building apps now only to drive adoption 2. Another countered that capable AI doesn't stay in a pipe. It absorbs apps, reducing them to background tool calls 2. A further reply noted that the interface sitting between a user and the outcome they want is also the ideal marketing channel 2. That observation helps explain why OpenAI would want to control both the interface and the checkout.

Another thread compared how competitors handle costs. One commenter found that Google's AI Studio may let apps run without the developer paying inference costs, but only inside AI Studio. Outside it, the developer is back to footing the bill through an API key 2. That detail shows why monetization matters so much: someone pays for every model call, and developers need a reliable way to recover those costs.

The bottom line

OpenAI has the distribution and has shipped the developer tools 4. It has also signaled that commerce features are coming 1. Until submission rules clearly permit selling digital goods, though, ChatGPT functions less like an app store and more like a storefront window. Developers can showcase their products there, but closing the sale mostly happens somewhere else.