GPT: Simple endpoint that retrieve data in a action hallucinates

Here is the thing: I have a simple endpoint that returns data of a user base of an Id as the parameter, I tested this in postman and the data is deliver right.

I checked the schema and everything seems correct, the GPT is fetching the data the endpoint right but when the GPT answers the data is completely wrong is a big hallucination problem.

How can we avoid this problem? Could this be the prompt that I’m writing or how the schema is set? Because I’m out of ideas here :smile: any tips ?

What does the debug info say? Are you seeing the endpoint called with all the params you think it should be sending? What response debug data are you getting?

You will probably have to show just that part of the schema that you think is correct. It’s hard to help with not much info.

1 Like

Hi mojave and thanks for the reply

The GPT action successfully connect to the external endpoint, I checked the debug and I get a response 200.

What I don’t get is why the GPT is returning funny data :smile:

Take a look of the schema

{
“openapi”: “3.0.1”,
“info”: {
“title”: “Resource Request using an ID”,
“version”: “1.0.0”
},
“servers”: [
{
“url”: “https://mydomainblahblahblah.com
}
],
“paths”: {
“/api/json/reply/”: {
“get”: {
“summary”: “Get Information from using an id parameter”,
“operationId”: “resourcerequest”,
“parameters”: [
{
“name”: “id”,
“in”: “query”,
“required”: true,
“schema”: {
“type”: “string”
}
}
],
“responses”: {
“200”: {
“description”: “Successful response with the resourcerequest”,
“content”: {
“application/json”: {
“schema”: {
“type”: “object”,
“properties”: {
“Name”: {
“type”: “string”
},
“Id”: {
“type”: “integer”
},
“UserLogin”: {
“type”: “string”
}
}
}
}
}
},
“400”: {
“description”: “The user does not exist, or you do not have access to it.”
}
}
}
}
}
}

1 Like