Huge difference between ChatGPT assistant and API assistant

I have used ChatGPT for prototyping an assistant that can take a user natural language prompt and translate it into URL filters.
It works very nicely as a GPT in the Chat interface, but setting it up in Playground, with identical instructions and same document to retrieve information about URL parameters, produces responses that are wrong and vastly slower than the mockup in ChatGPT.

In playground, it does not seem to check the document for instructions and just makes guesses about the URL structure.

Are there any key differences between assistants in chat and assistants in playground, that should be taken into account, when setting them up?
Or are GPU resources just throttled for API assistants atm?

1 Like