generated: '2026-07-31'
method: searched
source: >-
  https://www.aquant.ai/company/whats-new, https://security.aquant.ai/,
  live probes of aquant.ai / aquant.io hosts and status-page vendors 2026-07-31
versioning:
  scheme: none
  current:
    aquant:mcp-server:
      spec_info_version: 1.0.0
      running_server_version: 1.28.1
      source: 'POST https://mcp.aquant.ai/mcp initialize → result.serverInfo.version'
      mcp_protocol_version: '2025-06-18'
    aquant:acp-voiceai:
      spec_info_version: 0.1.0
      note: FastAPI default; not a meaningful published version.
      sdk_version: 0.1.3
  docs: null
  note: >-
    No version segment in any URL path, no version header, no dated-release train. The MCP
    server's real version (1.28.1) is only discoverable through the MCP initialize handshake —
    it is not reflected in the published OpenAPI, which still says 1.0.0.
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecation_header: false
  deprecated_operations: []
  note: >-
    No operation in either OpenAPI is marked `deprecated: true`. No RFC 8594 Sunset or
    Deprecation header was observed on any probed response. No deprecation policy page exists.
    One in-spec deprecation SIGNAL does exist, in prose rather than metadata — the `tenant_id`
    argument on the parts tools is documented as "[TEMPORARY] The tenant ID. This should be
    removed in the future.", an announced future breaking change with no dated policy behind it.
sla:
  url: null
  uptime_target: null
  note: >-
    A Service-Level Agreement document is listed under Legal in the SafeBase trust center at
    https://security.aquant.ai/ but is access-gated; no public uptime target is published.
  risk_profile:
    source: https://security.aquant.ai/
    recovery_time_objective: 4 hours
    recovery_point_objective: 12 hours
    third_party_dependence: true
status_page:
  url: null
  probed:
  - {url: 'https://status.aquant.ai/', result: no DNS}
  - {url: 'https://status.aquant.io/', result: no DNS}
  - {url: 'https://aquant.statuspage.io/', result: 200 but resolves to Atlassian Statuspage marketing — not an Aquant page}
  note: >-
    Aquant operates no public status page. The trust center lists "Status Monitoring" as an
    internal infrastructure control only. No StatusPage pointer is emitted in apis.yml.
health_endpoints:
- {api: 'aquant:mcp-server', path: /health, operationId: health_check, method: GET}
- {api: 'aquant:acp-voiceai', path: /health/live, operationId: liveness_health_live_get, method: GET, purpose: liveness probe}
- {api: 'aquant:acp-voiceai', path: /health/ready, operationId: readiness_health_ready_get, method: GET, purpose: 'readiness probe — checks DB and Redis before accepting traffic'}
domain_migration:
  from: aquant.io
  to: aquant.ai
  status: aquant.io and docs.aquant.io return HTTP 521 (Cloudflare — origin unreachable)
  probed: '2026-07-31'
  note: >-
    The legacy aquant.io domain is dead, not redirected. Any older documentation or integration
    URL under aquant.io is unrecoverable; the npm scope @aquant-io/ survives from that era.
changelog:
  url: https://www.aquant.ai/company/whats-new
  artifact: changelog/aquant-changelog.yml
  kind: marketing "What's New" page — not a developer changelog
gaps:
- No deprecation policy, no Sunset/Deprecation header support.
- No public status page and no published uptime target.
- No API version in path or header; server version invisible to REST consumers.
- No developer-facing, dated changelog for either API.