Explore more topics
Published model evaluations

Laguna Xs 2.1: trading task evaluations

See how poolside/laguna-xs-2.1 performed in 1 trading task evaluation, with exact version, measured results, dates and test inputs.

As of 2026-08-08

Jump to a section

TL;DR

Laguna Xs 2.1 recorded a next-action mean of 51.1 and valid structured output on 66.5% of responses in the August 2026 evaluation. Historical billing was $5.58 per 1,000 decisions and production median latency was 4.3 seconds. Its quick responses came with low decision scores and frequent structure failures. The study replayed 69 saved decisions three times each; it judged proposed actions rather than executing a new trading workflow.

Exact tested ID
poolside/laguna-xs-2.1
Published studies
1
Provider
poolside

Next-action execution model bakeoff: compare the tested outputs

Valid structured next-action output

Scale: 0 to 100 % · zero baseline

69 frozen decisions × 3 samples

  • Laguna Xs 2.1+66.5%
  • Luna Pro+100%

August 8, 2026 replay of 69 decisions with three samples each. Valid structure can still contain the wrong action. Laguna scored 51.1 and Luna Pro scored 91.7 on judged decision quality.

Show the table · 2 rows, 5 columns

Scroll sideways to compare all columns. Select a heading to sort.

poolside/laguna-xs-2.151.166.5%$5.584.3s
openai/gpt-5.6-luna-pro91.7100.0%$25.059.9s

23-model campaign; 69 frozen decisions × 3 samples; 12 published model rows. Published 2026-08-08. Values retain their original units and grading scale.

poolside/laguna-xs-2.1 was tested on 2026-08-08. 23-model campaign; 69 frozen decisions × 3 samples; 12 published model rows. Its row and the other published arm use the same task and measurement units.

What this version helps you choose

A short median response time accompanied low next-action scores and 66.5% output validity. Readable structured actions matter alongside speed.

Choose the next allowed agent action: follow the published task

A well-formed action can still be the wrong decision. Keep output validity and judged decision quality separate.

Step 1 of 2

Published task summary

The existing plan, conversation and results returned by tools.

What you should see

Choose one next allowed action, or finish with an answer when the evidence is sufficient.

Step 2 of 2

Read what came back

A structured action. The replay records the proposed action without executing its tools.

What you should see

Replay 69 saved decisions three times each. Check the required output structure separately from the judge score.

Next-action execution model bakeoff

For the next allowed action, Laguna Xs 2.1 recorded a judge mean of 51.1 and produced valid structured output 66.5% of the time. Historical billing was $5.58 per 1,000 decisions; production median response time was 4.3s. Decision quality, readable output and operating cost answer different questions.

Show the table · 4 rows, 2 columns
Published metricValue
Mean score51.1
Schema valid66.5%
$ / 1k decisions$5.58
Prod p504.3s

Next-action execution model bakeoff: read these measurements

Read the complete rubric, sample and billing notes

23-model campaign; 69 frozen decisions × 3 samples; 12 published model rows

Choose one next action in an unfinished trading-agent workflow. This replay measures individual decisions, not a fresh complete trading run.

  1. Scoring

    Mean action score comes from the judge. Schema validity is the share of actions matching the required output structure; a valid structure can still contain the wrong action. Switching judges reduced the Luna-versus-DeepSeek score gap from 13.9 to 1.5 points.

  2. Cost units

    Cost uses historical provider billing per 1,000 decisions. Reused prefixes earned cache discounts; the cached-token split was not retained.

  3. Time units

    Prod p50 is median production response latency, separate from replay quality and complete agent wall time.

Continue exploring

Discussion

Sign in or create a free account to join the discussion.

No comments yet.

Aurora · AI research assistant

Try this in Aurora

Edit the request, then open it in Aurora. You choose when to send it.