TESSEN Platform
Documentation
Docs/Model capabilities
MODEL CAPABILITIES

Conversations

The API is stateless: you send the whole conversation with every request.

A chat request carries the conversation so far in messages, oldest first. Tessen does not keep a conversation between requests for the chat API: to continue one, append the model's reply and your next message, and send the whole list again.

roleUse
systemInstructions that frame the whole conversation. Put it first.
userWhat the person said.
assistantWhat the model said earlier. May carry tool_calls.
toolThe result of a function the model asked for. Carries tool_call_id.
CONTINUE A CONVERSATION
curl https://api.tessen.ai/v1/chat/completions \  -H "Authorization: Bearer $TESSEN_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "model": "z1",    "max_tokens": 256,    "messages": [      {"role": "system", "content": "Answer in one short sentence."},      {"role": "user", "content": "Name a prime number greater than 10."},      {"role": "assistant", "content": "13 is a prime number greater than 10."},      {"role": "user", "content": "And the next prime after it?"}    ]  }'

Things to plan for

  • Every request is billed for all the input tokens you send, including the history. Long conversations cost more per turn; trim or summarise old turns.
  • The context window is not published, so these docs state no number. Watch usage.prompt_tokens and keep conversations comfortably short.
  • Keep any conversation you need to keep. The Console Playground does not store conversations.

Search documentation

Titles, headings and guides↑ ↓ navigate · Enter open
Conversations · Tessen Docs