@adcp/sdk 14.0.0-rc.49 → 14.0.0-rc.50

package/compliance/cache/{3.1.18 → 3.1.24}/universal/get-products-pagination-integrity.yaml

@@ -67,7 +67,7 @@ fixtures:
       publisher_properties:
         - publisher_domain: "acmeoutdoor.example"
       format_ids:
-        - agent_url: "https://compliance.adcontextprotocol.org"
+        - agent_url: "https://compliance.adcontextprotocol.org/"
           id: "get_products_pagination_integrity_display"
     - product_id: "get_products_pagination_product_2"
       name: "Get Products Pagination Test Product 2"
@@ -77,7 +77,7 @@ fixtures:
       publisher_properties:
         - publisher_domain: "acmeoutdoor.example"
       format_ids:
-        - agent_url: "https://compliance.adcontextprotocol.org"
+        - agent_url: "https://compliance.adcontextprotocol.org/"
           id: "get_products_pagination_integrity_display"
   pricing_options:
     - product_id: "get_products_pagination_product_1"
@@ -166,7 +166,7 @@ phases:
             operator: "pinnacle-agency.example"
           filters:
             format_ids:
-              - agent_url: "https://compliance.adcontextprotocol.org"
+              - agent_url: "https://compliance.adcontextprotocol.org/"
                 id: "get_products_pagination_integrity_display"
           pagination:
             max_results: 1
@@ -188,7 +188,7 @@ phases:
           - check: field_contains
             path: "products[0].format_ids[*]"
             value:
-              agent_url: "https://compliance.adcontextprotocol.org"
+              agent_url: "https://compliance.adcontextprotocol.org/"
               id: "get_products_pagination_integrity_display"
             description: "The returned product satisfies the requested test format filter"
           - check: field_absent
@@ -239,7 +239,7 @@ phases:
             operator: "pinnacle-agency.example"
           filters:
             format_ids:
-              - agent_url: "https://compliance.adcontextprotocol.org"
+              - agent_url: "https://compliance.adcontextprotocol.org/"
                 id: "get_products_pagination_integrity_display"
           pagination:
             cursor: "$context.products_next_cursor"
@@ -262,7 +262,7 @@ phases:
           - check: field_contains
             path: "products[0].format_ids[*]"
             value:
-              agent_url: "https://compliance.adcontextprotocol.org"
+              agent_url: "https://compliance.adcontextprotocol.org/"
               id: "get_products_pagination_integrity_display"
             description: "The terminal-page product satisfies the requested test format filter"
           - check: field_absent

package/compliance/cache/{3.1.18 → 3.1.24}/universal/pagination-integrity-creative-formats.yaml

@@ -174,7 +174,7 @@ phases:
           non-terminal. The runner captures `pagination.cursor` for the
           follow-up step.
         task: list_creative_formats
-        schema_ref: "creative/list-creative-formats-request.json"
+        schema_ref: "media-buy/list-creative-formats-request.json"
         response_schema_ref: "creative/list-creative-formats-response.json"
         doc_ref: "/creative/task-reference/list_creative_formats"
         comply_scenario: pagination_integrity
@@ -225,7 +225,7 @@ phases:
           `cursor` field. A cursor on `has_more=false` is a stale token
           that invites callers to follow it past the end of results.
         task: list_creative_formats
-        schema_ref: "creative/list-creative-formats-request.json"
+        schema_ref: "media-buy/list-creative-formats-request.json"
         response_schema_ref: "creative/list-creative-formats-response.json"
         doc_ref: "/creative/task-reference/list_creative_formats"
         comply_scenario: pagination_integrity

package/compliance/cache/{3.1.18 → 3.1.24}/universal/read-tool-idempotency.yaml

@@ -1,18 +1,18 @@
 id: read_tool_idempotency
 version: "1.0.0"
 introduced_in: "3.1"
-title: "Read-tool idempotency_key tolerance"
+title: "Read-tool idempotency_key envelope tolerance"
 category: idempotency
-summary: "Validates that read-only AdCP tasks accept the 3.1 every-request idempotency_key envelope without strict wrapper rejection."
+summary: "Validates that read-only AdCP tasks and the 3.x get_products compatibility facade tolerate an optional idempotency_key without claiming read-response replay."
 track: core
 required_tools: []  # protocol-level baseline; read-tool probes gate themselves per step
 
 narrative: |
