generated: '2026-08-13'
method: searched
source:
- https://docs.interchange.io/v2/changelog
- https://docs.interchange.io/v2/setup/built-for-agents
- https://docs.interchange.io/v2/setup/migration-guide
- https://docs.scope3.com/docs/getting-started
versioning:
  scheme: uri-path
  current: v2
  interchange_server: https://api.interchange.io/api/v2
  measurement_server: https://api.scope3.com/v2
  ai_server: https://aiapi.scope3.com
  build_version: 5.148.0
  build_version_source: https://api.interchange.io/health
  build_version_checked: '2026-08-13'
  docs:
  - https://docs.interchange.io/v2/authentication#versioning
  - https://docs.scope3.com/docs/getting-started
  pinning_policy: >-
    The Interchange REST URLs are pinned to v2 and will keep serving v2 even after a future
    major version ships. The buyer and storefront-management MCP URLs are unversioned aliases
    that auto-redirect to whatever is currently stable (today v2). A v3 agent surface is
    already documented as a preview.
  preview: https://docs.interchange.io/v2/setup/v3-preview
deprecation:
  policy_url: https://docs.interchange.io/v2/setup/migration-guide
  notes: >-
    Scope3 runs a dated deprecation cadence with published migration guides on both platforms.
    On the measurement side, API 1.3 was scheduled for deprecation on September 30 and earlier
    V1 versions were fully deprecated on January 1, 2025. On Interchange, a v1-to-v2 migration
    guide is published and v2 REST URLs are contractually pinned so a future v3 does not move
    existing callers. Sunset/Deprecation HTTP headers (RFC 8594) are not documented on either
    platform.
  sunset_header: false
  migration_guides:
  - https://docs.interchange.io/v2/setup/migration-guide
  - https://docs.scope3.com/docs/migration-guides.md
  - https://docs.scope3.com/docs/measurement-v1-to-v2.md
  - https://docs.scope3.com/docs/migrating-from-v1-measure-to-v2-measure.md
status_page: null
status_page_note: >-
  No public status page. status.scope3.com and status.interchange.io do not resolve (DNS
  failure, curl exit 6, checked 2026-08-13). The nearest published substitute is the
  unauthenticated health endpoint below, which is a liveness probe rather than an incident
  history, so no StatusPage pointer is emitted.
health_endpoint:
  url: https://api.interchange.io/health
  auth: none
  returns: [status, version, commitSha, inFlightJobs, services, timestamp]
  services_reported: [database, agenticDatabase, mcp, a2a, electric]
  verified: {status: 200, checked: '2026-08-13'}
sla: null
sla_note: No published SLA or uptime target was found on either platform.
changelog:
- https://docs.interchange.io/v2/changelog
- https://docs.scope3.com/changelog
dataset_update_calendar: https://docs.scope3.com/docs/dataset-update-calendar.md
deprecated_operations: []
deprecated_operations_note: >-
  No operation in any of the four published specs carries `deprecated: true`.
release_governance:
  note: >-
    The Interchange changelog documents per-change rollout controls — entitlement gating,
    named kill switches, and explicit "Action:" / "Buyer impact:" statements per entry. Unusual
    rigour for a public changelog and worth recording as lifecycle evidence.
  see: changelog/scope3-changelog.yml