generated: '2026-08-02'
method: searched
source: https://smithrx.com/ (sitemap.xml, 319 URLs), https://smithrx.com/system-maintenance
summary: SmithRx publishes no API versioning policy, deprecation policy, SLA or status
  page, because it publishes no public API. What exists is a static maintenance-notice
  page and a partner-portal release narrative on the company blog.
versioning:
  scheme: null
  current: null
  docs: null
  note: No public API, therefore no published versioning scheme. The partner portal
    is marketed by generation ("Partner Portal 2.0") rather than by API version.
deprecation:
  policy_url: null
  sunset_header: unknown
  note: No RFC 8594 Sunset/Deprecation policy published.
sla:
  url: null
  uptime_target: null
status_page:
  url: null
  probed:
  - host: status.smithrx.com
    result: does not resolve
  - host: status.mysmithrx.com
    result: does not resolve
  - host: smithrx.statuspage.io
    result: redirects to atlassian.com marketing — not a claimed Statuspage
  note: No status page, component status, incident history or uptime feed exists. NOT
    wired as a StatusPage pointer.
maintenance_notice:
  url: https://smithrx.com/system-maintenance
  kind: static advisory page
  copy: 'System Maintenance in progress — "We''re making some upgrades so our systems
    work better for you. We''ll be back online once the maintenance is completed."'
  note: A static holding page shown during planned downtime. It carries no schedule,
    no components and no incident history, so it is recorded here but deliberately
    NOT treated as a status page.
release_communication:
- channel: Company blog
  url: https://smithrx.com/blog
  note: Product changes are announced as narrative blog posts (e.g. "The Partner Portal
    2.0 — Enhanced PBM Tools for Brokers", "Introducing the Prior Authorization Status
    Feature") rather than in a dated, structured changelog.
- channel: Newsroom
  url: https://smithrx.com/news
deprecated_operations: []
gaps:
- No status page or uptime transparency for the member/partner portals.
- No dated, structured changelog — product release notes are blog posts only.
- No deprecation or versioning policy (moot until an API is published).