Spec
Contract validation, diff, repair, and generation for OpenAPI, AsyncAPI, JSON Schema, MCP, webhook, event, policy, and envelope contracts.
Validate Spec 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
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
404degraded
trace echo not confirmed
Browserbase Runtime
Protected 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 protected validation require PLATPHORM_API_KEY.
Handoff Examples
Spec remains the contract truth engine; BrowserOps dry-runs the browser plan before protected execution.