@adcp/client 4.20.0 → 4.22.0

package/storyboards/media_buy_guaranteed_approval.yaml

@@ -0,0 +1,396 @@
+id: media_buy_guaranteed_approval
+version: "1.0.0"
+title: "Guaranteed media buy with human IO approval"
+category: media_buy_guaranteed_approval
+summary: "Seller agent that requires human-in-the-loop IO signing before guaranteed media buys go live."
+platform_types:
+  - display_ad_server
+  - video_ad_server
+  - audio_platform
+  - linear_tv_platform
+
+track: media_buy
+required_tools:
+  - create_media_buy
+narrative: |
+  You run a sell-side platform that requires human approval before guaranteed media buys go
+  live. When a buyer creates a guaranteed buy, your platform returns a submitted status with
+  an estimated completion time. A human reviewer on your side reviews the deal terms and
+  signs the IO through a URL your platform provides.
+
+  The buyer either polls get_media_buys or configures a push_notification_config webhook to
+  receive a callback when the IO is signed. Once approved, the media buy transitions from
+  pending_approval to confirmed/active and the buyer can sync creatives and monitor delivery.
+
+  This storyboard isolates the guaranteed approval path — the async handshake between agent
+  automation and human decision-making that makes guaranteed buys work in practice.
+
+agent:
+  interaction_model: media_buy_seller
+  capabilities:
+    - sells_media
+    - supports_guaranteed
+    - requires_io_approval
+  examples:
+    - "Premium publisher with IO requirements"
+    - "Retail media network with sales approval"
+    - "CTV platform with guaranteed deals"
+
+caller:
+  role: buyer_agent
+  example: "Scope3 (DSP)"
+
+prerequisites:
+  description: |
+    The caller needs a brand identity and operator credentials for account setup.
+    The test kit provides a sample brand (Acme Outdoor) with campaign parameters
+    suitable for testing the guaranteed approval flow.
+  test_kit: "test-kits/acme-outdoor.yaml"
+
+phases:
+  - id: account_setup
+    title: "Account setup"
+    narrative: |
+      Before buying anything, the buyer establishes an account relationship with
+      your platform. This is the handshake: the buyer tells you which brand and
+      agency (operator) they represent, and you return an account ID, status, and
+      any setup requirements.
+
+    steps:
+      - id: sync_accounts
+        title: "Establish account relationship"
+        narrative: |
+          The buyer registers their brand and operator with your platform. This is
+          the first call in any new relationship. Your platform validates the request,
+          provisions the account, and returns its status.
+        task: sync_accounts
+        schema_ref: "account/sync-accounts-request.json"
+        response_schema_ref: "account/sync-accounts-response.json"
+        doc_ref: "/accounts/tasks/sync_accounts"
+        stateful: true
+        expected: |
+          Return the account with:
+          - account_id: your platform's identifier for this relationship
+          - action: created or updated
+          - status: active or pending_approval
+          - account_scope: operator, brand, operator_brand, or agent
+          - setup: URL and message if pending_approval
+          - payment_terms: net_30, prepay, etc.
+
+        sample_request:
+          accounts:
+            - brand:
+                domain: "acmeoutdoor.com"
+              operator: "pinnacle-agency.com"
+              billing: "operator"
+              payment_terms: "net_30"
+
+        validations:
+          - check: response_schema
+            description: "Response matches sync-accounts-response.json schema"
+          - check: field_present
+            path: "accounts[0].account_id"
+            description: "Account has a platform-assigned ID"
+          - check: field_present
+            path: "accounts[0].status"
+            description: "Account has a status (active or pending_approval)"
+
+  - id: product_discovery
+    title: "Discover guaranteed products"
+    narrative: |
+      The buyer sends a brief to discover your guaranteed inventory. The emphasis
+      here is on products with delivery_type: guaranteed — fixed-price, reserved
+      inventory that requires an IO commitment. Your platform returns products with
+      pricing, delivery forecasts, and SLA commitments.
+
+    steps:
+      - id: get_products_brief
+        title: "Send a brief targeting guaranteed inventory"
+        narrative: |
+          The buyer describes what they want, emphasizing guaranteed delivery. Your
+          platform returns products with delivery_type: guaranteed, including SLA
+          commitments, minimum spend requirements, and IO terms.
+        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"
+        stateful: false
+        expected: |
+          Return guaranteed products matching the brief. Each product should include:
+          - product_id: unique identifier
+          - name and description
+          - delivery_type: guaranteed
+          - pricing_models: fixed CPM or flat-rate pricing
+          - forecast: committed impressions with SLA guarantees
+          - creative_format_ids: required creative formats
+          - minimum_spend or commitment terms if applicable
+
+        sample_request:
+          buying_mode: "brief"
+          brief: "Guaranteed premium video on sports and outdoor lifestyle publishers. Q2 flight, $50K budget. Adults 25-54, US only. Need completion rate SLA."
+          brand:
+            domain: "acmeoutdoor.com"
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.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: field_present
+            path: "products[0].product_id"
+            description: "Each product has a product_id"
+          - check: field_present
+            path: "products[0].delivery_type"
+            description: "Each product declares delivery_type: guaranteed"
+
+  - id: create_buy_submitted
+    title: "Create guaranteed buy (submitted for approval)"
+    narrative: |
+      The buyer creates a guaranteed media buy. Because your platform requires human
+      IO signing for guaranteed deals, the response comes back as submitted — not
+      completed. The buyer gets an estimated_completion timestamp indicating when the
+      IO review should finish. The buyer configures a webhook to be notified when the
+      status changes.
+
+    steps:
+      - id: create_media_buy
+        title: "Create a guaranteed media buy"
+        narrative: |
+          The buyer commits to guaranteed products with budgets and flight dates. Your
+          platform accepts the request but does not confirm it immediately. Instead,
+          it enters an IO approval workflow and returns submitted status with an
+          estimated_completion timestamp.
+
+          The buyer includes push_notification_config so your platform can call back
+          when the IO is signed (or rejected).
+        task: create_media_buy
+        schema_ref: "media-buy/create-media-buy-request.json"
+        response_schema_ref: "media-buy/create-media-buy-response.json"
+        doc_ref: "/media-buy/task-reference/create_media_buy"
+        stateful: true
+        expected: |
+          Return the media buy in submitted status:
+          - media_buy_id: your platform's identifier
+          - status: submitted (NOT completed — this requires human approval)
+          - estimated_completion: timestamp when the IO review should finish
+          - packages: the proposed line items echoed back
+          - The buyer's push_notification_config is acknowledged
+
+          Do NOT return completed status for guaranteed buys that require IO signing.
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          brand:
+            domain: "acmeoutdoor.com"
+          start_time: "2026-04-01T00:00:00Z"
+          end_time: "2026-06-30T23:59:59Z"
+          packages:
+            - product_id: "sports_preroll_q2_guaranteed"
+              budget: 30000
+              pricing_option_id: "cpm_guaranteed_fixed"
+              creative_assignments:
+                - creative_id: "video_30s_trail_pro"
+            - product_id: "outdoor_ctv_q2_guaranteed"
+              budget: 20000
+              pricing_option_id: "cpm_guaranteed_fixed"
+          push_notification_config:
+            url: "https://buyer.example/webhooks/adcp"
+            authentication:
+              scheme: "HMAC-SHA256"
+
+        validations:
+          - check: response_schema
+            description: "Response matches create-media-buy-response.json schema"
+
+  - id: poll_approval
+    title: "Poll for IO approval"
+    narrative: |
+      The media buy is sitting in an approval queue. A human on the seller side needs
+      to review the deal terms and sign the IO. The buyer polls get_media_buys to check
+      the current status. Your platform returns pending_approval with a setup URL where
+      the human reviewer signs the IO and a message explaining what is needed.
+
+    steps:
+      - id: get_media_buys_pending
+        title: "Check media buy status (pending approval)"
+        narrative: |
+          The buyer polls for the media buy status. Your platform returns
+          pending_approval with a setup object containing the URL where the human
+          reviewer signs the IO and a message describing what action is needed.
+        task: get_media_buys
+        schema_ref: "media-buy/get-media-buys-request.json"
+        response_schema_ref: "media-buy/get-media-buys-response.json"
+        doc_ref: "/media-buy/task-reference/get_media_buys"
+        stateful: true
+        expected: |
+          Return the media buy in pending_approval status:
+          - media_buy_id: matches the buy created earlier
+          - status: pending_approval
+          - setup.url: where the human goes to review and sign the IO
+          - setup.message: explains what the human needs to do (e.g., "Review and sign the IO for Acme Outdoor Q2 campaign")
+          - packages: line items with their current state
+          - valid_actions: what the buyer can do in this state
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          media_buy_ids:
+            - "mb_acme_q2_2026_guaranteed"
+
+        validations:
+          - check: response_schema
+            description: "Response matches get-media-buys-response.json schema"
+          - check: field_present
+            path: "media_buys[0].status"
+            description: "Media buy has a status"
+          - check: field_present
+            path: "media_buys[0].setup.url"
+            description: "Pending approval buy includes a setup URL for IO signing"
+          - check: field_present
+            path: "media_buys[0].setup.message"
+            description: "Pending approval buy includes a message explaining what's needed"
+
+  - id: confirm_active
+    title: "Confirm active after IO signing"
+    narrative: |
+      The human has reviewed the IO and signed it through the setup URL. The buyer
+      polls get_media_buys again (or received a webhook notification) and sees that the
+      media buy has transitioned from pending_approval to confirmed or active. The buy
+      is now live.
+
+    steps:
+      - id: get_media_buys_confirmed
+        title: "Check media buy status (confirmed/active)"
+        narrative: |
+          After the human signs the IO, the buyer checks the media buy status again.
+          Your platform returns confirmed or active, indicating the buy is approved
+          and inventory is reserved.
+        task: get_media_buys
+        schema_ref: "media-buy/get-media-buys-request.json"
+        response_schema_ref: "media-buy/get-media-buys-response.json"
+        doc_ref: "/media-buy/task-reference/get_media_buys"
+        stateful: true
+        expected: |
+          Return the media buy in confirmed or active status:
+          - media_buy_id: matches the buy created earlier
+          - status: confirmed or active (IO has been signed)
+          - confirmed_at: timestamp when the IO was signed
+          - packages: line items now confirmed with reserved inventory
+          - valid_actions: updated for confirmed state (creative sync, pause, etc.)
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          media_buy_ids:
+            - "mb_acme_q2_2026_guaranteed"
+
+        validations:
+          - check: response_schema
+            description: "Response matches get-media-buys-response.json schema"
+          - check: field_present
+            path: "media_buys[0].status"
+            description: "Media buy status is confirmed or active"
+          - check: field_present
+            path: "media_buys[0].confirmed_at"
+            description: "Confirmed buy includes a confirmed_at timestamp"
+
+  - id: creative_sync
+    title: "Creative sync"
+    narrative: |
+      With the IO signed and the media buy confirmed, the buyer syncs creative assets
+      to your platform. Each package has creative format requirements that the buyer
+      discovered during product discovery.
+
+    steps:
+      - id: sync_creatives
+        title: "Push creative assets"
+        narrative: |
+          The buyer uploads creative assets for the confirmed packages. Your platform
+          validates each creative against the format specs and returns per-creative status.
+        task: sync_creatives
+        schema_ref: "creative/sync-creatives-request.json"
+        response_schema_ref: "creative/sync-creatives-response.json"
+        doc_ref: "/creative/task-reference/sync_creatives"
+        stateful: true
+        expected: |
+          Accept and validate creatives:
+          - Per-creative action: created or updated
+          - Per-creative status: accepted, pending_review, or rejected
+          - Validation errors for rejected creatives
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          creatives:
+            - creative_id: "video_30s_trail_pro"
+              name: "Trail Pro 3000 - 30s CTV Spot"
+              format_id:
+                agent_url: "https://your-platform.example.com"
+                id: "ssai_30s"
+              assets:
+                - asset_id: "video"
+                  asset_type: "video"
+                  url: "https://cdn.pinnacle-agency.example/trail-pro-30s.mp4"
+                  mime_type: "video/mp4"
+
+        validations:
+          - check: response_schema
+            description: "Response matches sync-creatives-response.json schema"
+          - check: field_present
+            path: "creatives[0].action"
+            description: "Each creative has an action (created/updated)"
+
+  - id: delivery_monitoring
+    title: "Delivery and reporting"
+    narrative: |
+      The campaign is live with guaranteed delivery commitments. The buyer monitors
+      delivery to ensure the seller is meeting the SLA guarantees from the IO.
+
+    steps:
+      - id: get_delivery
+        title: "Check delivery metrics"
+        narrative: |
+          The buyer requests delivery data for the active guaranteed media buy. Your
+          platform returns performance metrics with pacing against the guaranteed
+          commitment.
+        task: get_media_buy_delivery
+        schema_ref: "media-buy/get-media-buy-delivery-request.json"
+        response_schema_ref: "media-buy/get-media-buy-delivery-response.json"
+        doc_ref: "/media-buy/task-reference/get_media_buy_delivery"
+        stateful: true
+        expected: |
+          Return delivery metrics for the guaranteed media buy:
+          - Per-package delivery: impressions, clicks, spend, completion rates
+          - Pacing against guaranteed commitment: on track, ahead, behind
+          - Budget utilization: spent vs. committed
+          - SLA compliance: completion rate vs. guaranteed threshold
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          media_buy_ids:
+            - "mb_acme_q2_2026_guaranteed"
+          include_package_daily_breakdown: true
+
+        validations:
+          - check: response_schema
+            description: "Response matches get-media-buy-delivery-response.json schema"
+          - check: field_present
+            path: "media_buys"
+            description: "Response contains media buy delivery data"

