Skip to main content
The PRIXO AI assistant answers food delivery questions in Arabic and English using live price data from the community database. You send a conversation history and receive a streaming response over Server-Sent Events — the assistant may invoke tools mid-stream to fetch prices, locate branches, or recall your saved preferences before it replies.

Endpoint

Authentication

Required. You must be signed in with a valid session cookie. Calls without a session receive a 401 response. See the Authentication guide for how to obtain a session.

Rate limit

30 requests per minute per authenticated user. Exceeding this limit returns a 429 response.
When you exceed the rate limit, the endpoint immediately returns HTTP 429 with the body {"error": "rate_limit_exceeded"}. Your client should back off and retry after at least 60 seconds.

Request

Set Content-Type: application/json and send a JSON body containing the full conversation history.

Body parameters

array
required
The conversation history as an array of message objects. Each message must have a role and content field.

Example request

Response

The response is a Server-Sent Events (SSE) stream with Content-Type: text/event-stream. The stream delivers the assistant’s reply in incremental text chunks, interleaved with tool call events when the assistant needs to look up live data. The stream closes automatically when the assistant finishes its response.

Stream events

The assistant emits several types of events during a response:

Tool names

The assistant has access to these tools. Tool call events in the stream identify which tool is running:
Use a streaming-capable client to consume this endpoint. Any SSE-capable HTTP client or EventSource implementation can consume the stream. The stream closes automatically when the assistant finishes its response.

Example stream output

The following shows an abbreviated stream for a price query. Each line beginning with data: is one SSE event.

Error responses

For multi-turn conversations, include the full conversation history in every request — not just the latest message. The assistant uses earlier turns to provide context-aware answers, especially when recalling saved preferences.