@adcp/client 4.22.0 → 4.23.0

package/dist/lib/version.d.ts

@@ -1,7 +1,7 @@
 /**
  * AdCP client library version
  */
-export declare const LIBRARY_VERSION = "4.20.0";
+export declare const LIBRARY_VERSION = "4.22.1";
 /**
  * AdCP specification version this library is built for
  */
@@ -20,10 +20,10 @@ export declare const COMPATIBLE_ADCP_VERSIONS: readonly ["v2.5", "v2.6", "v3", "
  * Full version information
  */
 export declare const VERSION_INFO: {
-    readonly library: "4.20.0";
+    readonly library: "4.22.1";
     readonly adcp: "latest";
     readonly compatibleVersions: readonly ["v2.5", "v2.6", "v3", "3.0.0-beta.1", "3.0.0-beta.3"];
-    readonly generatedAt: "2026-04-03T18:46:26.762Z";
+    readonly generatedAt: "2026-04-08T19:27:19.775Z";
 };
 /**
  * Get the AdCP specification version this library is built for

package/dist/lib/version.js

@@ -10,7 +10,7 @@ exports.getCompatibleVersions = getCompatibleVersions;
 /**
  * AdCP client library version
  */
-exports.LIBRARY_VERSION = '4.20.0';
+exports.LIBRARY_VERSION = '4.22.1';
 /**
  * AdCP specification version this library is built for
  */
@@ -29,10 +29,10 @@ exports.COMPATIBLE_ADCP_VERSIONS = ['v2.5', 'v2.6', 'v3', '3.0.0-beta.1', '3.0.0
  * Full version information
  */
 exports.VERSION_INFO = {
-    library: '4.20.0',
+    library: '4.22.1',
     adcp: 'latest',
     compatibleVersions: exports.COMPATIBLE_ADCP_VERSIONS,
-    generatedAt: '2026-04-03T18:46:26.762Z',
+    generatedAt: '2026-04-08T19:27:19.775Z',
 };
 /**
  * Get the AdCP specification version this library is built for

package/docs/guides/BUILD-AN-AGENT.md

@@ -24,8 +24,8 @@ import {
   GetSignalsRequestSchema,
 } from '@adcp/client';
 
-function createAgent() {
-  const server = createTaskCapableServer('My Signals Agent', '1.0.0');
+function createAgent({ taskStore }) {
+  const server = createTaskCapableServer('My Signals Agent', '1.0.0', { taskStore });
 
   server.tool(
     'get_signals',
@@ -193,7 +193,7 @@ Key storyboards for server-side builders:
 
 ### HTTP Transport
 
-The `serve()` helper handles HTTP transport setup. Pass it a factory function that returns a configured `McpServer`:
+The `serve()` helper handles HTTP transport setup. Pass it a factory function that receives a `ServeContext` and returns a configured `McpServer`:
 
 ```typescript
 import { serve } from '@adcp/client';
@@ -203,6 +203,8 @@ serve(createMyAgent, { port: 8080 });          // custom port
 serve(createMyAgent, { path: '/v1/mcp' });     // custom path
 ```
 
+`serve()` creates a shared task store and passes it to your factory on every request via `{ taskStore }`. Pass it through to `createTaskCapableServer()` so MCP Tasks work correctly across stateless HTTP requests.
+
 `serve()` returns the underlying `http.Server` for lifecycle control (e.g., graceful shutdown).
 
 For custom routing or middleware, you can wire the transport manually:

package/docs/llms.txt

@@ -1,7 +1,7 @@
 # Ad Context Protocol (AdCP)
 
 > Generated at: 2026-04-08
-> Library: @adcp/client v4.20.0
+> Library: @adcp/client v4.22.1
 > AdCP major version: 3
 > Canonical URL: https://adcontextprotocol.github.io/adcp-client/llms.txt
 
@@ -17,8 +17,8 @@ AdCP is an open protocol for AI agents to buy, manage, and optimize advertising
 ```typescript
 import { createTaskCapableServer, taskToolResponse, serve, GetSignalsRequestSchema } from '@adcp/client';
 
-function createAgent() {
-  const server = createTaskCapableServer('My Agent', '1.0.0');
+function createAgent({ taskStore }) {
+  const server = createTaskCapableServer('My Agent', '1.0.0', { taskStore });
   server.tool('get_signals', 'Discover segments.', GetSignalsRequestSchema.shape, async (args) => {
     return taskToolResponse({ signals: [...], sandbox: true }, 'Found segments');
   });
@@ -191,7 +191,7 @@ Optional: `catalogs: object[]`, `catalog_ids: string[]`, `delete_missing: boolea
 
 Request parameters for AI-powered creative generation.
 
-Optional: `message: string`, `creative_manifest: Creative Manifest`, `creative_id: string`, `concept_id: string`, `media_buy_id: string`, `package_id: string`, `target_format_id: Format Id`, `target_format_ids: object[]`, +10 more
+Optional: `message: string`, `creative_manifest: Creative Manifest`, `creative_id: string`, `concept_id: string`, `media_buy_id: string`, `package_id: string`, `target_format_id: Format Id`, `target_format_ids: object[]`, +11 more
 
 #### `preview_creative`
 
@@ -202,7 +202,7 @@ Request parameters for generating creative previews.
 
 Request parameters for discovering creative formats from this creative agent.
 
-Optional: `format_ids: object[]`, `type: 'audio' | 'video' | 'display' | 'dooh'`, `asset_types: string[]`, `max_width: integer`, `max_height: integer`, `min_width: integer`, `min_height: integer`, `is_responsive: boolean`, +8 more
+Optional: `format_ids: object[]`, `type: 'audio' | 'video' | 'display' | 'dooh'`, `asset_types: string[]`, `max_width: integer`, `max_height: integer`, `min_width: integer`, `min_height: integer`, `is_responsive: boolean`, +10 more
 
 #### `get_creative_delivery`
 
@@ -214,7 +214,7 @@ Optional: `account: Account Ref`, `media_buy_ids: string[]`, `creative_ids: stri
 
 Request parameters for querying creative library with filtering and pagination.
 
-Optional: `filters: Creative Filters`, `sort: object`, `pagination: Pagination Request`, `include_assignments: boolean`, `include_snapshot: boolean`, `include_items: boolean`, `include_variables: boolean`, `fields: string[]`, +1 more
+Optional: `filters: Creative Filters`, `sort: object`, `pagination: Pagination Request`, `include_assignments: boolean`, `include_snapshot: boolean`, `include_items: boolean`, `include_variables: boolean`, `include_pricing: boolean`, +3 more
 
 #### `sync_creatives`
 
@@ -416,26 +416,57 @@ These are the standard tool call sequences from the AdCP storyboards. Each flow
 
 ### Audiences
 
-**Audience sync** — Tests sync_audiences: account discovery, audience creation with hashed identifiers, and audience deletion.
+**Audience sync** — Full audience lifecycle: account discovery, audience creation with hashed identifiers, and audience deletion.
 Flow: `list_accounts → sync_audiences`
 
+**Social platform** — Social media platform that accepts audience segments, native creatives, and conversion events from buyer agents.
+Flow: `sync_accounts → list_accounts → sync_audiences → sync_creatives → log_event → get_account_financials`
+
 ### Products
 
-**Behavioral analysis** — Validates product discovery behavior, response consistency, and pricing edge cases.
+**Behavioral analysis** — Validates product discovery behavior: brief filtering, response consistency, and pricing edge cases.
 Flow: `get_products`
 
 ### Core
 
-**Brand rights flow** — Agent that provides brand identity, queries rights, and supports rights acquisition.
-Flow: `get_brand_identity → get_rights → acquire_rights`
+**Brand identity and rights licensing** — Brand agent that serves identity assets and licenses rights for AI-generated content.
+Flow: `get_brand_identity → get_rights → acquire_rights → update_rights → creative_approval`
+
+**Capability discovery** — Buyer calls get_adcp_capabilities to discover what an agent supports before making any buying or creative decisions.
+Flow: `get_adcp_capabilities`
 
 **Deterministic testing** — Uses comply_test_controller to force state transitions and simulate delivery/budget, verifying state machines and reporting.
 Flow: `comply_test_controller → list_accounts → comply_test_controller → create_media_buy → comply_test_controller → get_media_buys → comply_test_controller → sync_creatives → comply_test_controller → si_initiate_session → comply_test_controller → si_send_message → create_media_buy → comply_test_controller → get_media_buy_delivery → create_media_buy → comply_test_controller`
 
+### Campaign Governance
+
+**Campaign governance — conditional approval** — Governance agent approves a media buy with conditions. Buyer re-checks after meeting the conditions.
+Flow: `sync_plans → check_governance → create_media_buy`
+
+**Campaign governance — delivery monitoring with drift detection** — Governance agent monitors delivery, detects budget drift past thresholds, and triggers re-evaluation.
+Flow: `sync_plans → check_governance → get_media_buy_delivery → check_governance`
+
+**Campaign governance — denied** — Governance agent denies a media buy that exceeds the agent's spending authority. No human escalation — the buy is blocked.
+Flow: `sync_plans → check_governance`
+
+**Governance denial and human escalation** — Buyer's governance agent denies a media buy that exceeds spending authority, escalates to a human who approves with conditions.
+Flow: `sync_accounts → sync_governance → sync_plans → get_products → check_governance → create_media_buy → report_plan_outcome → get_plan_audit_logs`
+
+### Governance
+
+**Content standards** — Define creative quality rules, calibrate content against them, and validate that delivered ads met the standards.
+Flow: `create_content_standards → list_content_standards → get_content_standards → update_content_standards → calibrate_content → validate_content_delivery`
+
+**Property governance** — Manage brand safety property lists — create inclusion/exclusion lists, query and update them, validate delivery compliance.
+Flow: `create_property_list → list_property_lists → get_property_list → update_property_list → delete_property_list → validate_property_delivery`
+
 ### Creative
 
-**Creative ad server** — Stateful ad server with pre-loaded creatives. Generates serving tags per media buy.
-Flow: `list_creatives → list_creative_formats → build_creative → get_creative_delivery`
+**Creative ad server** — Stateful ad server with pre-loaded creatives. Generates serving tags per media buy with pricing and billing.
+Flow: `list_creatives → list_creative_formats → build_creative → get_creative_delivery → report_usage`
+
+**Creative lifecycle** — Full creative lifecycle on a stateful platform: sync multiple creatives, list with filtering, build and preview across formats, observe status transitions.
+Flow: `list_creative_formats → sync_creatives → list_creatives → preview_creative → build_creative`
 
 **Sales agent with creative capabilities** — Stateful sales agent that accepts pushed creative assets and renders them in its environment.
 Flow: `list_creative_formats → sync_creatives → preview_creative`
@@ -448,14 +479,6 @@ Flow: `list_creative_formats → preview_creative → build_creative`
 **Error handling and compliance** — Validates that agents return properly structured AdCP errors with correct codes, recovery hints, and transport bindings.
 Flow: `create_media_buy → get_products → create_media_buy`
 
-### Governance
-
-**Governance content standards** — Content standards discovery, calibration, and delivery validation.
-Flow: `list_content_standards → get_content_standards → calibrate_content → validate_content_delivery`
-
-**Governance property list management** — CRUD lifecycle for property lists with filter round-trip validation.
-Flow: `create_property_list → get_property_list → update_property_list → list_property_lists → delete_property_list → get_property_list → create_property_list → get_property_list → delete_property_list`
-
 ### Media Buy
 
 **Catalog-driven creative and conversion tracking** — Seller that renders dynamic ads from product catalogs, tracks conversions, and optimizes delivery based on performance feedback.
@@ -470,23 +493,16 @@ Flow: `get_products → create_media_buy → get_media_buys → update_media_buy
 **Media buy via proposal acceptance** — Seller agent that generates curated media plan proposals the buyer can review, refine, and accept.
 Flow: `sync_accounts → get_products → create_media_buy → list_creative_formats → sync_creatives → get_media_buy_delivery`
 
-**Media buy state machine lifecycle** — Validates media buy state transitions: create, pause, resume, cancel, and terminal state enforcement.
-Flow: `get_products → create_media_buy → update_media_buy`
-
-### Campaign Governance
-
-**Governance denial and human escalation** — Buyer's governance agent denies a media buy that exceeds spending authority, escalates to a human who approves with conditions.
-Flow: `sync_accounts → sync_governance → sync_plans → get_products → check_governance → create_media_buy → report_plan_outcome → get_plan_audit_logs`
-
-### Reporting
-
 **Media buy seller agent** — Seller agent that receives briefs, returns products, accepts media buys, and reports delivery.
 Flow: `sync_accounts → sync_governance → get_products → create_media_buy → get_media_buys → list_creative_formats → sync_creatives → get_media_buy_delivery`
 
+**Media buy state machine lifecycle** — Validates media buy state transitions: create, pause, resume, cancel, and terminal state enforcement.
+Flow: `get_products → create_media_buy → update_media_buy`
+
 ### Sponsored Intelligence (SI)
 
-**Sponsored intelligence session** — SI agent that serves offerings, manages conversational sessions, and handles purchase handoffs.
-Flow: `si_get_offering → si_initiate_session → si_send_message → si_terminate_session → si_send_message → si_initiate_session → si_send_message → si_terminate_session`
+**Sponsored intelligence session** — Conversational ad session on an AI platform — discover offerings, initiate a session, exchange messages, and terminate.
+Flow: `si_get_offering → si_initiate_session → si_send_message → si_terminate_session`
 
 ### Signals
 

package/examples/signals-agent.ts

@@ -18,7 +18,7 @@
  */
 
 import { createTaskCapableServer, taskToolResponse, serve, GetSignalsRequestSchema } from '@adcp/client';
-import type { GetSignalsResponse } from '@adcp/client';
+import type { GetSignalsResponse, ServeContext } from '@adcp/client';
 
 // ---------------------------------------------------------------------------
 // Audience segment catalog — typed to match the AdCP signals response schema
@@ -132,8 +132,9 @@ function querySegments(args: {
 // ---------------------------------------------------------------------------
 // Server factory
 // ---------------------------------------------------------------------------
-function createSignalsAgent() {
+function createSignalsAgent({ taskStore }: ServeContext) {
   const server = createTaskCapableServer('Example Signals Agent', '1.0.0', {
+    taskStore,
     instructions: 'Signals agent providing audience segment discovery via get_signals.',
   });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adcp/client",
-  "version": "4.22.0",
+  "version": "4.23.0",
   "description": "AdCP client library with protocol support for MCP and A2A",
   "main": "dist/lib/index.js",
   "types": "dist/lib/index.d.ts",

package/storyboards/audience_sync.yaml

@@ -1,8 +1,8 @@
 id: audience_sync
 version: "1.0.0"
 title: "Audience sync"
-category: audiences
-summary: "Tests sync_audiences: account discovery, audience creation with hashed identifiers, and audience deletion."
+category: audience_sync
+summary: "Full audience lifecycle: account discovery, audience creation with hashed identifiers, and audience deletion."
 track: audiences
 required_tools:
   - sync_audiences
@@ -10,6 +10,7 @@ platform_types:
   - display_ad_server
   - social_platform
   - retail_media
+  - audio_platform
   - dsp
   - pmax_platform
 
@@ -53,20 +54,14 @@ phases:
       - id: discover_account
         title: "Discover or create account"
         narrative: |
-          List existing accounts to find one suitable for audience sync. If no accounts
-          exist, sync_accounts creates one. The account_id is captured for use in
+          List existing accounts to find one suitable for audience sync. The account
+          must already exist and be active. The account_id is captured for use in
           subsequent audience operations.
         task: list_accounts
         schema_ref: "account/list-accounts-request.json"
         response_schema_ref: "account/list-accounts-response.json"
         doc_ref: "/accounts/tasks/list_accounts"
-        comply_scenario: account_setup
         stateful: false
-        context_outputs:
-          - name: account_id
-            path: "accounts[0].account_id"
-          - name: account_ref
-            path: "accounts[0]"
         expected: |
           Return at least one account with:
           - account_id: platform-assigned identifier
@@ -98,14 +93,11 @@ phases:
           already exist on the platform for this account. This is a read-only
           discovery call.
         task: sync_audiences
-        schema_ref: "audience/sync-audiences-request.json"
-        response_schema_ref: "audience/sync-audiences-response.json"
-        doc_ref: "/audiences/tasks/sync_audiences"
-        comply_scenario: audience_sync
+        schema_ref: "media-buy/sync-audiences-request.json"
+        response_schema_ref: "media-buy/sync-audiences-response.json"
+        doc_ref: "/media-buy/task-reference/sync_audiences"
+        comply_scenario: sync_audiences
         stateful: false
-        context_outputs:
-          - name: existing_audience_count
-            path: "audiences.length"
         expected: |
           Return existing audiences for the account (may be empty).
           Each audience should have an audience_id and status.
@@ -127,14 +119,11 @@ phases:
           matches identifiers against their user graph and returns the audience with
           action: created, match counts, and match rate.
         task: sync_audiences
-        schema_ref: "audience/sync-audiences-request.json"
-        response_schema_ref: "audience/sync-audiences-response.json"
-        doc_ref: "/audiences/tasks/sync_audiences"
-        comply_scenario: audience_sync
+        schema_ref: "media-buy/sync-audiences-request.json"
+        response_schema_ref: "media-buy/sync-audiences-response.json"
+        doc_ref: "/media-buy/task-reference/sync_audiences"
+        comply_scenario: sync_audiences
         stateful: true
-        context_outputs:
-          - name: test_audience_id
-            path: "audiences[0].audience_id"
         expected: |
           Accept the audience and return:
           - audience_id: matches the submitted ID
@@ -151,7 +140,7 @@ phases:
             operator: "pinnacle-agency.com"
           audiences:
             - audience_id: "adcp-test-audience-001"
-              name: "AdCP E2E Test Audience"
+              name: "AdCP test audience"
               add:
                 - hashed_email: "a000000000000000000000000000000000000000000000000000000000000000"
                 - hashed_phone: "b000000000000000000000000000000000000000000000000000000000000000"
@@ -172,10 +161,10 @@ phases:
           Clean up by deleting the test audience. The seller should acknowledge the
           deletion with action: deleted.
         task: sync_audiences
-        schema_ref: "audience/sync-audiences-request.json"
-        response_schema_ref: "audience/sync-audiences-response.json"
-        doc_ref: "/audiences/tasks/sync_audiences"
-        comply_scenario: audience_sync
+        schema_ref: "media-buy/sync-audiences-request.json"
+        response_schema_ref: "media-buy/sync-audiences-response.json"
+        doc_ref: "/media-buy/task-reference/sync_audiences"
+        comply_scenario: sync_audiences
         stateful: true
         expected: |
           Delete the test audience and return:

package/storyboards/behavioral_analysis.yaml

@@ -1,8 +1,8 @@
 id: behavioral_analysis
 version: "1.0.0"
 title: "Behavioral analysis"
-category: products
-summary: "Validates product discovery behavior, response consistency, and pricing edge cases."
+category: behavioral_analysis
+summary: "Validates product discovery behavior: brief filtering, response consistency, and pricing edge cases."
 track: products
 required_tools:
   - get_products
@@ -13,7 +13,6 @@ platform_types:
   - retail_media
   - search_platform
   - audio_platform
-  - linear_tv_platform
   - dsp
   - pmax_platform
   - ai_ad_network
@@ -54,7 +53,7 @@ prerequisites:
 
 phases:
   - id: behavior_analysis
-    title: "Behavior analysis"
+    title: "Brief filtering behavior"
     narrative: |
       Tests whether the agent filters products based on the brief content. Two different
       briefs are sent — one narrow (podcast audio only) and one broad (all products across
@@ -73,18 +72,13 @@ phases:
         doc_ref: "/media-buy/task-reference/get_products"
         comply_scenario: behavior_analysis
         stateful: false
-        context_outputs:
-          - name: narrow_product_ids
-            path: "products[*].product_id"
-          - name: narrow_product_count
-            path: "products.length"
         expected: |
-          Return products matching the narrow brief. The result set should be scoped
-          to audio/podcast inventory if the agent performs brief filtering.
+          Return products matching the narrow brief. If the agent interprets briefs,
+          this should return fewer products than a broad request.
 
         sample_request:
           buying_mode: "brief"
-          brief: "Looking specifically for podcast audio advertising only"
+          brief: "Podcast audio advertising only — 30-second pre-roll spots"
           brand:
             domain: "acmeoutdoor.com"
 
@@ -98,9 +92,9 @@ phases:
       - id: get_products_broad
         title: "Get products with broad brief"
         narrative: |
-          Send a broad brief requesting all products across all channels. Compare the
-          result count against the narrow brief to determine whether the agent filters
-          by brief content.
+          Send a broad brief requesting all available products. Compare the result count
+          with the narrow brief — if the agent filters by brief, the broad request should
+          return more products.
         task: get_products
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
@@ -108,69 +102,56 @@ phases:
         comply_scenario: behavior_analysis
         stateful: false
         expected: |
-          Return all available products. If the agent performs brief filtering, this
-          response should contain more products than the narrow brief response.
+          Return all available products. The product count should be greater than or
+          equal to the narrow brief response.
 
         sample_request:
           buying_mode: "brief"
-          brief: "Show all products across all channels and formats"
+          brief: "Show me everything — all channels, all formats, all inventory"
           brand:
             domain: "acmeoutdoor.com"
 
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
-          - check: field_present
-            path: "products"
-            description: "Response contains a products array"
-          - check: compare_context
-            description: "Broad brief returns >= narrow brief product count"
-            context_ref: narrow_product_count
-            comparison: ">="
 
   - id: response_consistency
     title: "Response consistency"
     narrative: |
-      Calls get_products twice with the identical brief and brand. The agent should
-      return the same product IDs both times. Non-deterministic responses indicate
-      randomness in product selection or caching issues.
+      Tests whether the agent returns deterministic results for identical inputs.
+      The same brief is sent twice — the response should contain the same product IDs
+      in both cases.
 
     steps:
       - id: get_products_first
-        title: "First call with fixed brief"
+        title: "First request with identical brief"
         narrative: |
-          Send a specific brief and capture the returned product IDs for comparison.
+          Send a brief and capture the product IDs returned.
         task: get_products
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
         doc_ref: "/media-buy/task-reference/get_products"
         comply_scenario: response_consistency
         stateful: false
-        context_outputs:
-          - name: first_call_product_ids
-            path: "products[*].product_id"
         expected: |
-          Return products matching the brief. Product IDs are captured for comparison
-          with a second identical call.
+          Return products matching the brief. Product IDs will be compared with a
+          subsequent identical request.
 
         sample_request:
           buying_mode: "brief"
-          brief: "Premium video inventory on sports and outdoor lifestyle publishers. Q2 flight, $50K budget. Adults 25-54, US and Canada."
+          brief: "Premium video inventory on sports publishers. Adults 25-54."
           brand:
             domain: "acmeoutdoor.com"
 
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
-          - check: field_present
-            path: "products[0].product_id"
-            description: "At least one product returned with a product_id"
 
       - id: get_products_second
-        title: "Second call with identical brief"
+        title: "Second request with identical brief"
         narrative: |
-          Repeat the exact same request. The returned product IDs should match
-          those from the first call.
+          Send the exact same brief again. The returned product IDs should match the
+          first response.
         task: get_products
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
@@ -178,37 +159,31 @@ phases:
         comply_scenario: response_consistency
         stateful: false
         expected: |
-          Return the same product IDs as the first call. Consistent responses
-          for identical inputs are expected.
+          Return the same product IDs as the first request. Deterministic responses
+          are expected for identical inputs.
 
         sample_request:
           buying_mode: "brief"
-          brief: "Premium video inventory on sports and outdoor lifestyle publishers. Q2 flight, $50K budget. Adults 25-54, US and Canada."
+          brief: "Premium video inventory on sports publishers. Adults 25-54."
           brand:
             domain: "acmeoutdoor.com"
 
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
-          - check: match_context
-            description: "Product IDs match the first call"
-            context_ref: first_call_product_ids
-            path: "products[*].product_id"
 
   - id: pricing_edge_cases
-    title: "Pricing edge cases"
+    title: "Pricing structure validation"
     narrative: |
-      Validates the structure of pricing_options on returned products. Each product
-      should declare a delivery_type (guaranteed or non_guaranteed) and well-formed
-      pricing options with recognized fields.
+      Validates that products declare well-formed pricing_options with recognized
+      delivery_type values and complete pricing structures.
 
     steps:
       - id: get_products_pricing
-        title: "Fetch products for pricing analysis"
+        title: "Validate pricing structures"
         narrative: |
-          Request all products with pricing details. Validate that each product has
-          a valid delivery_type and that pricing_options contain recognized fields
-          (fixed_price, floor_price, price_guidance, min_spend_per_package).
+          Send a brief and inspect the pricing structures on returned products.
+          Every product must have a recognized delivery_type and valid pricing_options.
         task: get_products
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
@@ -216,29 +191,22 @@ phases:
         comply_scenario: pricing_edge_cases
         stateful: false
         expected: |
-          Return products with well-formed pricing structures:
-          - Each product has a delivery_type: guaranteed or non_guaranteed
-          - Each pricing_option has a pricing_option_id
-          - Pricing fields are valid (no negative values, recognized pricing models)
+          Products with valid pricing structures:
+          - delivery_type: "guaranteed" or "non_guaranteed"
+          - pricing_options with pricing_option_id and pricing_model
 
         sample_request:
           buying_mode: "brief"
-          brief: "Show all products with pricing details"
+          brief: "All available products with detailed pricing"
           brand:
             domain: "acmeoutdoor.com"
 
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
-          - check: field_present
-            path: "products"
-            description: "Response contains products array"
           - check: field_present
             path: "products[0].delivery_type"
-            description: "Each product declares guaranteed or non_guaranteed delivery"
-          - check: field_value
-            path: "products[*].delivery_type"
-            allowed_values:
-              - "guaranteed"
-              - "non_guaranteed"
-            description: "delivery_type is a recognized value"
+            description: "Products declare delivery_type"
+          - check: field_present
+            path: "products[0].pricing_options"
+            description: "Products include pricing_options"