Not publicly available.This describes the Loupestack API before launch. Endpoints, limits and fields can still change.
Errors
Every endpoint under /v1/ answers errors in one shape:
{ "error": { "code": "query_not_allowed", "message": "table function not allowed: read_csv", "details": [] } }
code is stable and meant for programs. Branch on it, not on the status or the message.
message is for people and can change.
details is there only for some codes; for invalid_request it lists each problem with its path.
The login endpoints under /api/auth/ use Better Auth’s own shape, { "code", "message" }
(Authentication).
This page is the list of codes. A test in the API fails when the API can answer with a code that is not on it.
Order. Who you are and what you may do are checked first, before the request body is read: whatever the
body, a caller without a session gets 401 unauthenticated, someone without a workspace 403 no_workspace, and a
member calling an owner/admin operation 403 admin_required. Only a caller who may call the operation gets
422 invalid_request for a body that does not match its schema.
A stream that has started reports a failure as an error event:
event: error
data: {"code":"no_answer","message":"I could not write a query that works for this question. Try rephrasing it or naming the table.","conversationId":"3d4e5f60-7182-4930-9c4d-5e6f7a8b9cad"}
Code
Stream
Meaning
no_answer
ask, chat
No working SQL after two repairs. Rephrase the question
no_ui
UI, chat
No usable UI after two repairs. Rephrase the prompt
ask_timeout
ask, chat
The question took longer than 60 seconds
ui_timeout
UI, chat
The generation took longer than 10 minutes
llm_timeout
all
The language model did not answer in time
llm_unavailable
all
The language model is not available
llm_bad_output
all
The language model’s answer was unusable
query_timeout
ask, chat
A query took longer than its time limit
too_many_queries
ask, chat
Too many queries running in the workspace
engine_busy
ask, chat
All query engines are in use
shutting_down
all
The server is restarting. Ask again
internal_error
all
Something went wrong on our side
A UI stream can also end with one of the codes from the tables above, for example tenant_not_provisioned.
A query that the model wrote and that was refused or failed is not an error by itself: the model gets the
reason and repairs its SQL, up to two times, before no_answer or no_ui.