12

+1 for me also ! That’s would be a wonderful feature !

1 Like
13

One more:
+1 for the capability to call CustomGPT via API integration from a custom app.

1 Like
14

+1 from me as well. I was all excited to just hit my custom GPT with curl calls from a PHP widget, sigh very disappointed, I’m assuming this will be implemented soon ?

1 Like
15
  • on this, it would be great to be able to call my customGPT via API to my webapp.
2 Likes
16

+1 for the capability to call CustomGPT via API integration from a custom app.

1 Like
17

As @Foxabilo said, this is specifically what assistants are for? OpenAI likely won’t ever make the GPTs themselves interactable through the API, that defeats the whole purpose of the GPT store and the push for more Plus Subscribers.

Assistants are nearly identical, especially if you add in dalle-3 and code interpreter. Vision will likely come eventually, but at the moment it would be too compute-intensive to run on the scale of GPT-4 Turbo.

1 Like
18

You can transform your GPT to an assistant and use the assistant api.

19

Another way to ask this question could be, is there going to be feature parity to fine tune models via API the same way custom GPTs are trained?

20

This is needed. i spent hours and hours yesterday creating a custom GPT client through the interface, So happy with my results only to find out that i have no way of connecting my fastapi script to it. i can only share the web link… what is the point ? hours and hours wasted.

3 Likes
21

Same here bro, it’s frustrating to have to backtrack!

22

Big + 1 for this , we want to integrate our custom GPT into our application and use internally for data processing

23

+++++1 for this one!
GPT’s are useless for 3rd party apps, if they’re stuck on OpenAI UI.
Don’t you guys wanna make more $$$ with token and requests?

24

Hopefully in the future we can duplicate the GPT as an Assistant (assuming they use the same API, who knows, Assistants don’t even have GPT-4V or Dall-E yet)

But if you are expecting GPTs to be freely available for API, well, don’t hold your breath. You should’ve been building an Assistant and paying for the service.

Not at all. You can attract & introduce customers that are already Plus subscribers to your services using GPTs & Actions. Users can switch between commonly used GPTs for their daily routines instead of having 3 different apps.

It’s free for you to create and distribute a GPT (And you get revenue sharing) on the platform because it’s expected to stay IN the platform and attract plus subscribers to the GPT ecosystem.

1 Like
25

Im not sure you got my point.
If Im building bots, that can be beneficial for our company and employees, and I would like to white label them, GPTS are personalized and polished models that I’d love to use inside my company. But, how can I do that, If our employees has to use OpenAI’s GUI? GPTs stuck inside OpenAI platform, has no use for my use case that Im trying to build. I believe I can fine tune a model there and use it, but… Do you understand my point? Would be much easier to just been able to share the GPTs thru APIs, and of course, we’d pay for it as we already do to use tokens.

2 Likes
26

Assistants are GPTs thru API. You have to pay for the service.

27
  • for same requirement, I have created custom gpt using interface and its public. Now I want to access it through API. Mostly from Android / IOS apps. Please assume mobile developers while documenting the API reference docs.
1 Like
28

What’s up with the implication that we aren’t “paying for the service” when building a custom GPT?

Custom GPTs and the GPT store are not available to non-plus users.

1 Like
29

It’s not an implication, you’re also missing the point.

If you want your GPT to be used on your website you need to create an Assistant and pay for it (for other people to use it)

Of course you need to pay a plus membership to create & use GPTs, but that’s not what I was talking about.

1 Like
30

Hello, guys! You’ve created a wonderful service, and I sincerely thank you for it. However, it doesn’t work on my website and displays the error ‘Sorry, something went wrong. Please try again later.’ Meanwhile, the ChatGPT connection through the API, which I set up myself, works fine. Your test code for your Assistant also works. What could be the problem? Care Chat

31

This seems to be weirdly difficult for some users to understand, I guess that’s to be expected when you release something like GPTs. It lowers the barrier to access drastically.

1 Like