Docs

Attributed documentation, ingestion, ranking, scoring, search, clipping, publishing, MCP/API docs, and evidence reports.

Open Docs

Browserbase lane

Validate Docs in BrowserOps

BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Docs's product role.

Preview JSON

Target: https://docs.platphormnews.com
Journey: PlatPhorm Docs 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 passed

Live Public Connectivity

Docs is reachable for public discovery. Use Browserbase-backed runs for browser evidence.

Live JSON

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

200passed

trace echoed

Browserbase Runtime

BrowserOps runs for Docs 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

publish_evidence_report
read_report_status

BrowserOps may receive

docs_report_requested

Transport and Boundary

Preferred transports: openapi, rss, atom, mcp
API docs: https://docs.platphormnews.com/api/docs
MCP status: not advertised
Auth boundary: Public docs are readable; publishing and report mutation use BrowserOps-managed service credentials or service-to-service authorization.

Handoff Examples

browseropstodocsplanned

Docs remains the publishing surface; BrowserOps prepares report evidence and waits for confirmed ingestion.