docs/protocol/extension_generate.md
[!NOTE] The Generate Extension is provisional and likely to change in future versions.
This document describes Triton's generate extension. The generate extension provides a simple text-oriented endpoint schema for interacting with large language models (LLMs). The generate endpoint is specific to HTTP/REST frontend.
In all JSON schemas shown in this document, $number, $string, $boolean,
$object and $array refer to the fundamental JSON types. #optional
indicates an optional JSON field.
Triton exposes the generate endpoint at the following URLs. The client may use HTTP POST request to different URLs for different response behavior, the endpoint will return the generate results on success or an error in the case of failure.
POST v2/models/${MODEL_NAME}[/versions/${MODEL_VERSION}]/generate
POST v2/models/${MODEL_NAME}[/versions/${MODEL_VERSION}]/generate_stream
Both URLs expect the same request JSON object, and generate the same JSON response object. However, there are some differences in the format used to return each:
/generate returns exactly 1 response JSON object with a
Content-Type of application/json/generate_stream may return multiple responses based on the inference
results, with a Content-Type of text/event-stream; charset=utf-8.
These responses will be sent as
Server-Sent Events
(SSE), where each response will be a "data" chunk in the HTTP
response body. In the case of inference errors, responses will have
an error JSON object.
/generate_stream.Content-Type of application/json, similar to errors
from other endpoints with the status code set to an error.The generate request object, identified as $generate_request, is required in the HTTP body of the POST request. The model name and (optionally) version must be available in the URL. If a version is not provided, the server may choose a version based on its own policies or return an error.
$generate_request =
{
"id" : $string, #optional
"text_input" : $string,
"parameters" : $parameters #optional
}
[!NOTE] Any additional properties in the request object are passed either as parameters or tensors based on model specification.
The $parameters JSON describes zero or more “name”/”value” pairs,
where the “name” is the name of the parameter and the “value” is a
$string, $number, or $boolean.
$parameters =
{
$parameter, ...
}
$parameter = $string : $string | $number | $boolean
Parameters are model-specific. The user should check with the model specification to set the parameters.
Below is an example to send generate request with additional model parameters stream and temperature.
$ curl -X POST localhost:8000/v2/models/mymodel/generate -d '{"id": "42", "text_input": "client input", "parameters": {"stream": false, "temperature": 0}}'
POST /v2/models/mymodel/generate HTTP/1.1
Host: localhost:8000
Content-Type: application/json
Content-Length: <xx>
{
"id" : "42",
"text_input" : "client input",
"parameters" :
{
"stream": false,
"temperature": 0
}
}
A successful generate request is indicated by a 200 HTTP status code.
The generate response object, identified as $generate_response, is returned in
the HTTP body.
$generate_response =
{
"id" : $string
"model_name" : $string,
"model_version" : $string,
"text_output" : $string
}
200
{
"id" : "42"
"model_name" : "mymodel",
"model_version" : "1",
"text_output" : "model output"
}
A failed generate request must be indicated by an HTTP error status
(typically 400). The HTTP body must contain the
$generate_error_response object.
$generate_error_response =
{
"error": <error message string>
}
400
{
"error" : "error message"
}