Docs

Gateway API

Every Murable computer exposes one token-gated gateway. Point your agent at it and drive the machine with Computer Use and Browser Use commands — no coordinates required for menu items, a structured element tree when you need to see, and a standard Chrome DevTools endpoint for the browser.

Authentication

The gateway is reached through the panel proxy, which keeps a stable address and wakes a stopped machine on the next request. Authenticate every call with your gateway key as a bearer token.

Base URL   https://app.murable.ai/gw/{computer_id}

Authorization: Bearer <gateway_key>
Endpoint paths below are appended to the base URL — for example GET https://app.murable.ai/gw/{computer_id}/computer/tree. Your gateway key is shown in the panel and can be regenerated there. Access is only through this gateway; raw CDP is not exposed to the open internet.

Endpoint reference

See
MethodPathDescription
GET/computer/tree?app=…structured element tree {role,name,bbox,text} — cheap, preferred
POST/computer/capturescreenshot PNG — fallback when the tree is not enough
Act
MethodPathDescription
POST/computer/click_elementclick a menu/dialog item by {name} — no coordinates
POST/computer/clickclick at {x,y}
POST/computer/double_clickdouble-click at {x,y}
POST/computer/movemove cursor to {x,y}
POST/computer/typetype {text}
POST/computer/keypress {key} — "Enter", "ctrl+c"
POST/computer/dragdrag {start_x,start_y,end_x,end_y}
POST/computer/scrollscroll {direction,amount}
POST/computer/waitpause {seconds} (≤60)
GET/computer/windowslist open windows
POST/computer/focusfocus a window {app}
Files & shell
MethodPathDescription
POST/computer/bashrun a shell command {command} (user abc)
POST/computer/execrun Python {code}
GET/files/list?path=…list a directory
GET/files/read?path=…read raw file bytes
POST/files/writewrite a file {path, content | content_b64}
DELETE/files/delete?path=…delete a file / directory
Browser (CDP)
MethodPathDescription
CDP/cdp/<key>Chrome DevTools endpoint — /browser connect or Playwright --cdp-endpoint

Browser Use over CDP

The gateway exposes the built-in cloud browser through a standard Chrome DevTools Protocol (CDP) endpoint at /cdp/<gateway_key>. CDP runs over a WebSocket, so any tooling that speaks it connects unchanged — attach Playwright with connectOverCDP (or --cdp-endpoint), Puppeteer with connect({ browserWSEndpoint }), or a Browser Use /browser connect. Because the connection is proxied through the gateway, the same bearer key gates it and the machine wakes on demand.