@Sim2K will the paywall be for GPTs in the GPT Store? Or accessed on a credz site?
Re: openAI response - I’d also prefer not to work on something if it’s about to be imminently rolled out lol but GPT Wallets was super easy for us to switch on cos we already had a lot of the payments infrastructure set up from our previous startup so we figured why not, seemed like we could be useful in the interim while revenue share is still being set up.
But also potentially after revenue share is rolled out. Afterall, youtube does ad revenue share with creators, who then also find all kinds of other supplementary income streams like patreon / affiliate links / sponsorships… and ultimately youtube creators making money benefits youtube cos it keeps them within the youtube ecosystem.
but yeah, that’s all speculation at my end, would love to hear how the good folks at OpenAI are thinking about it!
@jeevika the GPT Credz paywall is available for all the GPTs on the GPT Store. All GPT owners will be able to use it. Hoping to get some testers this week. Did you check my demo? Credz is the currency. The aim is for GPT owners to cashout Credz paid for their GPT service for real currency.
The setup allows a GPT owner to be good to go in under 1min. They register, next it’s one click to connect their GPT, copy n paste the YAML schema and a prompt, and your good to go.
I’m currently finishing off the functionality that allows people to test GPTs for a set amount of times (set dynamically by the GPT owner) before paying for the GPT access. This is important so users can see if the GPT is for them without paying. A try before you buy option. With so many GPT’s, you need this functionality as users might not use a GPT when others are free even though the paid one might be better. If they can test 1st and see why the premium one is better, they most likely to pay the next time.
I wanted to share that I have finally solved this problem with Oauth and Stripe for creating a paywall for a GPT.
Using auth0, I turned on a new custom solution where unless a user has a premium subscription, they are simply redirected to a signup page.
In other words, if a user doesn’t have a premium role assigned already (as the result of a paid subscription via Stripe), our system automatically assigns them a free user role via Auth0, if they try to use the premium GPT.
In case it helps anyone, Auth0, and Stripe have APIs and webhooks, which combined with an email client webhook can automate the whole process.
From a high level, the customer journey is: Stripe -->Auth0–>Role_Assigned–>Login_GPT_OAuth–>ChatGPT_Response–>Login_SaaS_App–>–>Return_back_to GPT on ChatGPT–>Repeat).