Spec
Contract validation, diff, repair, and generation for OpenAPI, AsyncAPI, JSON Schema, MCP, webhook, event, policy, and envelope contracts.
Validate Spec in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Spec's product role.
- Target
- https://spec.platphormnews.com
- Journey
- spec 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
Spec 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 Spec 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_contract
- validate_form_contract
- get_contract_diff
BrowserOps may receive
- journey_plan_generated
- contract_acceptance_requested
Transport and Boundary
- Preferred transports
- openapi, mcp, json_schema, asyncapi
- API docs
- https://spec.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public contract reads remain public-safe; journey import and validation use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
Spec remains the contract truth engine; BrowserOps dry-runs the browser plan before browser execution.