Assistant Gym / For Builders

Build where assistants already work.

APIs, headless interfaces, local tools and assistant-to-assistant communication will be essential. The Gym must fit into existing assistant workflows, not ask the world to switch platforms.

Designed for two kinds of users

Human-operated experiences. Assistant-operated interfaces.

A human can explore a result in a browser. An assistant needs explicit machine interfaces, defined inputs and outputs, predictable errors and the evidence necessary to continue the job.

01 / Browser

See the work.

Readable examples, interactive explanations and selected early tools.

02 / Local & CLI

Bring the work to the Gym.

Use supported focused checks locally where exact packages and input contracts exist.

03 / Headless & connectors

Let assistants use it.

Connect assistants to the Gym through APIs, MCP, plugins and extensions as the interfaces become available.

A common contract

An assistant doesn't need a dashboard.

It needs a clear way to ask for supported help and receive a result it can interpret, verify and act on appropriately.

Example product interface shape
{
  "product": "structured decision check",
  "job": "compare expected and actual fields",
  "inputs": "supported JSON schema",
  "result": "specific findings and limits",
  "evidence": "input, version, observation"
}
Current engineering evidence

The parts we can actually name.

Existing Alpha tools

Alpha web and local surfaces.

Bill Check, Decision Audit, Reply Compare, Assistant Audit, Practice and supported local tools each provide a limited job-specific entry.

Explore the current tools ↗
Connected tools and interfaces

Build. Connect. Do the work.

The Gym is being built with web tools, local utilities and connectors so people can keep using the assistants they already have.

Explore the route status ↗
Developer principle

Connectivity is useful. Completion is the point.

A successful tool call is not a finished job. An assistant needs to know whether the actual state changed, whether an action was authorized and which evidence it can rely on.

As the company matures, that requirement should inform every headless interface, connector and organizational integration we build.

The path from connection to useful work

From a working connection to a finished job.

A useful connection gives the assistant a real job it can finish, a clear result and a reason to come back.