generated: '2026-08-06'
method: searched
source: openapi/arkestro-api-v2-openapi.yml
versioning:
  scheme: uri-path
  current: v2
  path_prefix: /api/v2/
  info_version: '2.0'
  spec_url: https://api.arkestro.com/api-docs/v2/openapi.yaml
  docs: https://api.arkestro.com/api-docs
  policy_published: false
  note: >-
    The spec is served from a version-segmented path (/api-docs/v2/openapi.yaml) which
    implies a v1 existed, but /api-docs/v1/openapi.yaml and /api-docs/v3/openapi.yaml both
    return 404 — only v2 is published. No written versioning policy, no statement of how long
    a major version is supported, and no migration guide are public.
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  deprecated_operations: []
  note: >-
    No operation in the published spec carries `deprecated: true`, and no Sunset or
    Deprecation header support is documented. This is an absence of a published policy, not
    evidence that Arkestro never deprecates.
status_page:
  url: https://www.arkestrostatus.com/
  platform: Atlassian Statuspage
  page_id: bvy41y9z9ry2
  aliases:
  - https://arkestro.statuspage.io/
  api: https://www.arkestrostatus.com/api/v2/status.json
  history_feed: https://www.arkestrostatus.com/history.rss
  status_at_probe: All Systems Operational
  components_published: 0
  note: >-
    The status page is live and machine-readable through the standard Statuspage v2 API, but
    it publishes no named components — the page reports an overall indicator only, so a
    consumer cannot tell whether an incident affects the API, the app, or the MCP server.
    Note that status.arkestro.com is a DIFFERENT host that 302s to a sign-in wall; the public
    status page is www.arkestrostatus.com.
sla:
  url: null
  uptime_target: null
  published: false
changelog:
  url: null
  published: false
  note: >-
    No public changelog or release-notes page was found. docs.arkestro.com and
    developer.arkestro.com, the likely homes for one, both 302 to a sign-in wall.
support:
  contact: https://arkestro.com/contact-us/
  legal_contact: legal@arkestro.com
gaps:
- No versioning or deprecation policy published.
- No SLA or uptime target published.
- No public changelog.
- Status page exposes no per-service components.
x-evidence:
- url: https://www.arkestrostatus.com/api/v2/status.json
  http_status: 200
  fetched: '2026-08-06'
  response: '{"page":{"id":"bvy41y9z9ry2","name":"Arkestro",...},"status":{"indicator":"none","description":"All
    Systems Operational"}}'
- url: https://api.arkestro.com/api-docs/v1/openapi.yaml
  http_status: 404
  fetched: '2026-08-06'
- url: https://api.arkestro.com/api-docs/v2/openapi.yaml
  http_status: 200
  fetched: '2026-08-06'
- url: https://docs.arkestro.com/
  http_status: 200
  fetched: '2026-08-06'
  note: redirects to https://docs.arkestro.com/login