@adcp/sdk 13.1.2 → 13.1.4

package/dist/lib/schemas-data/3.1/core/placement.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/placement.json",
+  "$id": "/schemas/3.1.30/core/placement.json",
   "title": "Placement",
   "description": "Represents a specific public ad placement within a product's inventory. Placement IDs are scoped by publisher domain, matching placement definitions in that publisher's adagents.json. `kind` is the structural discriminator: `publisher_ref` means this product placement is a reference to `{publisher_domain, placement_id}`; `seller_inline` means the seller is defining public buyer-facing placement metadata inline. The schema accepts either `name` or `publisher_domain` because publisher-referenced placements can omit `name` only when the publisher declaration supplies it; seller-inline placements carry `name` directly. Whether a reference was resolved from publisher-hosted adagents.json or a community-maintained fallback is resolver metadata, not placement structure. Buyers reference placements in creative assignments with structured PlacementRef objects (`publisher_domain` + `placement_id`) when a product spans multiple publishers or the namespace is otherwise ambiguous. Reusing a registered placement preserves the registry's semantic identity; product-level placement objects may narrow format_ids/format_options or add operational detail, but SHOULD NOT redefine the placement's meaning incompatibly.",
   "type": "object",
@@ -51,7 +51,7 @@
       "type": "array",
       "description": "Format IDs supported by this specific placement. Can include: (1) concrete format_ids (fixed dimensions), (2) template format_ids without parameters (accepts any dimensions/duration), or (3) parameterized format_ids (specific dimension/duration constraints). When present on a product placement, this field narrows the product-level `format_ids` contract for this placement and MUST NOT introduce formats the product does not accept.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/format-id.json"
+        "$ref": "/schemas/3.1.30/core/format-id.json"
       },
       "minItems": 1
     },
@@ -59,7 +59,7 @@
       "type": "array",
       "description": "3.1+ canonical format-option declarations supported by this specific product placement. When present, this field narrows the product-level `format_options` contract for this placement and MUST NOT introduce formats the product does not accept. Buyers compute the effective accepted formats for a placement as the intersection of product-level and placement-level declarations; placements without a format declaration inherit the product-level formats.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/product-format-declaration.json"
+        "$ref": "/schemas/3.1.30/core/product-format-declaration.json"
       },
       "minItems": 1
     },
@@ -67,7 +67,7 @@
       "type": "array",
       "description": "Declared video placement types for this product placement, using IAB Tech Lab/OpenRTB 2.6 video.plcmt definitions with AdCP-native names. Most concrete placements SHOULD declare a single value; aggregate placements MAY declare multiple values. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/video-placement-type.json"
+        "$ref": "/schemas/3.1.30/enums/video-placement-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -76,7 +76,7 @@
       "type": "array",
       "description": "Declared audio distribution types for this product placement, using IAB Tech Lab/OpenRTB 2.6 audio.feed definitions with AdCP-native names. Most concrete placements SHOULD declare a single value; aggregate placements MAY declare multiple values. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/audio-distribution-type.json"
+        "$ref": "/schemas/3.1.30/enums/audio-distribution-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -85,7 +85,7 @@
       "type": "array",
       "description": "Declared sponsored-placement types for this product placement, distinguishing where the catalog-driven retail-media placement renders on the retailer surface. Most concrete placements SHOULD declare a single value; aggregate placements MAY declare multiple values. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/sponsored-placement-type.json"
+        "$ref": "/schemas/3.1.30/enums/sponsored-placement-type.json"
       },
       "uniqueItems": true,
       "minItems": 1
@@ -94,7 +94,7 @@
       "type": "array",
       "description": "Declared social-placement surfaces for this product placement, distinguishing the in-app surface where the social placement renders. Most concrete placements SHOULD declare a single value; aggregate placements MAY declare multiple values. This is seller-declared discovery metadata, not independent verification of inventory quality or delivery context.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/social-placement-surface.json"
+        "$ref": "/schemas/3.1.30/enums/social-placement-surface.json"
       },
       "uniqueItems": true,
       "minItems": 1

package/dist/lib/schemas-data/3.1/core/planned-delivery.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/planned-delivery.json",
+  "$id": "/schemas/3.1.30/core/planned-delivery.json",
   "title": "Planned Delivery",
   "description": "The seller's interpreted delivery parameters for a media buy. Represents what the seller will actually run, which may differ from what the buyer requested (e.g., the seller may apply additional targeting, frequency caps, or adjust geo to match their inventory). Used for authorization verification and audit.",
   "type": "object",
