Poolside: Laguna XS 2.1
Catalog snapshot on AI Hippo. This model is discoverable on-site even when it is not currently included in the global ranking list.
Data updated:
Model
1 verified sources
Aggregator quote only — no official sync yet
Next steps on AI Hippo
This model is currently available from the catalog snapshot and may not be included in the latest ranked board yet.
About this model
Poolside: Laguna XS 2.1 is listed in our model catalog as a LLM model with 262,144 ctx and a snapshot average price around $0.09 per 1M tokens. The tables below summarize the latest catalog snapshot; use Compare or the Token hub to dig deeper.
You can also explore more models from Poolside , and browse more options from 🇺🇸 United States .
Capabilities & specs
- Modality
- text->text
- Input modalities
- text
- Supported API parameters
- include_reasoning, max_tokens, reasoning, temperature, tool_choice, tools
Catalog description: Laguna XS 2.1 is the latest coding agent model in the 33B-A3B category from [Poolside](https://poolside.ai/) and a step forward from their Laguna XS.2 model (released in April 2026). It combines...
Token pricing by provider
Compare per-provider token prices for this model across available platforms.
| Provider | Input / 1M tokens | Output / 1M tokens | Latency | Status |
|---|---|---|---|---|
| OpenRouter | $0.06 | $0.12 | — | Verified · 2026-07-06 |
Provider prices are sourced from the token comparison dataset and may change between snapshots.
Alternative picks
-
Qwen: Qwen3 Coder 480B A35B (free)
Compare now -
DeepSeek: DeepSeek V4 Flash
Compare now -
Z.ai: GLM 5.2
Compare now
Pick one or two more models on global rankings and use Compare to view them side by side.
FAQ
Why is the official price missing?
Official rows require a verified direct vendor or cloud API price. When only aggregators list a model, the Official column shows — and verified aggregator quotes appear in the token table.
How is context different from max output tokens?
Context window is how much input the model can accept in a single request. Max output tokens is the per-response generation cap from the primary listing—often much smaller than the context window.
Where do multi-provider prices come from?
Prices are crawled or synced from token providers (OpenRouter, Groq, Together, and others) and merged into the infrastructure comparison dataset. Verified rows show a fetch date in the status column.
Data source & methodology
- Source
- OpenRouter catalog, verified vendor crawls, and Hugging Face hub snapshots.
- Metrics
- Context window, blended 1M-token price, max output tokens, and capability fields from the OpenRouter models API.
- Update cadence
- Daily pipeline refresh; provider prices may change between snapshots.
- Fetched at
- 2026-07-06
- Method
- Composite rank uses on-site context × price weighting (not LMSYS Arena ELO).