Skip to content

Conversation

@bmilekic
Copy link
Contributor

@bmilekic bmilekic commented Nov 18, 2025

Summary

This PR implements the complete Deals Protocol (renamed from Curation Protocol) to enable buyer agents to discover and activate pre-packaged and ad-hoc inventory deal packages from SSPs and curation platforms.

New Protocol: Deals Protocol

The Deals Protocol provides an alternative to the Media Buy Protocol for package-based buying, enabling:

  • Natural language deal discovery
  • Activation on SSP platforms (Magnite, Pubmatic, OpenX, Index Exchange, Microsoft Curate, etc.)
  • Support for PMP and Curated deal types
  • Integration with Signals Protocol for audience-targeted inventory packages

Tasks Implemented

get_deals

  • Discover deal packages using natural language descriptions
  • Simplified API: single deal_spec parameter (no filters, no deliver_to)
  • Returns deals with platforms array showing where they can be activated

activate_deal

  • Activate deals on specific SSP platforms
  • Atomic success/error responses
  • Uses deployment model similar to Signals Protocol

Core Schemas Added

Data Models (/static/schemas/v1/core/)

  • deal.json: Deal package with platforms, pricing, targeting, status
  • deal-pricing.json: Floor/Fixed/Market pricing with optional margins for curated deals
  • deal-targeting.json: Geo, devices, allow/block lists, segments (can reference Signal IDs)

Task Schemas (/static/schemas/v1/deals/)

  • get-deals-request.json: Natural language spec only
  • get-deals-response.json: Returns deals array with platform availability
  • activate-deal-request.json: Deal ID + destination platforms
  • activate-deal-response.json: Atomic response with deployments or errors

Architecture

Integration Flow:
Buyer Agent → Deals Agent → Signals Agent
(Deals Protocol) (Signals Protocol)

  • Deals Agents integrate with Signals Agents (using Signals Protocol)
  • Buyer Agents interact with Deals Agents (using Deals Protocol)
  • Parallel architecture to Media Buy Protocol's Sales Agent integration

Documentation

  • /docs/deals/overview.mdx: User-friendly protocol introduction with use cases
  • /docs/deals/specification.mdx: Complete RFC specification with task definitions and data models
  • Updated intro, README, and navigation to reflect Deals Protocol

Key Design Decisions

  1. Simplified get_deals: Natural language handles all filtering (no separate filters object)
  2. Platform availability in deals: Each deal includes platforms array showing where it can be activated
  3. SSP-focused: All examples use SSPs (not DSPs) as activation destinations
  4. Draft deals: Discovered deals have status "draft" until activated

Testing

✅ All schema validation tests pass (111 schemas validated)
✅ All example data validation tests pass
✅ TypeScript type checking passes

Changeset

A changeset has been included for minor version bump automation.

🤖 Generated with Claude Code

@bmilekic bmilekic force-pushed the deals-protocol branch 2 times, most recently from 22580e9 to 9ca575e Compare November 19, 2025 01:45
@@ -0,0 +1,33 @@
---
"adcontextprotocol": minor
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably should be major

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we assume the next significant release is 3.0 - thinking January - then that would make sense. we may want to do a beta branch before that. I started a product roadmap doc if you want to sketch this in there

@bmilekic
Copy link
Contributor Author

bmilekic commented Dec 5, 2025

This PR has been replaced by #273

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants