Docs / Docs

Build and run

Build in the Lab or over MCP. Run it for real. Publish it to the Market.

What you can publish

Thing	What it is
Skill	One ability, written as a standard `SKILL.md`.
Rig	A flow of steps: skills, MCP tools, model steps.
MCP server	Your own server, listed by its URL. Rokha reads its tools and lists each one.
Agent	A persona with its own tools, on its owner's model keys.

A free account can list 1 agent, 3 rigs, 2 MCP servers and 3 skills. The Lab removes the limits.

In the Lab

Open rokha.ai/lab, or press Run on any Market listing. Tell Rokha what you want, test it, and publish it.

Over MCP

rig_author {name, nodes, edges}   # save a rig
rig_run {rig_id, input}           # a real run, a real trace
rig_publish {rig_id}              # list it on the Market
trace_get {id}                    # read a step

REST twins: POST /api/rigs/run, POST /api/rigs/publish, GET /api/traces/{id}.

Keys

Save a key once (Profile → API keys) or connect an account. A step that calls an API (url) or a remote MCP tool (endpoint + tool) attaches it with secret_refs. Rokha's servers add the key at the call; it never appears in params, traces or listings, and whoever runs the rig uses their own.

The sandbox

Code that has no hosted server runs in Rokha's cloud sandbox: an isolated microVM, non-root, outbound network only, and never any of your saved keys.

A run	A fresh sandbox per run, about 4 minutes of work. 0.25 vCPU / 1 GB free, 1 vCPU / 2 GB on the Lab.
A session	One sandbox kept alive across commands: 15 minutes free, up to 4 hours on the Lab. A step you run while your session is live may run inside it.
Tools inside	Node 22, Python 3, git, curl, jq, ripgrep. Packages install with npx or pip at run time. A missing tool fails with its real error.
Keeping things	Files end with the sandbox. Keep what matters in the run's result or a data step.
Transforms	A transform step runs your Python or TypeScript once, with no network and no keys (30 s, 512 MB, 1 MB out). Fetch in the step before it.

Every published thing gets doors

Each listing has its own REST door and MCP door. All of a builder's tools are one MCP server at https://rokha.ai/mcp/@yourhandle/jsonrpc. You choose who can call it: anyone, key holders, or only you.

Proven

A clean end-to-end run earns the Proven stamp. It is tied to the exact version that ran, so changing the code clears it.