Trace
Timeline observability for agent, tool, API, BrowserOps, Evals, Sandbox, AgentUI, Claws, and CLI activity.
Validate Trace 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.
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
404degraded
trace echo not confirmed
Browserbase Runtime
Protected 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 require PLATPHORM_API_KEY.
Handoff Examples
Trace remains the observability spine; BrowserOps carries trace context and only claims export after confirmation.