generated: '2026-09-19'
method: searched
source: https://aicomglobal.com/changelog
derived_from: openapi/aicomglobal-com-openapi.json
docs:
- https://aicomglobal.com/status
- https://aicomglobal.com/terms
- https://aicomglobal.com/about
versioning:
  scheme: unversioned paths; a single semantic version carried by the server, the MCP serverInfo and the agent card
  current_version: 0.15.0 (MCP serverInfo.version, agent card version, GET /status version) / 1.0.0 (OpenAPI info.version) / 1.0.1 (toolkit `version` in the /svc envelope)
  spec_url: https://aicomglobal.com/openapi.json
  base_url: https://aicomglobal.com
  policy_published: false
  note: >-
    Paths carry no version segment. The service version 0.15.0 is consistent across MCP, A2A and /status, and
    each changelog entry is stamped with it; the OpenAPI document and the toolkit carry their own version
    numbers. The Terms of Service and Privacy Policy are dated (last updated 2026-06-24) rather than
    numbered. No versioning or breaking-change policy is published; the changelog's own convention is to
    state "No money-path change; capabilities/paid actions unchanged" on entries that alter nothing an agent
    pays for.
deprecation:
  policy_published: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  deprecated_operations: []
  documented_retirements: []
  note: >-
    Zero of 24 operations carry deprecated: true; no Sunset or Deprecation header was observed on any
    response; no deprecation policy page exists. The changelog records one pricing-phase promise rather than
    a retirement — experiment publishing is "$0 founding -> $0.25 USDC" — with no date for the phase change.
    No Deprecation pointer is emitted.
status_page:
  url: https://aicomglobal.com/status
  format: application/json (machine-readable; no HTML status page, no history, no subscriptions)
  probed: [{url: 'https://aicomglobal.com/status', status: 200, fetched: '2026-09-19'}]
  observed:
    allOk: true
    version: 0.15.0
    uptimeHuman: 2d 8h
    startedAt: '2026-09-17T16:04:26.020Z'
    components:
    - 'Web + REST + MCP + A2A — ok (serving this request)'
    - 'Toolkit self-checks (78 services) — ok (in-process contract-stability checks every ~30 min)'
    - 'Subjects failing now (fleet-wide) — ok (0 of 124 tracked subjects in a fail-streak)'
    - 'The Annal (permanent record) — ok (intact — 4 reflections, unbroken hash-chain)'
    - 'x402 Bazaar snapshot — ok (captured 2026-09-19 22:04 UTC)'
    - 'x402 rail (USDC per-call payments) — ok (live · network base)'
    - 'Stripe rail (subscriptions + verification) — ok (live)'
  note: >-
    A live, component-level self-reported status document with a process uptime counter — enough to emit a
    StatusPage pointer, with the caveat that it is generated by the same process it reports on (an outage
    takes the status endpoint down with it), carries no incident history and no uptime SLA. The Commons
    Beacon (/.well-known/aicom-beacon) is a second, signed, hourly liveness datum over the fleet the provider
    measures, not over itself.
sla:
  published: false
  note: >-
    No uptime target. The Terms commit to remedy timelines instead: re-delivery or full refund within 14 days
    of a settled x402 payment whose artifact was not delivered; Reliability Watch refunds pro-rata for any
    period the provider failed to monitor a paid subject; 14-day no-questions refund on verification and new
    Watch subscriptions.
changelog:
  published: true
  url: https://aicomglobal.com/changelog
  format: 'application/json {entries[]: {title, items[]}} — also linked as HTML from every page footer'
  artifact: changelog/aicomglobal-com-changelog.yml
  entries: 18
  first_entry: '2026-06-15 — The Oasis founded'
  latest_entry: '2026-07-04 — v0.15.0 · the measured referral loop'
  note: >-
    Dated, versioned and detailed (v0.9.15 through v0.15.0 carry 3-7 items each, naming files, headers and
    behaviours changed). The last entry is 2026-07-04 while the live server still reports 0.15.0 on
    2026-09-19, so the surface has been stable — or unlogged — for eleven weeks. The npm bridge (1.0.1,
    2026-07-03) and MCP-registry entry (0.9.16, 2026-07-03) date from the same burst.
key_lifecycle:
  signing_key: https://aicomglobal.com/.well-known/aicom-pubkey
  current_kid: 8ad71ce94418677d
  valid_from: '2026-06-16T18:42:13.589Z'
  rotation_policy: >-
    Per /about — key history served publicly, artifacts bind a content-hash of the public key (kid) into their
    signed bytes, verification resolves an artifact's own kid so rotation is non-destructive; on suspected
    compromise the key is rotated immediately, the event is recorded in the key history and the changelog,
    and artifacts signed in the suspect window are re-issued free on request.