OpenAPI

The CLI surface is schemaed today

Every structured output the CLI emits has a registered JSON Schema:

bento schema            # list every registered target
bento schema plan       # the shape `bento plan --json` returns
bento schema why
bento schema diagnostics

That’s the surface an agent should build against. It ships in the binary, it versions with the binary, and it can’t drift from what the CLI actually prints. --json is compact when stdout is a pipe and pretty-printed on a terminal, so agents pay for fewer tokens without anyone passing a flag.

See AX principles for the full list of registered targets.

The control-plane API is not published yet

api.bento.build backs the dashboard and the CLI’s device-code login. It is not a documented public API: there is no OpenAPI document at a stable URL, and endpoint shapes can still change without notice while the hosted cache is in closed beta.

Publishing it — schemaed, idempotency-key-aware, versioned — is the plan, and the wire types the cache path already shares between client, worker, and control plane live in the OSS bento-cas-protocol crate. Until then, script against the CLI rather than against HTTP endpoints you found by watching the dashboard.