@@ -29,7 +29,7 @@
     "channels": {
       "type": "array",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/channels.json"
+        "$ref": "/schemas/3.1.30/enums/channels.json"
       },
       "description": "Channels the seller will deliver on."
     },
@@ -44,7 +44,7 @@
       "description": "Actual flight end the seller will use."
     },
     "frequency_cap": {
-      "$ref": "/schemas/3.1.24/core/frequency-cap.json",
+      "$ref": "/schemas/3.1.30/core/frequency-cap.json",
       "description": "Frequency cap the seller will apply."
     },
     "audience_summary": {
@@ -55,7 +55,7 @@
       "type": "array",
       "description": "Structured audience targeting the seller will activate. Each entry is either a signal reference or a descriptive criterion. When present, governance agents MUST use this for bias/fairness validation and SHOULD ignore audience_summary for validation purposes. The audience_summary field is a human-readable rendering of this array, not an independent declaration.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/audience-selector.json"
+        "$ref": "/schemas/3.1.30/core/audience-selector.json"
       },
       "minItems": 1
     },
@@ -77,7 +77,7 @@
       }
     },
     "ext": {
-      "$ref": "/schemas/3.1.24/core/ext.json"
+      "$ref": "/schemas/3.1.30/core/ext.json"
     }
   },
   "additionalProperties": true

package/dist/lib/schemas-data/3.1/core/platform-extension-ref.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/platform-extension-ref.json",
+  "$id": "/schemas/3.1.30/core/platform-extension-ref.json",
   "title": "Platform Extension Reference",
   "description": "Reference to a platform extension definition. The agent that owns the URI is authoritative for the extension's schema. Buyers fetch the definition once per content digest and cache it. Platform extensions are typically bundled in `get_products` responses under an `extensions` map keyed by `uri@digest`, eliminating the need for a separate fetch.\n\n**Within a single response**, multiple references to the same `uri` MUST carry the same `digest` — divergent digests in one response indicate producer-side error (e.g., concurrent extension revision mid-render). Buyers encountering divergent digests for the same URI MUST fail closed: treat all references to that URI as unresolved and surface a validation error rather than picking one branch silently. **Across responses**, digest divergence is normal — extension authors revise their schemas, the new digest differs, the cache key changes, and the buyer refetches. Cache by `uri@digest`, not by `uri` alone.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/postal-area-support.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/postal-area-support.json",
+  "$id": "/schemas/3.1.30/core/postal-area-support.json",
   "title": "Postal Area Support",
   "description": "Declares supported postal area systems. Native support is keyed by ISO 3166-1 alpha-2 country with arrays of country-local postal systems. Deprecated country-fused boolean aliases may be included during migration.",
   "type": "object",
@@ -153,7 +153,7 @@
         "pattern": "^[A-Z]{2}$"
       },
       {
-        "$ref": "/schemas/3.1.24/enums/legacy-postal-system.json"
+        "$ref": "/schemas/3.1.30/enums/legacy-postal-system.json"
       }
     ]
   },

