Browser workflows
Multi-step tasks with state, tools, recovery paths, and a verifiable end state.
- Task state
- Tool calls
- Final artifact
We turn real work into structured environments, trajectories, and evaluations that an agent can practice and a team can inspect.
Each product starts with a real workflow and ends with an outcome that can be replayed, checked, and improved.
Multi-step tasks with state, tools, recovery paths, and a verifiable end state.
Change-making workflows that connect intent, files, commands, tests, and reviewable diffs.
Open-ended work with source material, intermediate decisions, and a rubric for the outcome.
Composable tasks for systems that learn by acting, observing, correcting, and trying again.
These examples show the shape of an Apexy trajectory. Production collections are built around each team's task distribution and evaluation needs.
| Task | Domain | Trace | Check |
|---|---|---|---|
| Browser checkout recovery | Web | State → actions → artifact | Replayable |
| Repository migration | Code | Plan → diff → tests | Diff checked |
| Multi-source research brief | Reasoning | Sources → decisions → rubric | Rubric scored |
| Pick-and-place recovery | Robotics | Observation → action → outcome | State logged |
Structure is what makes a trajectory more than a recording. It lets teams see where an agent acted, why it failed, and what to try next.
Start with a task that has context, constraints, and a meaningful outcome.
Add the tools, state transitions, and dependencies an agent must navigate.
Make the target, trajectory, and evaluation criteria inspectable.
Turn what the agent did into the next environment, task, or test.