Explore more topics
Published model evaluations

Grok 4.5: trading task evaluations

See how x-ai/grok-4.5 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

Grok 4.5's planning mean was near the leaders in the August 8, 2026 study of 29 frozen conversations. It scored 0.724 with a standard error of 0.065, at historical billing of $0.0519 per decision and 23.5-second median latency. Luna had lower cost and median response time. Small differences in mean score should be read with the sample uncertainty.

Exact tested ID
x-ai/grok-4.5
Published studies
1
Provider
x-ai

Planning models on 29 frozen conversations: compare the tested outputs

Recorded planning response time

Scale: 0 to 23.5 seconds · zero baseline

Same planning replay

  • Grok 4.5+23.5 seconds
  • Muse Spark 1.1+9.6 seconds

These exact August 8, 2026 p50 cells compare the displayed Grok and Muse arms on 29 frozen conversations. Labels are rounded; the means and standard errors remain exact in the full table.

Show the table · 2 rows, 5 columns

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

x-ai/grok-4.50.7240.065$0.051923.5s
meta/muse-spark-1.10.7590.079$0.02299.6s

16-model campaign, 29 frozen conversations; 14 model rows shown in the public table. Published 2026-08-08. Values retain their original units and grading scale.

x-ai/grok-4.5 was tested on 2026-08-08. 16-model campaign, 29 frozen conversations; 14 model rows shown in the public table. Its row and the other published arm use the same task and measurement units.

What this version helps you choose

Its planning mean was near the leading means, while recorded billing and median response time exceeded Luna’s.

Route a request and plan the work: follow the published task

A useful planner chooses the right kind of work before doing it. The complete customer conversations and system prompts remain private.

Step 1 of 2

Published task summary

An incoming request and its existing conversation.

What you should see

Choose whether to write a plan, call a catalog tool, ask for clarification or continue an existing agent.

Step 2 of 2

Read what came back

A routing decision and plan. Every model receives the same saved conversation; the test compares that decision before fresh research begins.

What you should see

Replay 29 frozen conversations across the model arms, then compare graded plan scores, billing and response time.

Planning models on 29 frozen conversations

Inspect the original Grok planning metrics

For routing and planning, Grok 4.5 recorded a mean score of 0.724 with standard error 0.065. Historical billing was $0.0519 per decision, and median response time was 23.5s. Compare that cost and response time with the other models in the same 29-conversation study; the mean alone does not establish a decisive quality advantage.

Published metricValue
Score0.724
+/- SE0.065
$ / decision$0.0519
p5023.5s

Planning models on 29 frozen conversations: read these measurements

Read the complete rubric, sample and billing notes

16-model campaign, 29 frozen conversations; 14 model rows shown in the public table

Route an incoming request: write a plan, call a catalog tool, ask for clarification or continue an existing agent.

  1. Scoring

    Top planning means were close at this sample size. The source's paired comparison with Opus was inconclusive.

  2. Cost units

    Cost is provider-billed dollars per decision. Prefix reuse can make it differ from list price multiplied by every input token.

  3. Time units

    p50 is median latency in seconds, not the duration of complete research.

  4. Frozen conversation

    A saved input kept identical across model arms so their decisions can be compared.

  5. Standard error (SE)

    An estimate of uncertainty around the sample mean. A small mean difference needs more evidence than the ranking alone.

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.