Poolside Laguna

Poolside models are called with the poolside/... canonical model id. Two models are in the public catalog:

Model	Context	Max output	Use case
poolside/laguna-s-2.1	262,144	32,768	Long-horizon coding agents, multi-file refactors
poolside/laguna-xs-2.1	262,144	32,768	Fast coding agents, short iteration loops

Both take text input and produce text output, support tool calling, and support native reasoning that can be toggled per request.

Free usage

Poolside serves these models free on its own inference API, so LLMTR lists them at $0 and does not draw from your credit balance. There is no extra token allowance to track; only the standard rate limit that applies to every LLMTR request.

The price is the one Poolside currently publishes. If Poolside ends free access, the catalog prices are updated accordingly.

Chat Completions

curl "$LLMTR_BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer llmtr-your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "poolside/laguna-s-2.1",
    "messages": [
      { "role": "user", "content": "What are channels in Go?" }
    ],
    "max_tokens": 800
  }'

Turning reasoning on and off

Reasoning is on by default. Turn it off per request with chat_template_kwargs.enable_thinking:

curl "$LLMTR_BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer llmtr-your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "poolside/laguna-xs-2.1",
    "messages": [
      { "role": "user", "content": "Write a unit test for this function." }
    ],
    "chat_template_kwargs": { "enable_thinking": false },
    "max_tokens": 600
  }'

Latency drops noticeably with reasoning off. Leave it on for complex, multi-step tasks where quality matters more.

Tool calling

Both models support the OpenAI-compatible tools schema:

curl "$LLMTR_BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer llmtr-your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "poolside/laguna-s-2.1",
    "messages": [
      { "role": "user", "content": "What is the weather in Ankara?" }
    ],
    "tools": [
      {
        "type": "function",
        "function": {
          "name": "get_weather",
          "description": "Get the current weather for a city",
          "parameters": {
            "type": "object",
            "properties": { "city": { "type": "string" } },
            "required": ["city"]
          }
        }
      }
    ]
  }'

See Tool calling for the general tool call flow.

Prompt caching

Prompt caching is active upstream, and repeated context is reported in usage.prompt_tokens_details.cached_tokens. Cache reads are free as well.

If you use Laguna XS.2

Poolside removed poolside/laguna-xs.2 from its API. Requests for that identifier are automatically forwarded to poolside/laguna-xs-2.1, so existing integrations keep working. Still, update your integrations to call poolside/laguna-xs-2.1 directly.

Data policy

Poolside states that prompts and completions on free access may be logged and used to improve its products. Take this into account for production workloads that carry sensitive data.