Skip to main content
Generative production is an operation, not a separate format category. The output still conforms to a canonical creative contract such as image, video_hosted, native_in_feed, or sponsored_placement. Three tiers of generative creative: static output, optimized asset combinations, and context-generated variants

Discover a generation capability

Call the creative agent’s get_adcp_capabilities and inspect creative.supported_formats[]. A usable entry has build in operations and a canonical declaration compatible with the target product.
list_creative_formats is deprecated in 3.2. If you do not already know which creative agent to call, query the registry by canonical kind or exact publisher format option.

Generate from a brief

The agent returns a portable canonical manifest:
The manifest does not contain capability_id. Before trafficking to a product that requires exact option routing, add the appropriate publisher or product format_option_ref.

Transform existing creative

Provide an existing canonical manifest plus a target capability:
For priced or configurable generation services, discover a transformer_id through list_transformers. Its output_capability_ids[] declares the allowed targets; typed generation knobs go in config.

Multi-output generation

The response contains one canonical manifest per requested capability, in request order. Multi-output requests are atomic.

Seller-side and impression-time generation

A seller may accept a brief, catalog, or other structured inputs and compose the final ad later. The product’s canonical declaration expresses this through its slots and production parameters. The buyer submits a canonical manifest containing those inputs through sync_creatives; the seller/publisher runtime performs the impression-time composition. That runtime is not discovered as a creative-agent renderer. If the seller also exposes preview or pre-build operations, it advertises them explicitly in its own creative.supported_formats[].

Quality and refinement

  • quality controls build fidelity (draft or production).
  • preview_quality controls visualization fidelity independently.
  • Use refine_from_build_variant_id to refine a previously returned build leaf when the agent advertises refinement support.
  • max_variants and variant_axis request alternatives; keep_mode is advisory and does not change billing for produced leaves.

Failure handling

  • FORMAT_NOT_SUPPORTED: refresh get_adcp_capabilities and choose an advertised capability.
  • Field-attributed config.* error: correct the selected transformer’s typed configuration.
  • Target declaration mismatch: choose a capability whose full canonical envelope satisfies the product; matching only format_kind is insufficient.
  • Missing seller option: use the target product’s format_options[], not an agent-local capability ID, for package and manifest routing.