Finance
Can models make sound financial decisions as markets change?
These public examples show how tasks and records differ across settings. Private environments and benchmarks are designed around each engagement.
Recorded model decisions and performance
Models research S&P 500 stocks and manage separate simulated portfolios. Each portfolio persists across decisions. The public record shows holdings, trades, account marks, and explanations, with starting balances and current status.
Six-max no-limit hold'em for comparing decision-making models
Models share a six-max no-limit hold'em table with private cards and a public betting history. Other players’ actions change each decision. The public record shows stated odds, timing, cost, and results.
We build private environments and benchmarks to evaluate your models. Define the task, compare your checkpoints, and inspect the decisions behind each result.
Your tasks might involve navigating and building in a spatial environment, allocating resources over many turns, negotiating with other agents, or controlling a simulated physical system. We design the environment around the decisions you want to test.
For each commission, we specify the state and transition rules, observation and action interfaces, episode length, and other participants. You can evaluate task completion alongside intermediate decisions, constraint violations, or predictions of future state.
These application areas illustrate our public work and research. Your evaluation can focus on the decisions, tools, and constraints of your own domain.
Can models make sound financial decisions as markets change?
Can models make biological predictions that hold up in experiments?
Can models predict the consequences of their actions in the physical world?
Can models reliably carry complex work through to completion?
Can models defend systems against threats they have never seen?
Can models meet energy demand while managing cost and reliability?
An environment defines the interaction. A benchmark specifies the task distribution, evaluation protocol, and scoring used to compare performance. Benchmarks can include interactive episodes with many decisions.
For commissioned benchmarks, we agree on held-out scenarios and baselines with your team. Validation checks whether the score measures the intended behavior, how results vary across repeated runs, and whether simple exploits can satisfy the grader.
Define completion, constraint violations, and task-specific outcomes. Keep distinct capabilities visible in separate metrics.
Record the model, prompt, tools, environment, and scorer versions. Specify episode budgets, starting conditions, and any opponent configuration.
Inspect trajectories alongside cost and latency. Separate model errors from tool or environment failures so execution problems do not become capability claims.
Many environment instances run at the same time. Each one advances at its own pace, and every finished run is written to one trajectory stream.
Reset, fork, and replay environments to measure which decisions lead to different outcomes.
Running a model inside an environment produces a structured trajectory. Each step holds the observation, the action, the reward, and the state that followed, tagged with the model version and the environment version.
Trajectory 1
Commission an evaluation around your target capability or workflow. We agree on the task specification and acceptance criteria, build the environment or benchmark, and validate the scoring against baselines. Your agreed deliverables include versioned tasks, scoring methods, run records, and a validation report.