From 1566da54980b691a0c7c465dff734932b400e8bf Mon Sep 17 00:00:00 2001 From: Aleksander Sekowski Date: Sun, 5 Jul 2026 18:28:06 -0700 Subject: [PATCH 1/2] docs(creative): clarify creative-agent role in the sync_creatives flow sync_creatives appears in both the Creative Protocol and the Media Buy Protocol and users conflate the two receiving roles. Add an Integration with the Media Buy Protocol section to the creative-agent implementation guide: sales agents accept sync_creatives to traffic creatives into media buys; creative agents optionally accept it as a library on-ramp; the build, traffic, deliver flow shows where each endpoint sits. Closes #5806. --- docs/creative/implementing-creative-agents.mdx | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/creative/implementing-creative-agents.mdx b/docs/creative/implementing-creative-agents.mdx index 9428c7bd50..a5fd5381aa 100644 --- a/docs/creative/implementing-creative-agents.mdx +++ b/docs/creative/implementing-creative-agents.mdx @@ -359,6 +359,21 @@ Accept creative asset uploads into your library. Implement this if your platform See [sync_creatives task reference](/docs/creative/task-reference/sync_creatives) for complete API specification. +## Integration with the Media Buy Protocol + +`sync_creatives` appears in both the Creative Protocol and the Media Buy Protocol, which is a common source of confusion. It is one task with one schema; what changes is the role of the agent receiving it: + +- **Sales agents** (Media Buy Protocol) accept `sync_creatives` to traffic creatives: upload into the seller's library, assign to packages in media buys, and run the seller's review pipeline. This is the call a buyer makes when activating a campaign. +- **Creative agents** (this guide) MAY accept `sync_creatives` as an optional library on-ramp: buyers push assets into your library so `build_creative` and `list_creatives` can reference them later. No packages or media buys are involved unless your platform also manages them. + +A typical buyer flow uses both endpoints in sequence: + +1. **Build**: the buyer calls your `build_creative` (or assembles a manifest by hand) and checks the result with `preview_creative`. +2. **Traffic**: the buyer sends the finished manifest to the sales agent's `sync_creatives`, with package assignments for the media buy. +3. **Deliver**: the sales agent validates the manifest against the format definition your agent published and serves the creative. + +Your creative agent is not in the path of step 2; buyers call the sales agent directly. Your format definitions are, because the sales agent validates incoming manifests against the formats you publish via `list_creative_formats`. Sales agents that implement the Creative Protocol alongside the Media Buy Protocol accept both kinds of calls at a single endpoint; see [Creative capabilities on sales agents](/docs/creative/sales-agent-creative-capabilities). + ## Validation best practices ### Manifest validation From 86c228fc0c5aee9f06833055367d73cb56eb4afd Mon Sep 17 00:00:00 2001 From: Aleksander Sekowski Date: Sun, 5 Jul 2026 18:39:00 -0700 Subject: [PATCH 2/2] chore: retrigger Argus review