Authorizations
Headers
The dataset id or tracking_id to use for the request. We assume you intend to use an id if the value is a valid uuid.
Body
JSON request payload to delete an agent message then regenerate it in a strem
The id of the topic to regenerate the last message for.
If concat user messages query is set to true, all of the user messages in the topic will be concatenated together and used as the search query. If not specified, this defaults to false. Default is false.
Context options to use for the completion. If not specified, all options will default to false.
The currency symbol to use for the completion. If not specified, this defaults to "$".
ChunkFilter is a JSON object which can be used to filter chunks. This is useful for when you want to filter chunks by arbitrary metadata. Unlike with tag filtering, there is a performance hit for filtering on metadata.
{
"must": [
{
"field": "tag_set",
"match_all": ["A", "B"]
},
{
"field": "num_value",
"range": { "gte": 10, "lte": 25 }
}
]
}
Highlight Options lets you specify different methods to highlight the chunks in the result set. If not specified, this defaults to the score of the chunks.
LLM options to use for the completion. If not specified, this defaults to the dataset's LLM options.
Metadata is any metadata you want to associate w/ the event that is created from this request
Model name to use for the completion. If not specified, this defaults to the dataset's model.
No result message for when there are no chunks found above the score threshold.
Number of messages to include in the context window. If not specified, this defaults to 10.
x >= 0
Only include docs used is a boolean that indicates whether or not to only include the docs that were used in the completion. If true, the completion will only include the docs that were used in the completion. If false, the completion will include all of the docs.
Page size is the number of chunks to fetch during RAG. If 0, then no search will be performed. If specified, this will override the N retrievals to include in the dataset configuration. Default is None.
x >= 0
Overrides what the way chunks are placed into the context window
If true, stop words (specified in server/src/stop-words.txt in the git repo) will be removed. Queries that are entirely stop words will be preserved.
Set score_threshold to a float to filter out chunks with a score below the threshold. This threshold applies before weight and bias modifications. If not specified, this defaults to 0.0.
Query is the search query. This can be any string. The search_query will be used to create a dense embedding vector and/or sparse vector which will be used to find the result set. If not specified, will default to the last user message or HyDE if HyDE is enabled in the dataset configuration. Default is None.
fulltext
, semantic
, hybrid
, bm25
Sort Options lets you specify different methods to rerank the chunks in the result set. If not specified, this defaults to the score of the chunks.
Typo Options lets you specify different methods to correct typos in the query. If not specified, typos will not be corrected.
If true, the search will be conducted using llm tool calling. If not specified, this defaults to false.
If use_group_search is set to true, the search will be conducted using the search_over_groups
api. If not specified, this defaults to false.
If true, quoted and - prefixed words will be parsed from the queries and used as required and negated words respectively. Default is false.
The user_id is the id of the user who is making the request. This is used to track user interactions with the RAG results.
Response
This will be a JSON response of a string containing the LLM's generated inference. Response if not streaming.
The response is of type string
.