SITEBORNEUNIFIED SEMANTIC SYSTEM VCMgoverned release
Status / Current availability

SITEBORNE services are operational.

Current public production services are available. This page reports customer-relevant availability, production interfaces, and independently observed reachability without exposing internal release or control-plane detail.

Production state is runtime-authoritative. Candidate releases and internal qualification work are intentionally excluded from this public status view.

READYruntime 2paid production modes 6MCP tools observed 100%30-day MCP uptime observed

Last public observation: September 24, 2026 UTC. Live runtime metadata remains authoritative for current service availability and pricing.

Independent measurements are supporting observations, not production authority.

RUNTIMEREADYproduction services enabled OPENAPI3.1.0live contract MCP6 TOOLSindependently observed A2A1.0independently observed UPTIME100% · 30DMCPMetrics observation
PRODUCTION

What customers can use now.

Production remains on the current v2 service generation. The runtime and its live OpenAPI document are the source of truth for executable state.

RUNTIMEREADYproduction services enabled
LIVE SERVICE GENERATIONv2current production generation
OPENAPI3.1.0live runtime contract
VERIFY STANDARDLIVEverify_agent_output.v2
VERIFY STANDARD$0.017per request · x402
WEB DIRECTLIVEweb_context_verified.v2
WEB DIRECT$0.008per request · x402
MCP TOOLS OBSERVED6MCPMetrics external measurement
MCP UPTIME · 30D100%MCPMetrics external observation
A2A UPTIME · 30D100%Agenstry external observation
INDEPENDENT OBSERVATION · 2026-09-24 UTC

Public reachability is independently visible.

Third-party observers provide useful corroboration of public availability. Their measurements may use different windows and methods, so SITEBORNE does not treat them as production authority.

Status scope: This page intentionally reports public service health and integration availability. Product roadmap, candidate-release qualification, internal architecture, private scoring, provider routing, and control-plane implementation detail belong in their respective product, developer, or internal governance contexts—not on a customer-facing status page.