generated: '2026-09-02'
method: probed
source: https://upway.co/.well-known/ucp
name: Upway API Lifecycle
description: >-
  Versioning and lifecycle posture for Upway's agent commerce surface, read from the
  live UCP merchant profile served at https://upway.co/.well-known/ucp and from an MCP
  initialize handshake against https://upway.co/api/ucp/mcp. Upway does not publish a
  deprecation policy, an SLA or a status page of its own; what it does publish is a
  version ladder, and that is recorded here with its evidence.
versioning:
  scheme: dated
  format: YYYY-MM-DD
  current: '2026-08-25'
  supported_versions:
  - version: '2026-08-25'
    label: latest stable
    discovery: https://upway-us1.myshopify.com/.well-known/ucp/2026-08-25
    spec: https://ucp.dev/2026-08-25/specification/overview/
  - version: '2026-04-08'
    label: supported
    discovery: https://upway-us1.myshopify.com/.well-known/ucp/2026-04-08
    spec: https://ucp.dev/2026-04-08/specification/overview/
  - version: '2026-01-23'
    label: supported
    discovery: https://upway-us1.myshopify.com/.well-known/ucp/2026-01-23
  negotiation: >-
    Version selection is by URL - each supported version has its own discovery document
    listed in /.well-known/ucp. Three concurrent versions are live, so an agent pinned
    to an older protocol keeps working.
  source: https://upway.co/.well-known/ucp
  also_stated_in: https://upway.co/llms.txt
transport_versioning:
  protocol: Model Context Protocol
  negotiated: '2024-11-05'
  requested_by_probe: '2026-06-18'
  note: >-
    An initialize requesting protocolVersion 2026-06-18 was answered with 2024-11-05,
    so the MCP transport itself sits well behind the UCP application version it carries.
    Probed 2026-09-02; recorded as observed behaviour, not as a published policy.
  server_info:
    name: universal-commerce
    version: 0.1.0
deprecation_policy:
  published: false
  sunset_header: not observed
  deprecation_header: not observed
  rfc8594: false
  note: >-
    No deprecation or sunset policy is published on any Upway host, and neither the
    Deprecation nor the Sunset response header appeared on probed responses. The only
    lifecycle guarantee an integrator can read is the three-version support window in
    the UCP profile, which is a fact about what is currently served rather than a
    commitment about what will be retired or when.
status_page:
  published: false
  url: null
  note: >-
    Upway operates no status page. The storefront and the MCP endpoint run on Shopify
    infrastructure, whose status page (shopifystatus.com) is Shopify's and is not
    claimed here as Upway's.
sla:
  published: false
changelog:
  published: false
  note: >-
    No dated developer changelog or release notes exist on any Upway host. Protocol
    changes surface only as new dated versions appearing in /.well-known/ucp.
deprecated_operations: []
x-evidence:
  fetched: '2026-09-02'
  urls:
  - url: https://upway.co/.well-known/ucp
    status: 200
  - url: https://upway.co/api/ucp/mcp
    status: 200