Docs guide
Documentation pages describe what BrowserOps can prove today, what remains private or sensitive, and how public evidence can be reused by other PlatPhorm services.
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 managed action boundary
Blob storage and artifact management
PlatPhorm Network service integration
curl https://browserops.platphormnews.com/api/v1/health
curl -X POST \ 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 BrowserOps-managed service credentials when configured. Direct service-to-service clients can still send platform authorization headers.
platphormctl browserops flow browserops-homepage-smoke --mode browserbase_run platphormctl site inspect browserops platphormctl mcp validate browserops