package/storyboards/media_buy_non_guaranteed.yaml

@@ -0,0 +1,288 @@
+id: media_buy_non_guaranteed
+version: "1.0.0"
+title: "Non-guaranteed auction-based media buy"
+category: media_buy_non_guaranteed
+summary: "Seller agent for auction-based, non-guaranteed buying where the buyer sets bid prices and budgets."
+platform_types:
+  - social_platform
+  - dsp
+  - pmax_platform
+  - generative_dsp
+
+track: media_buy
+required_tools:
+  - create_media_buy
+narrative: |
+  You run a sell-side platform with auction-based inventory. Non-guaranteed buys don't
+  require IOs or human approval — the buyer sets a bid price and budget, and your platform
+  runs the auction. Delivery is best-effort based on bid competitiveness.
+
+  The buyer discovers products with floor prices and bid guidance, creates a buy with bid
+  prices per package, monitors win rates and pacing, and adjusts bids or budgets in-flight
+  to optimize performance.
+
+  This storyboard covers the non-guaranteed buying path — fast setup, no human approval,
+  real-time optimization through bid and budget adjustments.
+
+agent:
+  interaction_model: media_buy_seller
+  capabilities:
+    - sells_media
+    - supports_non_guaranteed
+    - auction_based
+  examples:
+    - "SSP with programmatic auction inventory"
+    - "Exchange-based publisher platform"
+    - "Open marketplace seller"
+
+caller:
+  role: buyer_agent
+  example: "Scope3 (DSP)"
+
+prerequisites:
+  description: |
+    The caller needs a brand identity and operator credentials. Non-guaranteed buys
+    typically have lower barriers to entry — no IO signing required. The test kit
+    provides a sample brand (Acme Outdoor) with bid parameters suitable for testing
+    the auction-based flow.
+  test_kit: "test-kits/acme-outdoor.yaml"
+
+phases:
+  - id: product_discovery
+    title: "Discover auction-based products"
+    narrative: |
+      The buyer sends a brief to discover your non-guaranteed inventory. Products
+      come back with delivery_type: non_guaranteed, floor prices, and bid guidance
+      that helps the buyer set competitive bids.
+
+    steps:
+      - id: get_products_brief
+        title: "Send a brief for non-guaranteed inventory"
+        narrative: |
+          The buyer describes what they want. Your platform returns non-guaranteed
+          products with auction mechanics: floor prices, recommended bid ranges,
+          estimated win rates at different bid levels, and available audience segments.
+        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"
+        stateful: false
+        expected: |
+          Return non-guaranteed products matching the brief. Each product should include:
+          - product_id: unique identifier
+          - name and description
+          - delivery_type: non_guaranteed
+          - pricing_models: auction-based pricing with floor_price and recommended bid range
+          - forecast: estimated impressions at different bid levels (best-effort)
+          - creative_format_ids: required creative formats
+          - targeting: available audiences and contexts
+
+        sample_request:
+          buying_mode: "brief"
+          brief: "Display and video inventory across sports and outdoor lifestyle sites. Q2 flight, $25K budget. Adults 25-54, US. Auction-based, looking for competitive CPMs."
+          brand:
+            domain: "acmeoutdoor.com"
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.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: field_present
+            path: "products[0].product_id"
+            description: "Each product has a product_id"
+          - check: field_present
+            path: "products[0].delivery_type"
+            description: "Each product declares delivery_type: non_guaranteed"
+
+  - id: create_buy
+    title: "Create non-guaranteed buy"
+    narrative: |
+      The buyer creates a media buy with bid prices per package. Since this is
+      non-guaranteed, no IO is required and no human approval is needed. The response
+      comes back as completed — the buy is immediately active and your platform starts
+      bidding in auctions on the buyer's behalf.
+
+    steps:
+      - id: create_media_buy
+        title: "Create a media buy with bid prices"
+        narrative: |
+          The buyer commits to non-guaranteed products with bid prices and budgets.
+          Your platform validates the bids against floor prices, confirms the buy
+          immediately (completed status), and begins auction participation.
+
+          Each package includes a bid_price that the buyer is willing to pay per unit
+          (CPM, CPC, etc.). The platform uses this to compete in auctions.
+        task: create_media_buy
+        schema_ref: "media-buy/create-media-buy-request.json"
+        response_schema_ref: "media-buy/create-media-buy-response.json"
+        doc_ref: "/media-buy/task-reference/create_media_buy"
+        stateful: true
+        expected: |
+          Return the media buy in completed status:
+          - media_buy_id: your platform's identifier
+          - status: confirmed or active (no async approval needed)
+          - confirmed_at: timestamp
+          - packages: confirmed line items with bid prices acknowledged
+          - valid_actions: pause, update_bid, get_delivery
+
+          Bids below floor_price should be rejected with a clear error.
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          brand:
+            domain: "acmeoutdoor.com"
+          start_time: "2026-04-01T00:00:00Z"
+          end_time: "2026-06-30T23:59:59Z"
+          packages:
+            - product_id: "sports_display_auction"
+              budget: 10000
+              bid_price: 8.50
+              pricing_option_id: "cpm_auction"
+              creative_assignments:
+                - creative_id: "display_trail_pro_300x250"
+            - product_id: "outdoor_video_auction"
+              budget: 15000
+              bid_price: 22.00
+              pricing_option_id: "cpm_auction"
+              creative_assignments:
+                - creative_id: "video_30s_trail_pro"
+
+        validations:
+          - check: response_schema
+            description: "Response matches create-media-buy-response.json schema"
+
+  - id: monitor_pacing
+    title: "Monitor win rates and pacing"
+    narrative: |
+      The non-guaranteed buy is live and bidding in auctions. The buyer checks
+      pacing to understand how competitive their bids are and whether the budget
+      is spending at the desired rate.
+
+    steps:
+      - id: get_media_buys_pacing
+        title: "Check buy status and pacing"
+        narrative: |
+          The buyer polls for the media buy status. Your platform returns the active
+          buy with pacing data — how much budget has been spent, win rates, and whether
+          the buy is on pace to exhaust the budget by the end of the flight.
+        task: get_media_buys
+        schema_ref: "media-buy/get-media-buys-request.json"
+        response_schema_ref: "media-buy/get-media-buys-response.json"
+        doc_ref: "/media-buy/task-reference/get_media_buys"
+        stateful: true
+        expected: |
+          Return the media buy with pacing data:
+          - media_buy_id: matches the buy created earlier
+          - status: active
+          - packages: line items with current spend, win rate, and pacing status
+          - valid_actions: update, pause, get_delivery
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          media_buy_ids:
+            - "mb_acme_q2_2026_auction"
+
+        validations:
+          - check: response_schema
+            description: "Response matches get-media-buys-response.json schema"
+          - check: field_present
+            path: "media_buys[0].status"
+            description: "Media buy has a status"
+
+  - id: adjust_bids
+    title: "Adjust bids and budget"
+    narrative: |
+      Based on pacing data, the buyer adjusts bids or budgets in-flight. If a package
+      is underspending (low win rate), the buyer increases the bid. If a package is
+      overspending, the buyer decreases the bid or caps the daily budget.
+
+    steps:
+      - id: update_media_buy
+        title: "Update bid prices and budget"
+        narrative: |
+          The buyer modifies the active media buy — adjusting bid prices, reallocating
+          budget between packages, or changing daily spend caps. Your platform applies
+          the updates immediately to the live auction participation.
+        task: update_media_buy
+        schema_ref: "media-buy/update-media-buy-request.json"
+        response_schema_ref: "media-buy/update-media-buy-response.json"
+        doc_ref: "/media-buy/task-reference/update_media_buy"
+        stateful: true
+        expected: |
+          Apply the updates and return the modified media buy:
+          - media_buy_id: matches the existing buy
+          - status: active (still running)
+          - packages: updated line items reflecting new bids and budgets
+          - Changes take effect immediately for subsequent auctions
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          media_buy_id: "mb_acme_q2_2026_auction"
+          packages:
+            - product_id: "sports_display_auction"
+              bid_price: 10.00
+              budget: 12000
+            - product_id: "outdoor_video_auction"
+              bid_price: 20.00
+              budget: 13000
+
+        validations:
+          - check: response_schema
+            description: "Response matches update-media-buy-response.json schema"
+
+  - id: delivery
+    title: "Delivery and auction metrics"
+    narrative: |
+      The buyer reviews delivery data including auction-specific metrics: win rates,
+      average clearing prices, and bid competitiveness across packages.
+
+    steps:
+      - id: get_delivery
+        title: "Check delivery with auction metrics"
+        narrative: |
+          The buyer requests delivery data for the active non-guaranteed media buy.
+          Your platform returns standard delivery metrics plus auction-specific data:
+          win rates, average clearing prices, bid-to-win ratios, and budget pacing.
+        task: get_media_buy_delivery
+        schema_ref: "media-buy/get-media-buy-delivery-request.json"
+        response_schema_ref: "media-buy/get-media-buy-delivery-response.json"
+        doc_ref: "/media-buy/task-reference/get_media_buy_delivery"
+        stateful: true
+        expected: |
+          Return delivery metrics for the non-guaranteed media buy:
+          - Per-package delivery: impressions, clicks, spend
+          - Win rate: percentage of auctions won per package
+          - Average clearing price: what the buyer actually paid vs. bid price
+          - Pacing: on track, ahead, behind relative to budget and flight dates
+          - Budget utilization: spent vs. committed
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.com"
+            operator: "pinnacle-agency.com"
+          media_buy_ids:
+            - "mb_acme_q2_2026_auction"
+          include_package_daily_breakdown: true
+
+        validations:
+          - check: response_schema
+            description: "Response matches get-media-buy-delivery-response.json schema"
+          - check: field_present
+            path: "media_buys"
+            description: "Response contains media buy delivery data"