Sandbox

Bounded command execution, file writing, logs, artifacts, and public-safe reports.

browser validation lane

Validate Sandbox in BrowserOps

Preview the plan publicly or launch the trusted-domain browser check using the server-side Vercel PLATPHORM_API_KEY when no key is entered.

Preview JSON

live passed

Live Public Connectivity

Sandbox is reachable for public discovery. Use Browserbase-backed protected runs for browser evidence.

Live JSON

health

200passed

trace echoed

apiDocs

200passed

trace echoed

llms

200passed

trace echoed

mcp

200passed

trace echoed

handoffReceiver

200passed

trace echoed

Browserbase Runtime

Protected BrowserOps runs for Sandbox use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.

tight integration contract

Sandbox Handoff Lane

Sandbox sends public preview URLs or reports; BrowserOps validates the real browser page through Browserbase, captures public-safe artifacts, and sends confirmed evidence back only after downstream acceptance.

Preview plan

Public-safe, no run stored.

Run with Browserbase

Protected run uses server-side key when blank.

Track handoff

No delivery claim without downstream response.

Capability Mapping

BrowserOps may call

read_preview_report
read_public_artifact

BrowserOps may receive

preview_url_ready
sandbox_report_ready

Transport and Boundary

Preferred transports: openapi, mcp, webhook, trace
API docs: https://sandbox.platphormnews.com/api/docs
MCP status: not advertised
Auth boundary: Public preview reads may be public-safe; execution and artifact persistence require PLATPHORM_API_KEY.

Handoff Examples

sandboxtobrowseropspreview_ready

Sandbox remains the bounded execution lab; BrowserOps verifies the resulting public preview.