Build Smarter Agents with Nemotron 3 Nano Omni on FriendliAI — Explore models
API Reference
Dedicated
Serverless
Container
Dataset & File
BetaFriendli SDK
curl --request POST \
--url https://api.friendli.ai/dedicated/v1/chat/render \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"messages": [
{
"content": "You are a helpful assistant.",
"role": "system"
},
{
"content": "Hello!",
"role": "user"
}
],
"model": "(endpoint-id)"
}
'{
"text": "<|begin_of_text|><|start_header_id|>system<|end_header_id|>\nYou are a helpful assistant.<|eot_id|><|start_header_id|>user<|end_header_id|>\nHello!<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n"
}Dedicated chat render
Preview the final prompt text that your Friendli Dedicated Endpoint will send to the model. Useful for debugging chat templates and token counts.
curl --request POST \
--url https://api.friendli.ai/dedicated/v1/chat/render \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"messages": [
{
"content": "You are a helpful assistant.",
"role": "system"
},
{
"content": "Hello!",
"role": "user"
}
],
"model": "(endpoint-id)"
}
'{
"text": "<|begin_of_text|><|start_header_id|>system<|end_header_id|>\nYou are a helpful assistant.<|eot_id|><|start_header_id|>user<|end_header_id|>\nHello!<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n"
}Given a list of messages forming a conversation, the API renders them into the final prompt text that will be sent to the model. To request successfully, it is mandatory to enter a Personal API Key (e.g. flp_XXX) value in the Bearer Token field. Refer to the authentication section on our introduction page to learn how to acquire this variable and visit here to generate your API Key.Documentation Index
Fetch the complete documentation index at: https://friendli.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Headers
ID of team to run requests as (optional parameter).
Body
ID of target endpoint. If you want to send request to specific adapter, use the format "YOUR_ENDPOINT_ID:YOUR_ADAPTER_ROUTE". Otherwise, you can just use "YOUR_ENDPOINT_ID" alone.
"(endpoint-id)"
A list of messages comprising the conversation so far.
[
{
"content": "You are a helpful assistant.",
"role": "system"
},
{ "content": "Hello!", "role": "user" }
]Additional keyword arguments supplied to the template renderer. These parameters will be available for use within the chat template.
A list of tools the model may call. Use this to provide a list of functions the model may generate JSON inputs for.
When tools is specified, min_tokens and response_format fields are unsupported.
Hide child attributes
Hide child attributes
The type of the tool. Currently, only function is supported.
"function"Hide child attributes
Hide child attributes
The name of the function to be called. Must be a-z, A-Z, 0-9, or contain underscores and dashes, with a maximum length of 64.
The parameters the functions accepts, described as a JSON Schema object.
To represent a function with no parameters, use the value {"type": "object", "properties": {}}.
A description of what the function does, used by the model to choose when and how to call the function.
Response
Successfully rendered chat messages into prompt text.
The rendered text.