AgentUI
Visual workflow orchestration and tool UI rendering.
Validate AgentUI 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
AgentUI 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
404degraded
trace echo not confirmed
Browserbase Runtime
Protected BrowserOps runs for AgentUI 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.
AgentUI Handoff Lane
AgentUI requests browser validation for rendered workflow UI; BrowserOps returns screenshots, accessibility status, labels, navigation state, and trace-linked run evidence.
Capability Mapping
BrowserOps may call
- validate_rendered_tool_ui
- read_workflow_step
- open_originating_workflow
BrowserOps may receive
- browser_validation_requested
- workflow_step_update
Transport and Boundary
- Preferred transports
- mcp, openapi, sse, webhook
- API docs
- https://agentui.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public workflow reads remain public-safe; protected workflow run updates require PLATPHORM_API_KEY.
Handoff Examples
AgentUI remains the workflow UI surface; BrowserOps proves what the browser saw.