Poolside Models
Usage
50.9M
842
2 of 2
- laguna-s-2.1-free
- laguna-xs-2.1-free
- laguna-s-2.1-free
- laguna-xs-2.1-free
Which models that traffic went to
- Laguna S 2.1 (free)75.2%38.3M
- Laguna Xs 2.1 (free)24.8%12.6M
- Laguna S 2.1 (free)60.3%508
- Laguna Xs 2.1 (free)39.7%334
All 2 Poolside Models
Open in model list| Modalities | |||
|---|---|---|---|
| laguna-s-2.1-free | Takes text, returns text. | 1.05M | FreeFree/M |
| laguna-xs-2.1-free | Takes text, returns text. | 262K | FreeFree/M |
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-xs-2.1-free when answer quality matters more than cost.
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.
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.
Start calling Poolside in one line
One key, one endpoint, 880 models across 38 model authors.