-  AdCP 3.1 extends the `idempotency_key` request envelope from mutating
-  operations to every task request, including read-only tools. Sellers MUST
-  tolerate the field on reads in 3.1. Tool wrappers must pass it through their
-  envelope normalization layer instead of rejecting it as an unknown
-  task-specific input.
+  AdCP requires `idempotency_key` replay protection for state-mutating
+  requests. Read-only tools leave the field optional, but their wrappers MUST
+  tolerate it instead of rejecting it as an unknown task-specific input. A
+  pure-read handler MAY ignore the field, and buyers MUST NOT infer a
+  byte-stable replay guarantee from this storyboard.
 
   This storyboard focuses on the 3.1 read-side contract. It sends
   `idempotency_key`, `context`, and `ext` on representative read tools and
@@ -21,11 +21,8 @@ narrative: |
   mutating replay semantics, conflict detection, TTL declaration, and
   `replayed: true`.
 
-  The final phase intentionally omits `idempotency_key` on a read request.
-  During the 3.1 grace window, sellers SHOULD reject this omission but MAY
-  accept it for compatibility; therefore the probe is documented here as a
-  future 3.2 switch point rather than a hard failure. The 3.2 storyboard cut
-  should flip that probe to a required rejection.
+  The final phase intentionally omits `idempotency_key` on a read request to
+  verify that optional-key requests remain valid.
 
 agent:
   interaction_model: "*"  # applies to every agent regardless of protocol or specialism
@@ -46,7 +43,7 @@ phases:
   - id: read_requests_accept_idempotency_key
     title: "Read requests accept idempotency_key"
     narrative: |
-      Send representative read requests with the full 3.1 request envelope:
+      Send representative read requests with optional envelope fields:
       `idempotency_key`, `context`, and `ext`. Passing these probes confirms
       that task wrappers do not treat read request schemas as closed
       task-specific payloads.
@@ -67,7 +64,8 @@ phases:
         stateful: false
         expected: |
           Return capabilities normally. The read wrapper MUST tolerate the
-          3.1 every-request envelope fields and echo context unchanged.
+          optional envelope fields and echo context unchanged. This step does
+          not require the response to be stored or replayed.
 
         sample_request:
           idempotency_key: "$generate:uuid_v4#read_tools_3_1_capabilities"
@@ -94,9 +92,10 @@ phases:
       - id: get_products_with_idempotency_key
         title: "Product discovery read accepts idempotency_key"
         narrative: |
-          `get_products` is the canonical media-buy read. Sellers that expose
-          it must accept the 3.1 every-request envelope even though the field is
-          not part of the task-specific product-discovery payload.
+          This brief-mode `get_products` probe resolves synchronously as a read,
+          but the compatibility tool is polymorphic: other calls may create a
+          task or finalize a proposal. Its request schema therefore declares an
+          optional `idempotency_key`; this read arm may ignore it.
         task: get_products
         requires_tool: get_products
         schema_ref: "media-buy/get-products-request.json"
@@ -268,27 +267,19 @@ phases:
             value: "read_tool_idempotency--list_creatives_with_key"
             description: "Context correlation_id returned unchanged"
 
-  - id: omitted_key_grace_accept_path
-    title: "3.1 omitted-key grace window — accept path"
+  - id: omitted_key_optional
+    title: "Read request without idempotency_key succeeds"
     narrative: |
-      Exercise the intentional omission vector on a read request. 3.1 sellers
-      SHOULD reject omitted `idempotency_key` values on reads but MAY continue
-      to accept them during the migration window. Passing this path records the
-      compatibility behavior without failing 3.1 acceptance; the peer reject
-      path below records the recommended behavior.
-    optional: true
-    branch_set:
-      id: omitted_key_grace_handled
-      semantics: any_of
+      Exercise the intentional omission vector on a pure read. The optional
+      key must not be required for this request shape.
 
     steps:
-      - id: get_capabilities_without_idempotency_key_3_1_accept
-        title: "Capabilities read without idempotency_key may still succeed in 3.1"
+      - id: get_capabilities_without_idempotency_key
+        title: "Capabilities read without idempotency_key succeeds"
         narrative: |
           The request intentionally omits `idempotency_key` and sets
-          `omit_idempotency_key: true` so future runners that auto-inject keys
-          for all tasks preserve the missing-key vector. Some 3.1 sellers may
-          still accept this request during migration.
+          `omit_idempotency_key: true` so runners preserve the missing-key
+          vector.
         task: get_adcp_capabilities
         schema_ref: "protocol/get-adcp-capabilities-request.json"
         response_schema_ref: "protocol/get-adcp-capabilities-response.json"
