Reference

The guides explain how to build with any; this section lists what exists. Every endpoint, command, frame, error code and config key is here once, in the shape you will see on the wire, so you can look something up without reading a chapter.

How the pieces fit

your client / script / agent
        │  HTTP + JSON, SSE           (http-api, events, errors)
        ▼
any server  127.0.0.1:7001            (config, cli)
        │  encrypted CRDT sync
        ▼
sync network + your other devices

anyrt serve  127.0.0.1:7010           (anyrt-cli, anybao-toml)
   └─ sandboxed programs ── effects ──▶ any server, LLM, web   (effects-catalog)
   └─ triggers                                                 (trigger-schema)

Two binaries, two config files, one API. The any CLI is a thin client over the HTTP API — every subcommand is one endpoint — and anyrt is a client of the same API from inside a sandbox.

Conventions used throughout

Paths are relative to http://127.0.0.1:7001; … in a path stands for the /v1/spaces/:spaceId prefix already shown in that table.
$SP, $OBJ, $CHAT in examples are a space id, an object id and a chat object id you substitute.
Dates on the wire are instants: {"$date": "2026-08-05T17:00:00.000Z"}.
Every non-2xx response is {"error": {"code", "message", "details?"}}.

HTTP APIEvery endpoint, grouped, with bodies, returns and error codes CLIEvery any command group with flags and exit codes SSE streamsEvery live stream, its frames, and the shared close reasons ErrorsThe envelope, status rules, and the full code namespace Server configurationEvery key, env var, flag, default and precedence anyrt CLIrun, serve, deploy, trace, drift — and the control API Effects catalogThe complete sandbox syscall surface and its capabilities Trigger schemaagent_trigger fields, kinds, runs, and control routes anybao.tomlEvery key of the runtime's host config GlossaryOne-line definitions with a link to the page that covers each