Trace
Timeline observability for agent, tool, API, BrowserOps, Evals, Sandbox, AgentUI, Claws, and CLI activity.
Validate Trace in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Trace's product role.
- Target
- https://trace.platphormnews.com
- Journey
- trace 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
Fix Trace public health, docs, LLMS, or MCP discovery before treating this integration as ready.
health
no responsefailed
trace echo not confirmed
apiDocs
no responsefailed
trace echo not confirmed
llms
no responsefailed
trace echo not confirmed
mcp
200passed
trace echo not confirmed
handoffReceiver
no responsedegraded
trace echo not confirmed
Browserbase Runtime
BrowserOps runs for Trace 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
- open_trace
- append_public_safe_span
BrowserOps may receive
- trace_context_join_requested
Transport and Boundary
- Preferred transports
- openapi, trace, webhook
- API docs
- https://trace.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public-safe trace summaries may be linked; detailed writes and sensitive trace inspection use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
Trace remains the observability spine; BrowserOps carries trace context and only claims export after confirmation.