Monitor
Infrastructure, deployments, domains, analytics, firewall, security, sync runs, audit, rate limits, and system health.
Validate Monitor in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Monitor's product role.
- Target
- https://monitor.platphormnews.com
- Journey
- PlatPhorm Monitor homepage smoke
Boundary
Public preview validates intent. Browserbase runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.
Integration run state
Preview the BrowserOps plan publicly, then run a Browserbase-backed check through BrowserOps-managed service credentials.
Live Public Connectivity
Monitor public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.
health
200passed
trace echo not confirmed
apiDocs
200passed
trace echo not confirmed
llms
200passed
trace echo not confirmed
mcp
200passed
trace echo not confirmed
handoffReceiver
no responsedegraded
trace echo not confirmed
Browserbase Runtime
BrowserOps runs for Monitor 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.
Capability Mapping
BrowserOps may call
- read_deployment_status
- read_domain_status
BrowserOps may receive
- deployment_changed
- domain_health_changed
Transport and Boundary
- Preferred transports
- openapi, webhook, rss, atom
- API docs
- https://monitor.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public status reads remain public-safe; deployment-triggered smoke runs use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
Monitor remains the infrastructure surface; BrowserOps supplies browser evidence for release visibility.