@@ -296,110 +287,24 @@ phases:
         comply_scenario: read_tool_idempotency
         omit_idempotency_key: true
         stateful: false
-        contributes: true
         expected: |
-          3.1 grace-window accept behavior: a seller MAY accept this request
-          and return capabilities normally, but SHOULD prepare to reject omitted
-          `idempotency_key` on read tools. The 3.2 compliance cut should remove
-          this accept branch.
+          Return capabilities normally. `idempotency_key` is optional for this
+          pure-read request.
 
         sample_request:
           context:
-            correlation_id: "read_tool_idempotency--capabilities_omitted_key_grace"
+            correlation_id: "read_tool_idempotency--capabilities_without_key"
           ext:
             adcp:
               storyboard: "read_tool_idempotency"
-              probe: "omitted_key_grace"
+              probe: "optional_key_omitted"
         validations:
           - check: response_schema
-            description: "Response matches get-adcp-capabilities-response.json schema during the 3.1 omitted-key grace window"
+            description: "Response matches get-adcp-capabilities-response.json schema without an idempotency key"
           - check: field_present
             path: "context"
             description: "Response echoes back the context object"
           - check: field_value
             path: "context.correlation_id"
-            value: "read_tool_idempotency--capabilities_omitted_key_grace"
+            value: "read_tool_idempotency--capabilities_without_key"
             description: "Context correlation_id returned unchanged"
-
-  - id: omitted_key_grace_reject_path
-    title: "3.1 omitted-key grace window — reject path"
-    narrative: |
-      Exercise the recommended 3.1 behavior for a read request that omits
-      `idempotency_key`: reject the request with `INVALID_REQUEST`. Passing
-      this path contributes the same branch-set flag as the accept path above,
-      so either behavior is conformant during the 3.1 migration window.
-    optional: true
-    branch_set:
-      id: omitted_key_grace_handled
-      semantics: any_of
-
-    steps:
-      - id: get_capabilities_without_idempotency_key_3_1_reject
-        title: "Capabilities read without idempotency_key may reject in 3.1"
-        narrative: |
-          The request intentionally omits `idempotency_key` and sets
-          `omit_idempotency_key: true`. In 3.1, sellers that already enforce
-          the every-request envelope should reject this with `INVALID_REQUEST`.
-          In 3.2 this becomes the only conformant branch.
-        task: get_adcp_capabilities
-        schema_ref: "protocol/get-adcp-capabilities-request.json"
-        response_schema_ref: "protocol/get-adcp-capabilities-response.json"
-        doc_ref: "/protocol/get_adcp_capabilities"
-        comply_scenario: read_tool_idempotency
-        omit_idempotency_key: true
-        expect_error: true
-        negative_path: payload_well_formed
-        stateful: false
-        contributes: true
-        expected: |
-          3.1 grace-window reject behavior: reject the read request with:
-          - Error code: INVALID_REQUEST
-          - Message indicating idempotency_key is required
-
-        sample_request:
-          context:
-            correlation_id: "read_tool_idempotency--capabilities_omitted_key_grace"
-          ext:
-            adcp:
-              storyboard: "read_tool_idempotency"
-              probe: "omitted_key_grace"
-        validations:
-          - check: error_code
-            value: "INVALID_REQUEST"
-            description: "Missing idempotency_key rejected with INVALID_REQUEST"
-          - check: field_present
-            path: "context"
-            description: "Response echoes back the context object"
-          - check: field_value
-            path: "context.correlation_id"
-            value: "read_tool_idempotency--capabilities_omitted_key_grace"
-            description: "Context correlation_id returned unchanged"
-
-  - id: omitted_key_grace_assertion
-    title: "3.1 omitted-key grace window — require handled outcome"
-    narrative: |
-      Synthetic assertion over the two optional omitted-key branches. In 3.1,
-      either success-path compatibility or recommended `INVALID_REQUEST`
-      rejection satisfies the migration window. A transport failure, unrelated
-      error, or schema-invalid success satisfies neither branch and is
-      non-conformant. The 3.2 storyboard cut should collapse this to the
-      rejection branch only.
-
-    steps:
-      - id: assert_omitted_key_grace_handled
-        title: "Require omitted_key_grace_handled from either path"
-        narrative: |
-          At least one omitted-key branch must pass: the 3.1 compatibility
-          accept path or the 3.1 recommended reject path.
-        task: assert_contribution
-        comply_scenario: read_tool_idempotency
-        stateful: false
-        expected: |
-          At least one of omitted_key_grace_accept_path or
-          omitted_key_grace_reject_path contributed
-          `omitted_key_grace_handled`.
-
-        validations:
-          - check: any_of
-            allowed_values: ["omitted_key_grace_handled"]
-            description: "Agent must either accept the omitted-key read during the 3.1 grace window or reject it with INVALID_REQUEST."

