Skip to content

docs(creative): clarify creative-agent role in the sync_creatives flow #5821

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aleksUIX wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs(creative): clarify creative-agent role in the sync_creatives flow #5821

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1566da5
docs(creative): clarify creative-agent role in the sync_creatives flow
aleksUIX Jul 6, 2026
86c228f
chore: retrigger Argus review
aleksUIX Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/creative/implementing-creative-agents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading