Page guide
BrowserOps proves what happened in the browser. Public reads stay open; trusted-domain execution uses the configured platform key path.
Complete reference for BrowserOps APIs, browser automation, and PlatPhorm Network integration.
Complete REST API documentation and SDK
PostgreSQL schema and data models
Playwright and browser journey execution
Public-safe reads and protected action boundary
Blob storage and artifact management
PlatPhorm Network service integration
curl https://browserops.platphormnews.com/api/v1/health
curl -X POST \ -H "Authorization: Bearer $PLATPHORM_API_KEY" \ https://browserops.platphormnews.com/api/v1/journeys/browserops-homepage-smoke/run
Run API controls open an action panel and never navigate directly to POST-only endpoints. GET on a run endpoint returns structured 405 JSON; trusted-domain browser execution uses a request key when provided, or the server-side Vercel PLATPHORM_API_KEY when no operator key is entered.
platphormctl browserops flow browserops-homepage-smoke --mode protected_browser_run platphormctl site inspect browserops platphormctl mcp validate browserops