#Chat Completion API Plugin Support
21 messages · Page 1 of 1 (latest)
There is authentication support for that. Plugin developers might want to make their plugins available through their own API integrations too.
the plugins seem be in a plugin store and some behind the plus subscription, there is no auth system nor payment logic for api to use plugins
devs can already implement most of the same stuff with api
Well, since there is no API support for plugins at all (no way to allow plugins to be used), of course there isn't. But since plugins support token auth, their use could be restricted to pre-authenticated API requests.
the plugin auth stuff is more related to plugin types, eg is it generic one or one that will have user specific stuff
Are you referring to API fine-tuning? Because they don't seem the same to me.
no i mean the new plugins api
eg. weather does not need oauth, while todo list might
Exactly. Hence the chat API integration could specify which plugin auth token to use depending on their end-users, presented in their own interface.
I thought you meant that API devs can already do everything plugin devs can do.
not with the current design that assumes everything works over openai web interface, also all existing api interfaces are incompatible and there are no references that such would come later
api devs can use langchain, bing/google api etc.
and also have oauth stuff to any service they want, the openai plugins just do the same in their ui
If there is a web UI, then there is an underlying API. What I'm asking is if anyone knows of any plan to make that API part of the public chat completion API. Of course API devs can replicate the plugin functionality on their own infrastructure, but that would be a missed opportunity for OpenAI, IMHO... And a loss for devs that just want the plugin functionality without having to build it themselves.