I have since resolved this making the GPT public can simply use OAuth protocol to authenticate premium users from my server.
No, this is wanting OpenAI to pay for the tokens used and for the creator to take a $ amount from that. That is what happened with Plugins and I suspect will attempt to be done again with GPTs.
This is why GPTs were proposed as having a revenue share for the top ones, i.e. there is not meant to be any monetisation within the GPT its self, that will not stop people trying though.
Thanks for chiming in! That’s an interesting point, though I wouldn’t mind paying for the token usage and since this GPT calls one of my plugins there would be usage costs there that could be offset by monetisation of GPTs. I look forward to what - if anything - OpenAI releases to help plugin/GPT developers monetize their products which could help fuel their development and offset operational costs, etc…
Thanks for sharing, as I hadn’t heard of OpenAI’s Assistants API and just checking it out!
While I don’t immediately see how Assistants could solve the issue I raised, I am not entirely sure either (looking into how they work more closely here) and would welcome any suggestions related to the paywall/protection of GPT URLs
I see how this is like making OpenAI pay for tokens, and please correct me if I am wrong, but wouldn’t anyone who accesses a GPT, such as with a private link, still need to pay for ChatGPT Plus?
I was referring to charging users in addition to what they pay for Chat GPT Plus subscriptions, such as for a premium version, compared to a free one that you get just from being a ChatGPT Plus subscriber.
Will your solution work for paywalling my GPT on a Squarespace site?
I think there are solutions that OpenAI has published, such as the documents for adding authentication, including service level authorization or using OAuth, which can provide an effective means of authenticating/authorizing users. The challenge is mapping the application flow to comply with OAuth and passing back/forth valid state parameters which can be tricky, especially with lots of moving pieces if your plugin is using 3rd party APIs or redirecting to other URLs outside of ChatGPT.
No reason it shouldn’t since you can embed in on any site and the embedding will have your paywall if you have one.
lol this is crazy because I’ve been coming at using an iframe so many different ways but think I might break down and use this. I’m using Squarespace + memberspace to paywall my GPT. It’s ready, just needs this last step.
I signed up for agenthost.ai for my paywalled GPT. Unfortunately, there is one “chat history” for all users. So anyone who logs in can see the entirety of every conversation that preceded that login.
Really hoping OpenAI decides to allow custom GPTs to be embedded on private websites and paywalled… essentially turning us into resellers. If I’m going to improve and maintain my own GPT, much less advertise it, I think I should be able to determine my own pricing/compensation. As long as I’m covering my token usage, does it matter?
Hey @Robabob thats not true based on my experience. Once you start a chat on agenthost, it saves the thread on your local browser. Other people can’t see what you see. You can verify that by opening the same agent in incognito mode or on another browser and seeing that the chat history is not showing up
Ahhhhh thanks so much!! So even though I’m logged in to two different accounts, because the browser is the same it’s being recognized as the same session. Thanks!!
You have a few options to monetize your custom GPTs by placing them behind a paywall.
You can use the Assistants API (still in Beta, so not quite ready for production) or the Chat API by OpenAI. You will need to know how to code or hire a developer to build the required components for you. This will involve, at a bare minimum, rolling your own backend server and frontend chat component. You would then be able to host your premium onto your website behind a paywall.
I’m the founder of Lingo Blocks, a no-code platform for building custom GPTs and hosting them onto your website. You can define an AI agent’s instructions, add custom knowledge, and embed it onto your website behind a paywall. What you’re wanting to accomplish is a common use case for my platform and is definitely achievable. My suggestion is to try a variety of solutions, then see which ones work best for you.
I ended up integrating OAuth into my premium version which is public on the GPT store, whereas the free version - which is also public - is unauthenticated and connected to a different server. Interested to hear more stories on how users are approaching this, including using 3rd party services.
Something like this seems to be the best way to earn with custom AI experiences. Custom GPT’s are limited in what you can do without hosting your own server to provide “actions”. If you already have a bunch of user’s on your platform and make a custom GPT that interacts with that platform, I suppose it could be profitable. But I don’t see a way to chain AI agents while using the user’s API key along the way, unless OpenAI provides a way for their users to authenticate as one of your users.
I’m looking for something similar where I can bring my own OpenAI keys and Assistant Ids, so a service that host backend and let me embed the chat interface on another website.
I was facing same issues.
I’m now using a Wordpress plugin (Chatbot Chat GPT), allowed you to embed or create a floating window with your GPT assistant.
My point now is just about creating the paywall with plugins
I think I’m following, but please correct me if I miss the mark of what you’re saying. Depending on what you’re building, you might need to deploy your own server to host the business logic of your agent’s Actions. That’s a fair point, and if that’s the case, you can select that action with upcoming Actions release on the platform.
There’s plenty of cases where it’d be advantageous to create both a GPT for ChatGPT to benefit from the free distribution and discovery. Depending on your use case, it’d also be beneficial to release your own custom agent and host it on your own website. Maybe that’s behind a paywall and you monetize it with subscriptions, or maybe it’s freely available as a service of your brand.