package/dist/lib/schemas-data/3.1/core/postal-area.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/postal-area.json",
+  "$id": "/schemas/3.1.30/core/postal-area.json",
   "title": "Postal Area",
   "description": "Postal area values. Prefer the native country + postal system form. Deprecated legacy country-fused postal-system tokens remain accepted for compatibility.",
   "anyOf": [
@@ -9,7 +9,7 @@
       "type": "object",
       "allOf": [
         {
-          "$ref": "/schemas/3.1.24/core/postal-country-system.json"
+          "$ref": "/schemas/3.1.30/core/postal-country-system.json"
         }
       ],
       "properties": {
@@ -19,7 +19,7 @@
           "description": "ISO 3166-1 alpha-2 country code for the postal values."
         },
         "system": {
-          "$ref": "/schemas/3.1.24/enums/postal-system.json",
+          "$ref": "/schemas/3.1.30/enums/postal-system.json",
           "description": "Country-local postal code system (e.g., 'zip', 'outward', 'plz', 'postal_code')."
         },
         "values": {
@@ -44,7 +44,7 @@
       "type": "object",
       "properties": {
         "system": {
-          "$ref": "/schemas/3.1.24/enums/legacy-postal-system.json",
+          "$ref": "/schemas/3.1.30/enums/legacy-postal-system.json",
           "description": "Deprecated country-fused postal code system (e.g., 'us_zip', 'gb_outward'). Prefer country + postal-system."
         },
         "values": {

package/dist/lib/schemas-data/3.1/core/postal-country-system.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/postal-country-system.json",
+  "$id": "/schemas/3.1.30/core/postal-country-system.json",
   "title": "Postal Country System",
   "description": "Valid country-local postal system pairing. Registered countries only accept their registered local systems; countries without a registered local system use postal_code or custom.",
   "type": "object",
@@ -11,7 +11,7 @@
       "description": "ISO 3166-1 alpha-2 country code."
     },
     "system": {
-      "$ref": "/schemas/3.1.24/enums/postal-system.json",
+      "$ref": "/schemas/3.1.30/enums/postal-system.json",
       "description": "Country-local postal code system."
     }
   },

package/dist/lib/schemas-data/3.1/core/price.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/price.json",
+  "$id": "/schemas/3.1.30/core/price.json",
   "title": "Price",
   "description": "A monetary amount with currency and optional billing period. Used across catalog item types for product prices, nightly hotel rates, salary ranges, rental costs, and similar monetary values.",
   "type": "object",

package/dist/lib/schemas-data/3.1/core/pricing-option.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/pricing-option.json",
+  "$id": "/schemas/3.1.30/core/pricing-option.json",
   "title": "Pricing Option",
   "description": "A pricing model option offered by a publisher for a product. Discriminated by pricing_model field. If fixed_price is present, it's fixed pricing. If absent, it's auction-based (floor_price and price_guidance optional). Bid-based auction models may also include max_bid as a boolean signal to interpret bid_price as a buyer ceiling instead of an exact honored price.",
   "discriminator": {
@@ -8,31 +8,31 @@
   },
   "oneOf": [
     {
-      "$ref": "/schemas/3.1.24/pricing-options/cpm-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/cpm-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/vcpm-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/vcpm-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/cpc-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/cpc-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/cpcv-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/cpcv-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/cpv-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/cpv-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/cpp-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/cpp-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/cpa-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/cpa-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/flat-rate-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/flat-rate-option.json"
     },
     {
-      "$ref": "/schemas/3.1.24/pricing-options/time-option.json"
+      "$ref": "/schemas/3.1.30/pricing-options/time-option.json"
     }
   ]
 }

package/dist/lib/schemas-data/3.1/core/product-allocation.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/product-allocation.json",
+  "$id": "/schemas/3.1.30/core/product-allocation.json",
   "title": "Product Allocation",
   "description": "A budget allocation for a specific product within a proposal. Percentages across all allocations in a proposal should sum to 100.",
   "type": "object",
@@ -49,16 +49,16 @@
       "type": "array",
       "description": "Recommended time windows for this allocation in spot-plan proposals.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/daypart-target.json"
+        "$ref": "/schemas/3.1.30/core/daypart-target.json"
       },
       "minItems": 1
     },
     "forecast": {
-      "$ref": "/schemas/3.1.24/core/delivery-forecast.json",
+      "$ref": "/schemas/3.1.30/core/delivery-forecast.json",
       "description": "Forecasted delivery metrics for this allocation"
     },
     "ext": {
-      "$ref": "/schemas/3.1.24/core/ext.json"
+      "$ref": "/schemas/3.1.30/core/ext.json"
     }
   },
   "required": [

package/dist/lib/schemas-data/3.1/core/product-allowed-action.json

@@ -1,19 +1,19 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/product-allowed-action.json",
+  "$id": "/schemas/3.1.30/core/product-allowed-action.json",
   "title": "Product Allowed Action",
   "description": "An action a seller declares as allowed on buys created against this product, scoped to the buy statuses where the action is permitted and the modes available. Advisory template only — the authoritative per-buy resolution lives in `available_actions[]` on the buy response (which may diverge from the product template based on negotiated terms, account tier, or buy-level overrides). The containing `allowed_actions[]` array is uniquely keyed by `action`; sellers MUST NOT emit two entries with the same `action` value. JSON Schema `uniqueItems` only catches structurally identical objects, so validators MUST enforce action-uniqueness separately.",
   "type": "object",
   "properties": {
     "action": {
-      "$ref": "/schemas/3.1.24/enums/media-buy-valid-action.json",
+      "$ref": "/schemas/3.1.30/enums/media-buy-valid-action.json",
       "description": "The action identifier."
     },
     "modes": {
       "type": "array",
       "description": "Modes available for this action on this product. A product may declare multiple modes (for example `self_serve` within tolerances, escalating to `requires_approval` outside) — the buy-side `available_actions[<action>].mode` resolves to the singular mode in effect at mutation time. SDKs that see multiple modes MUST NOT assume which one will fire; they must read the resolved `mode` on the buy.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/media-buy-action-mode.json"
+        "$ref": "/schemas/3.1.30/enums/media-buy-action-mode.json"
       },
       "minItems": 1,
       "uniqueItems": true
@@ -22,13 +22,13 @@
       "type": "array",
       "description": "Media buy statuses in which this action is permitted. When absent, the action is permitted in all non-terminal statuses (`pending_creatives`, `pending_start`, `active`, `paused`).",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/media-buy-status.json"
+        "$ref": "/schemas/3.1.30/enums/media-buy-status.json"
       },
       "minItems": 1,
       "uniqueItems": true
     },
     "sla": {
-      "$ref": "/schemas/3.1.24/core/sla-window.json",
+      "$ref": "/schemas/3.1.30/core/sla-window.json",
       "description": "Optional SLA commitment for this action on this product. Absence means no commitment."
     },
     "terms_ref": {

package/dist/lib/schemas-data/3.1/core/product-filters.json

@@ -1,15 +1,15 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "/schemas/3.1.24/core/product-filters.json",
+  "$id": "/schemas/3.1.30/core/product-filters.json",
   "title": "Product Filters",
   "description": "Structured filters for product discovery",
   "type": "object",
   "properties": {
     "delivery_type": {
-      "$ref": "/schemas/3.1.24/enums/delivery-type.json"
+      "$ref": "/schemas/3.1.30/enums/delivery-type.json"
     },
     "exclusivity": {
-      "$ref": "/schemas/3.1.24/enums/exclusivity.json",
+      "$ref": "/schemas/3.1.30/enums/exclusivity.json",
       "description": "Filter by exclusivity level. Returns products matching the specified exclusivity (e.g., 'exclusive' returns only sole-sponsorship products)."
     },
     "is_fixed_price": {
@@ -32,7 +32,7 @@
       "type": "array",
       "description": "Filter by specific format IDs",
       "items": {
-        "$ref": "/schemas/3.1.24/core/format-id.json"
+        "$ref": "/schemas/3.1.30/core/format-id.json"
       },
       "minItems": 1
     },
@@ -117,7 +117,7 @@
         "type": "object",
         "properties": {
           "system": {
-            "$ref": "/schemas/3.1.24/enums/metro-system.json",
+            "$ref": "/schemas/3.1.30/enums/metro-system.json",
             "description": "Metro classification system"
           },
           "code": {
@@ -137,7 +137,7 @@
       "type": "array",
       "description": "Filter by advertising channels (e.g., ['display', 'ctv', 'dooh'])",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/channels.json"
+        "$ref": "/schemas/3.1.30/enums/channels.json"
       },
       "minItems": 1
     },
@@ -145,7 +145,7 @@
       "type": "array",
       "description": "Filter video products by acceptable declared video placement types, using IAB Tech Lab/OpenRTB 2.6 video.plcmt definitions with AdCP-native names. Sellers SHOULD return only products they can satisfy with at least one requested type. Products whose only available delivery is a mixed, non-targetable bundle that includes unrequested video placement types SHOULD NOT match unless the seller can constrain delivery to the requested type during planning or purchase. This filter has set semantics for wholesale feed canonicalization.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/video-placement-type.json"
+        "$ref": "/schemas/3.1.30/enums/video-placement-type.json"
       },
       "uniqueItems": true,
       "minItems": 1,
@@ -155,7 +155,7 @@
       "type": "array",
       "description": "Filter audio products by acceptable declared audio distribution types, using IAB Tech Lab/OpenRTB 2.6 audio.feed definitions with AdCP-native names. Sellers SHOULD return only products they can satisfy with at least one requested type. Products whose only available delivery is a mixed, non-targetable bundle that includes unrequested audio distribution types SHOULD NOT match unless the seller can constrain delivery to the requested type during planning or purchase. This filter has set semantics for wholesale feed canonicalization.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/audio-distribution-type.json"
+        "$ref": "/schemas/3.1.30/enums/audio-distribution-type.json"
       },
       "uniqueItems": true,
       "minItems": 1,
