Measured harness ledgerPublic result
Grok 4.6

High-voxel-density Jungle Temple diorama — Grok 4.6 xhigh

Create a complete inspectable Blender voxel diorama of a jungle temple at a fixed 0.05-unit voxel resolution through the Blender MCP workflow.

xhigh reasoningHeadline result
Workflow cost
$2.11
Wall-clock
13m 09.039s wall-clock
Processed tokens
3.29M processed
Record state
partial_one_shot_token_timing_and_artifact_ledger
Public summary

Grok 4.6 xhigh partial_one_shot_token_timing_and_artifact_ledger ledger: 13m 09.039s wall-clock, 3.29M processed, and $2.11 Official-rate API-equivalent estimate that exactly reconciles to the provider-recorded usage estimate; not a subscription cash-charge invoice..

Run identity and stack
  • Result ID: jungle-temple-grok-4.6-xhigh
  • Technical model: Grok 4.6
  • Provider: xAI Grok Build
  • Client: Grok 1.0.3
  • Stack: xAI Grok Build
  • Stack: Grok 1.0.3
  • Stack: Technical model/configuration: Grok 4.6
  • Stack: Blender MCP
  • Stack: 0.05-unit voxel grid
  • Stack: Inspectable .blend artifact
Primary artifact integrity
  • Kind: blender-scene
  • Path: artifacts/jungle-temple-grok-4.6-xhigh/jungle_temple.blend
  • SHA-256: 2c0f27d59586847a5238b8f836c67531cc8c02e2e358c43b5946fdca98342388
Recorded caveats
  • Wall-clock is end-to-end latency, not model-only compute; it includes tool time and idle intervals.
  • Generated output includes visible output and reasoning output as provider-reported.
  • Cache reads are discounted in provider billing, so total processed tokens overstate cost.
  • The $2.11 figure is an official-rate API-equivalent estimate that reconciles to the provider-recorded usage estimate; it is not a subscription cash charge.
  • The receipt reports aggregate tool counts only; it does not publish a tool-by-tool transcript.
  • The final scene and supplied preview are archived; Blender was unavailable during intake, so the scene was not independently reopened or rerendered.
  • The source builder's output destinations were made portable without changing scene-building logic; the received and published hashes are both committed in the source manifest.
  • No render-hardware receipt, initial/optimized local FPS pair, RTX Pro 6000 1080p60 final capture, or blind evaluation is archived.
Visible evidence gaps
  • Blender version and render-hardware receipt
  • independent Blender scene inspection and rerender
  • initial local FPS
  • optimized local FPS
  • RTX Pro 6000 1080p60 final capture
  • blind-evaluation record
Public result only

This result keeps its public summary and evidence, but it does not currently have a matching Builder test with prompts, projects, Harness workflows or skills.

RemakeBenchResearch console