package/compliance/cache/{3.1.18 → 3.1.24}/universal/storyboard-schema.yaml

@@ -139,6 +139,14 @@
 #   rule above), not a schema concern — the same storyboard runs against
 #   different topologies.)
 #
+# Applicability order: storyboard-level `requires_capability` predicates MUST
+#   be evaluated before the runner evaluates `requires`. When the capability
+#   predicate is not satisfied, the runner emits `not_applicable` and MUST NOT
+#   report a missing runtime requirement. Only an agent that selected the
+#   storyboard by satisfying its authored capability predicate can receive
+#   `requirement_unmet`. This keeps optional capability storyboards out of the
+#   coverage totals of agents that never claimed the capability.
+#
 # requires: string[] (optional — storyboard-level runtime requirement gate.
 #   Known values: controller | seeded_state | real_wire | webhook_receiver | multi_agent (forward-compat:
 #   unrecognized values are NOT schema violations — runners emit
@@ -691,9 +699,9 @@
 #   `skipIdempotencyAutoInject` so the request reaches the agent WITHOUT an
 #   `idempotency_key`. Use for missing-key rejection vectors — without this flag
 #   the SDK may auto-inject a key and the agent never sees the missing-key path.
-#   3.0 used this only for mutating tasks. 3.1 extends `idempotency_key` to every
-#   request, so read-tool omission probes SHOULD also set this flag to prevent
-#   current or future runner/client auto-injection from masking the vector.)
+#   Read tools leave the key optional, so omission probes SHOULD also set this
+#   flag to prevent current or future runner/client auto-injection from masking
+#   the vector. Supplying a key on a pure read does not by itself require replay.)
 #
 # contributes_to: string (optional — marks this step as contributing a named flag
 #                         that a later assert_contribution step can require)

package/dist/lib/schemas-data/3.1/a2ui/bound-value.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/a2ui/bound-value.json",
+  "$id": "/schemas/3.1.24/a2ui/bound-value.json",
   "title": "A2UI Bound Value",
   "description": "A value that can be a literal or bound to a path in the data model",
   "oneOf": [

package/dist/lib/schemas-data/3.1/a2ui/component.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/a2ui/component.json",
+  "$id": "/schemas/3.1.24/a2ui/component.json",
   "title": "A2UI Component",
   "description": "A component in an A2UI surface",
   "type": "object",

package/dist/lib/schemas-data/3.1/a2ui/si-catalog.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/a2ui/si-catalog.json",
+  "$id": "/schemas/3.1.24/a2ui/si-catalog.json",
   "title": "SI Component Catalog",
   "description": "A2UI component catalog for Sponsored Intelligence",
   "definitions": {
@@ -9,7 +9,7 @@
       "description": "Text display component",
       "properties": {
         "text": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Text content to display"
         },
         "variant": {
@@ -32,7 +32,7 @@
       "description": "Interactive button component",
       "properties": {
         "label": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Button label text"
         },
         "action": {
@@ -47,7 +47,7 @@
               "type": "object",
               "description": "Context data to include with action",
               "additionalProperties": {
-                "$ref": "/schemas/3.1.18/a2ui/bound-value.json"
+                "$ref": "/schemas/3.1.24/a2ui/bound-value.json"
               }
             }
           },
@@ -65,7 +65,7 @@
           "default": "primary"
         },
         "disabled": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json"
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json"
         }
       },
       "required": [
@@ -78,11 +78,11 @@
       "description": "Hyperlink component",
       "properties": {
         "label": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Link text"
         },
         "url": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "URL to navigate to"
         },
         "external": {
@@ -101,11 +101,11 @@
       "description": "Image display component",
       "properties": {
         "src": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Image source URL"
         },
         "alt": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Alt text for accessibility"
         },
         "width": {
@@ -127,19 +127,19 @@
       "description": "Card container for grouped content",
       "properties": {
         "title": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Card title"
         },
         "subtitle": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Card subtitle"
         },
         "image": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Card image URL"
         },
         "badge": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Badge text (e.g., 'New', 'Sale')"
         },
         "action": {
@@ -152,7 +152,7 @@
             "context": {
               "type": "object",
               "additionalProperties": {
-                "$ref": "/schemas/3.1.18/a2ui/bound-value.json"
+                "$ref": "/schemas/3.1.24/a2ui/bound-value.json"
               }
             }
           },