@@ -165,7 +165,7 @@
       "type": "array",
       "description": "Filter retail-media products by acceptable declared sponsored-placement types (sponsored search, sponsored display, or sponsored native). Sellers SHOULD return only products they can satisfy with at least one requested type. Products whose only available delivery is a mixed, non-targetable bundle that includes unrequested sponsored-placement types SHOULD NOT match unless the seller can constrain delivery to the requested type during planning or purchase. This filter has set semantics for wholesale feed canonicalization.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/sponsored-placement-type.json"
+        "$ref": "/schemas/3.1.30/enums/sponsored-placement-type.json"
       },
       "uniqueItems": true,
       "minItems": 1,
@@ -175,7 +175,7 @@
       "type": "array",
       "description": "Filter social products by acceptable declared social-placement surfaces (feed, stories, short_video, explore, or search). Sellers SHOULD return only products they can satisfy with at least one requested surface. Products whose only available delivery is a mixed, non-targetable bundle that includes unrequested surfaces SHOULD NOT match unless the seller can constrain delivery to the requested surface during planning or purchase. This filter has set semantics for wholesale feed canonicalization.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/social-placement-surface.json"
+        "$ref": "/schemas/3.1.30/enums/social-placement-surface.json"
       },
       "uniqueItems": true,
       "minItems": 1,
