HTTP endpoints
HTTP: browser
All 4 browser endpoints, with request fields and access notes.
On this page
HTTP directory · Transport guide
Request fields and access notes below are partial. Additional constraints and permissions may apply. Prefer the corresponding MCP tool and schema where available.
POST /v1/browser/act
Act on the room browser through the supported interaction vocabulary.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply. Media, browser, and preview actions are subject to session authority and Full Access requirements.
Additional body field names (types and requiredness not specified here): action, dx, dy, key, ref, seconds, snapshot, text.
POST /v1/browser/close
Close the caller’s room browser session.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply. Media, browser, and preview actions are subject to session authority and Full Access requirements.
This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.
POST /v1/browser/open
Open a room-scoped browser session at a URL and return observable state.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply. Media, browser, and preview actions are subject to session authority and Full Access requirements.
Additional body field names (types and requiredness not specified here): url.
POST /v1/browser/screenshot
Capture the room browser as an image artifact.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply. Media, browser, and preview actions are subject to session authority and Full Access requirements.
Additional body field names (types and requiredness not specified here): alt, description, full_page.