1

I created a custom GPT and an assistant using the Assistant API some a q and a bot for a company. Both have the same instructions and access to the same exact set of documents. Same exact model also. However, it appears that the custom GPT consistently delivers more reliable and comprehensive results compared to the Assistant API. What could be the reason for this discrepancy?

4 Likes
2

interesting - do you know if custom GPTs have infinite thread context, like the assistant api?

3

i don’t think it has to do with thread context. assistant api doesn’t seem to be thorough in searching the documents that i’ve uploaded…at least that’s what i noticed

4

im guessing that you have the web capability turned on for the gpt vs the inability for the assistant to access real time data from the web whereby giving it access to far more comprehensive responses

5

OT, but is it possible that if I create an assistant via the API it does not show in ‘My GPTS’ ?

6

I have some difficulty understanding the purpose and goal of creating the Assistant API. Am I correct in understanding that essentially it is a tool similar to GPTs, with the ability to train a specific model on one’s own data and integrate it into one’s web application outside the openai platform?

1 Like
7

As far as I understand, you’re right. GPTs are used as a part of “ChatGPT ecosystem”, and Assistant API is a tool for using OpenAIs models outside of that ecosystem, for example a chatbot on your own website.

1 Like
8

I encountered the same problem. It seems the implementation is different between GPTs and assistant. Benzri, have you made any progress on this issue?

9

I have noticed the exact same thing, I guess there is a reason the assistant API is in Beta. Using same set of docs and instructions, the “My GPT” version comes up with much better results than Assistant API. Even when tweaking the instructions to be even more specific, assistant seems to miss the mark most of the time.

Hopefully, it will make progress, otherwise what could have been one of the API function, would turn out to be the least useful in real life :frowning:

10

Can you create a function to use the api to call on the Gpt to run the query?

1 Like
11

Hi and welcome to the Developer Forum!

You cannot call a GPT.
You can call an Assistant.
GPTs can call assistants if properly configured.
Assistants cannot call GPTs.

1 Like
12

Exactly my thoughts as well. Whats the point when we already have Custom GPTs?

13

Not needing to produce a product solely for the benefit of driving ChatGPT Plus subscriptions to OpenAI’s own site in order to use your custom AI function?

14

Same for me. The custom GPT I built as a help assistant vastly outperforms the Assistants API with the exact same settings and documents. Web browsing not a variable because vast majority of our site is behind a login. The gap is significant: the Assistants API is generating incorrect information about 20% of the time, where the GPT is consistently solid. Until OAI closes the gap, I don’t think the Assistants API is ready for prime time. (The API would enable us to integrate help functionality in our site, which is what most businesses need.)

15

I think Assistant feature will dissapear. Or merged somehow to ChatGPTs feature, allowing ChatGPTs to be called from an API.

They are mostly the same and a they are a little confusing. This is a whole new product, a lot of things will change, quickly.