@@ -226,7 +226,7 @@
           "type": "array",
           "description": "Filter to products supporting specific TMP response types (e.g., 'activation', 'creative', 'catalog_items'). Products must support at least one of the listed types.",
           "items": {
-            "$ref": "/schemas/3.1.24/enums/response-type.json"
+            "$ref": "/schemas/3.1.30/enums/response-type.json"
           },
           "minItems": 1
         }
@@ -234,7 +234,7 @@
       "additionalProperties": false
     },
     "required_features": {
-      "$ref": "/schemas/3.1.24/core/media-buy-features.json",
+      "$ref": "/schemas/3.1.30/core/media-buy-features.json",
       "description": "Filter to products from sellers supporting specific protocol features. Only features set to true are used for filtering."
     },
     "required_geo_targeting": {
@@ -244,7 +244,7 @@
         "type": "object",
         "properties": {
           "level": {
-            "$ref": "/schemas/3.1.24/enums/geo-level.json",
+            "$ref": "/schemas/3.1.30/enums/geo-level.json",
             "description": "Geographic targeting level (country, region, metro, postal_area)"
           },
           "country": {
@@ -315,7 +315,7 @@
                 {
                   "properties": {
                     "system": {
-                      "$ref": "/schemas/3.1.24/enums/metro-system.json"
+                      "$ref": "/schemas/3.1.30/enums/metro-system.json"
                     }
                   },
                   "required": [
@@ -360,12 +360,12 @@
                   }
                 },
                 {
-                  "$ref": "/schemas/3.1.24/core/postal-country-system.json"
+                  "$ref": "/schemas/3.1.30/core/postal-country-system.json"
                 },
                 {
                   "properties": {
                     "system": {
-                      "$ref": "/schemas/3.1.24/enums/legacy-postal-system.json"
+                      "$ref": "/schemas/3.1.30/enums/legacy-postal-system.json"
                     }
                   },
                   "required": [
@@ -392,7 +392,7 @@
         "type": "object",
         "allOf": [
           {
-            "$ref": "/schemas/3.1.24/core/signal-targeting.json"
+            "$ref": "/schemas/3.1.30/core/signal-targeting.json"
           }
         ],
         "properties": {
@@ -413,7 +413,7 @@
       "type": "array",
       "description": "Filter by postal area coverage for locally-bound inventory (direct mail, DOOH, local campaigns). Prefer the native country + postal system form. Deprecated legacy country-fused postal-system tokens remain accepted for compatibility. For digital inventory where products have broad coverage, use required_geo_targeting instead to filter by seller capability.",
       "items": {
-        "$ref": "/schemas/3.1.24/core/postal-area.json"
+        "$ref": "/schemas/3.1.30/core/postal-area.json"
       },
       "minItems": 1
     },
@@ -449,7 +449,7 @@
                 "description": "Travel time limit"
               },
               "unit": {
-                "$ref": "/schemas/3.1.24/enums/travel-time-unit.json"
+                "$ref": "/schemas/3.1.30/enums/travel-time-unit.json"
               }
             },
             "required": [
@@ -459,7 +459,7 @@
             "additionalProperties": false
           },
           "transport_mode": {
-            "$ref": "/schemas/3.1.24/enums/transport-mode.json",
+            "$ref": "/schemas/3.1.30/enums/transport-mode.json",
             "description": "Transportation mode for isochrone calculation. Required when travel_time is provided."
           },
           "radius": {
@@ -472,7 +472,7 @@
                 "description": "Radius distance"
               },
               "unit": {
-                "$ref": "/schemas/3.1.24/enums/distance-unit.json",
+                "$ref": "/schemas/3.1.30/enums/distance-unit.json",
                 "description": "Distance unit"
               }
             },
@@ -578,7 +578,7 @@
       "type": "array",
       "description": "Filter to products that can meet the buyer's performance standard requirements. Each entry specifies a metric, minimum threshold, and optionally a required vendor and standard. Products that cannot meet these thresholds or do not support the specified vendors are excluded. Use this to tell the seller upfront: 'I need DoubleVerify for viewability at 70% MRC.'",
       "items": {
-        "$ref": "/schemas/3.1.24/core/performance-standard.json"
+        "$ref": "/schemas/3.1.30/core/performance-standard.json"
       },
       "minItems": 1
     },
@@ -586,7 +586,7 @@
       "type": "array",
       "description": "Filter to products whose `reporting_capabilities.available_metrics` is a superset of these metrics — i.e., products that commit to reporting all listed metrics in delivery responses. Use this for capability-level discovery (e.g., 'I need products that report `completed_views` for a CTV CPCV buy'); guarantee-level requirements with thresholds belong in `required_performance_standards` and `measurement_terms`. Sellers MUST silently exclude products that cannot meet this list (filter-not-fail; do not return an error). The product's declared `available_metrics` becomes the binding reporting contract carried into the resulting media buy — the same metric vocabulary is used to compute `missing_metrics` on `get_media_buy_delivery`.",
       "items": {
-        "$ref": "/schemas/3.1.24/enums/available-metric.json"
+        "$ref": "/schemas/3.1.30/enums/available-metric.json"
       },
       "minItems": 1,
       "uniqueItems": true,
@@ -612,11 +612,11 @@
         "type": "object",
         "properties": {
           "vendor": {
-            "$ref": "/schemas/3.1.24/core/brand-ref.json",
+            "$ref": "/schemas/3.1.30/core/brand-ref.json",
             "description": "Pin to a specific vendor. Optional — omit to match any vendor offering this `metric_id`."
           },
           "metric_id": {
-            "$ref": "/schemas/3.1.24/core/vendor-metric-id.json",
+            "$ref": "/schemas/3.1.30/core/vendor-metric-id.json",
             "description": "Pin to an exact metric identifier within a vendor's vocabulary. Optional — omit to match any metric from the pinned vendor. Cross-vendor identifier matching only works after vendors converge on identifiers (typically post-standardization)."
           }
         },
@@ -677,7 +677,7 @@
             "description": "The keyword to target"
           },
           "match_type": {
-            "$ref": "/schemas/3.1.24/enums/match-type.json",
+            "$ref": "/schemas/3.1.30/enums/match-type.json",
             "default": "broad"
           }
         },
@@ -689,7 +689,7 @@
       "minItems": 1
     },
     "ext": {
-      "$ref": "/schemas/3.1.24/core/ext.json",
+      "$ref": "/schemas/3.1.30/core/ext.json",
       "description": "Vendor-namespaced extension parameters for seller-specific filter criteria not covered by standard fields. Keys MUST be namespaced under a vendor or platform key (e.g., ext.gam, ext.platform_x). Sellers MUST treat all values as untrusted buyer input; do not interpolate into LLM prompts, SQL queries, or system commands without sanitization. Persistent use of an extension key across multiple buyers is a signal to propose standardization."
     }
   },