@@ -177,27 +177,27 @@
       "description": "Product display card (SI-specific)",
       "properties": {
         "title": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Product name"
         },
         "price": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Price display string"
         },
         "image": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Product image URL"
         },
         "description": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Product description"
         },
         "badge": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Badge text (e.g., 'Best Seller')"
         },
         "ctaLabel": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "CTA button label"
         },
         "action": {
@@ -209,7 +209,7 @@
             "context": {
               "type": "object",
               "additionalProperties": {
-                "$ref": "/schemas/3.1.18/a2ui/bound-value.json"
+                "$ref": "/schemas/3.1.24/a2ui/bound-value.json"
               }
             }
           },
@@ -228,7 +228,7 @@
       "description": "Data-bound list component",
       "properties": {
         "items": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Path to array in data model"
         },
         "template": {
@@ -245,7 +245,7 @@
           ]
         },
         "emptyMessage": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Message to show when list is empty"
         },
         "layout": {
@@ -349,11 +349,11 @@
           "description": "Integration type"
         },
         "label": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Button label"
         },
         "url": {
-          "$ref": "/schemas/3.1.18/a2ui/bound-value.json",
+          "$ref": "/schemas/3.1.24/a2ui/bound-value.json",
           "description": "Integration endpoint URL"
         },
         "highlighted": {

package/dist/lib/schemas-data/3.1/a2ui/surface.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/a2ui/surface.json",
+  "$id": "/schemas/3.1.24/a2ui/surface.json",
   "title": "A2UI Surface",
   "description": "A contiguous UI region containing components",
   "type": "object",
@@ -18,7 +18,7 @@
       "type": "array",
       "description": "Flat list of components (adjacency list structure)",
       "items": {
-        "$ref": "/schemas/3.1.18/a2ui/component.json"
+        "$ref": "/schemas/3.1.24/a2ui/component.json"
       }
     },
     "rootId": {

package/dist/lib/schemas-data/3.1/a2ui/user-action.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/a2ui/user-action.json",
+  "$id": "/schemas/3.1.24/a2ui/user-action.json",
   "title": "A2UI User Action",
   "description": "User interaction event sent from client to agent",
   "type": "object",

package/dist/lib/schemas-data/3.1/aao/agent-publishers.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/aao/agent-publishers.json",
+  "$id": "/schemas/3.1.24/aao/agent-publishers.json",
   "title": "AAO Directory: Agent → Publishers Inverse Lookup Response",
   "description": "Response envelope for `GET /v1/agents/{agent_url}/publishers` against an AAO-compatible directory. Returns the set of publishers whose adagents.json authorizes the given agent_url, with provenance (discovery_method, manager_domain), per-publisher property counts, and lifecycle status. The publisher's own adagents.json remains the trust root; this endpoint is discovery, not authorization. Each `publisher_domain` row tells the operator which publishers to verify directly via the SDK's per-domain primitives.",
   "type": "object",

package/dist/lib/schemas-data/3.1/account/get-account-financials-request.json

@@ -1,28 +1,28 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.18/account/get-account-financials-request.json",
+  "$id": "/schemas/3.1.24/account/get-account-financials-request.json",
   "title": "Get Account Financials Request",
   "description": "Request financial status for an operator-billed account. Returns spend summary, credit/balance status, and invoice history. Only applicable when the seller declares account_financials capability.",
   "type": "object",
   "allOf": [
     {
-      "$ref": "/schemas/3.1.18/core/version-envelope.json"
+      "$ref": "/schemas/3.1.24/core/version-envelope.json"
     }
   ],
   "properties": {
     "account": {
-      "$ref": "/schemas/3.1.18/core/account-ref.json",
+      "$ref": "/schemas/3.1.24/core/account-ref.json",
       "description": "Account to query financials for. Must be an operator-billed account."
     },
     "period": {
-      "$ref": "/schemas/3.1.18/core/date-range.json",
+      "$ref": "/schemas/3.1.24/core/date-range.json",
       "description": "Date range for the spend summary. Defaults to the current billing cycle if omitted."
     },
     "context": {
-      "$ref": "/schemas/3.1.18/core/context.json"
+      "$ref": "/schemas/3.1.24/core/context.json"
     },
     "ext": {
-      "$ref": "/schemas/3.1.18/core/ext.json"
+      "$ref": "/schemas/3.1.24/core/ext.json"
     }
   },
   "required": [