Poolside Models

4 modelsGeneral models free to startUp to 1.05M context

Usage

Last 20 days · 2026-08-26 to 2026-09-24

Tokens

138M

Requests

2.1K

Models in use

4 of 4

Tokens per day, stacked by model

010.2M20.3M08-2609-1209-192026-08-26 — 1,302,610 tokens laguna-s-2.1-free: 1,291,815 laguna-xs-2.1-free: 10,7952026-08-27 — 1,803,595 tokens laguna-s-2.1-free: 1,794,840 laguna-xs-2.1-free: 8,7552026-08-28 — 676,790 tokens laguna-s-2.1-free: 675,135 laguna-xs-2.1-free: 1,6552026-09-08 — 0 tokens2026-09-09 — 1,170 tokens laguna-xs-2.1-free: 630 laguna-s-2.1-free: 5402026-09-10 — 1,449,370 tokens laguna-xs-2.1-free: 1,434,190 laguna-s-2.1-free: 15,1802026-09-11 — 5,751,250 tokens laguna-xs-2.1-free: 5,020,620 laguna-s-2.1-free: 730,6302026-09-12 — 7,898,570 tokens laguna-s-2.1-free: 6,402,120 laguna-xs-2.1-free: 1,496,4502026-09-13 — 11,522,345 tokens laguna-s-2.1-free: 9,261,195 laguna-xs-2.1-free: 2,261,1502026-09-14 — 4,615,640 tokens laguna-s-2.1-free: 2,891,915 laguna-xs-2.1-free: 1,723,7252026-09-15 — 12,718,695 tokens laguna-xs-2.1-free: 6,456,370 laguna-s-2.1-free: 6,262,3252026-09-16 — 10,744,760 tokens laguna-xs-2.1-free: 9,732,220 laguna-s-2.1-free: 1,012,5402026-09-17 — 3,128,625 tokens laguna-xs-2.1-free: 1,574,035 laguna-s-2.1-free: 1,554,5902026-09-18 — 12,789,880 tokens laguna-xs-2.1-free: 12,783,600 laguna-s-2.1-free: 6,2802026-09-19 — 5,982,275 tokens laguna-xs-2.1-free: 5,889,035 laguna-s-2.1-free: 93,2402026-09-20 — 5,367,985 tokens laguna-xs-2.1-free: 5,188,655 laguna-s-2.1-free: 179,3302026-09-21 — 9,606,575 tokens laguna-s-2.1-free: 4,975,025 laguna-xs-2.1-free: 4,631,5502026-09-22 — 10,656,980 tokens laguna-s-2.1-free: 9,326,945 laguna-xs-2.1-free: 1,330,0352026-09-23 — 11,847,790 tokens laguna-s-2.1-free: 7,915,855 laguna-xs-2.1-free: 3,931,475 laguna-s-2.1: 230 laguna-xs-2.1: 2302026-09-24 — 20,338,425 tokens laguna-xs-2.1-free: 17,136,125 laguna-s-2.1-free: 3,202,300
  • laguna-xs-2.1-free
  • laguna-s-2.1-free
  • laguna-s-2.1
  • laguna-xs-2.1

Which models that traffic went to

  1. Laguna Xs 2.1 (free)58.3%80.6M
  2. Laguna S 2.1 (free)41.7%57.6M
  3. Laguna S 2.1<0.1%230
  4. Laguna Xs 2.1<0.1%230

Share of 138M tokens.

The two views disagree on purpose: a model can take a large share of the calls and a small share of the tokens — many short requests — or the reverse. Which one matters depends on whether your cost is driven by call volume or by prompt length. Measured on AIHubMix over the last 20 days, counting the 4 model IDs listed on this page; traffic routed through upstream-specific IDs that are not in the public catalog is not included.

All 4 Poolside Models

Open in model list
Poolside models on AIHubMix with input and output modalities, context length, maximum output, price per million tokens including cache read and cache write rates, and measured throughput and latency.
Modalities
laguna-s-2.1-freeTakes text, returns text.1.05M262KFreeFree/M—
laguna-s-2.1Takes text, returns text.1.05M—$0.1$0.2/M$0.01/M
laguna-xs-2.1-freeTakes text, returns text.262K—FreeFree/M—
laguna-xs-2.1Takes text, returns text.262K—$0.1$0.2/M$0.05/M

Prices are USD per million tokens; cache read and cache write are the rates for prompt-cache hits and for writing a prompt into the cache. Throughput and latency are measured on AIHubMix — the same figures the model detail page shows — not vendor claims. A dash means the catalog does not publish that field for that model, which is not the same as the model not supporting it.

Common Comparisons

laguna-s-2.1 vs laguna-s-2.1-freelaguna-s-2.1 vs laguna-xs-2.1laguna-s-2.1 vs laguna-xs-2.1-freelaguna-s-2.1 vs qwen3.8-max-previewkimi-k3 vs laguna-s-2.1

Poolside on AIHubMix

Which Poolside model should I start with?

laguna-s-2.1-free is free on input — the cheapest entry here that declares tool calling, and it carries a 1.05M context. Move up to laguna-s-2.1 when answer quality matters more than cost, or to laguna-xs-2.1-free for long-form reasoning.

Which of these models reason before answering?

2 of the 4 models here declare a reasoning phase — they work through the problem before producing an answer, which helps on multi-step problems at the cost of extra output tokens. Use the Reasoning filter above the table to see them. The catalog does not record anything further about how they differ, so this page does not sort them into families.

Why are there several entries for the same model?

Because each row is a route you can call, not a model release. Some IDs name an upstream (azure-, alicloud-, cc-), and some differ only in capitalisation, kept so older integrations keep working.

The catalog does not carry a field saying which of those a given row is, so this page does not sort them into buckets it would have to invent. Every row shows that route’s own price, context and speed — compare those directly, and open a model to see the upstreams that serve it.

How is cached input billed?

The Cache read column is the rate for input tokens served from the prompt cache — for example laguna-s-2.1 bills cache hits at 10% of the input rate and laguna-xs-2.1 bills cache hits at 50% of the input rate. Cache write is the surcharge for putting a prompt into the cache in the first place, and only a few upstreams bill it separately. A dash in either column means the catalog carries no cache rate for that model, so plan on paying the full input rate.

Do I need a separate Poolside account?

No. One AIHubMix key covers every model on this page, and switching between them is a change to the model string — billing, rate limits, and logs stay in one place.

Other Model Authors

See all model authors →
Qwen
148 modelsOpenAI
141 modelsGoogle
87 modelsZ.AI
71 modelsLlama
53 models

Start calling Poolside in one line

One key, one endpoint, 908 models across 41 model authors.

Get API keyRead the docs

© 2023 - 2026 AIHubMix, LLC

Product

Developer

Connect

Terms & Policies