Optionalcontext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalgovernance_context?: stringSummary of the query that was executed
Total number of creatives matching filters (across all pages)
Number of creatives returned in this response
Optionalfilters_applied?: string[]List of filters that were applied to the query
Optionalsort_applied?: { field?: string; direction?: SortDirection }Sort order that was applied
Whether more results are available beyond this page
Optionalcursor?: stringOpaque cursor to pass in the next request to fetch the next page. Only present when has_more is true.
Optionaltotal_count?: numberTotal number of items matching the query across all pages. Optional because not all backends can efficiently compute this.
Array of creative assets matching the query
Optionalformat_summary?: Omit<Omit<{ [key: string]: number | undefined }, "bank">, "authentication"> & {Breakdown of creatives by format. Keys are agent-defined format identifiers, optionally including dimensions (e.g., 'display_static_300x250', 'video_30s_vast'). Key construction is platform-specific — there is no required format.
Optionalstatus_summary?: {Breakdown of creatives by status
Optionalprocessing?: numberNumber of creatives being processed
Optionalapproved?: numberNumber of approved creatives
Optionalpending_review?: numberNumber of creatives pending review
Optionalrejected?: numberNumber of rejected creatives
Optionalarchived?: numberNumber of archived creatives
Optionalerrors?: {Task-specific errors (e.g., invalid filters, account not found)
Optionalsandbox?: booleanWhen true, this response contains simulated data from sandbox mode.
Optionalext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalsummary: string
Governance context token issued by the account's governance agent during check_governance. Buyers attach it to governed purchase requests (media buys, rights acquisitions, signal activations, creative services); sellers persist it and include it on all subsequent governance calls for that action's lifecycle. An account binds to one governance agent (see sync_governance); governance is phased across
purchase/modification/delivery, not partitioned across specialist agents, so the envelope carries a single token for the full lifecycle.Value format: governance agents MUST emit a compact JWS per the AdCP JWS profile (see Security — Signed Governance Context). Sellers MAY verify; sellers that do not verify MUST persist and forward the token unchanged. In 3.1 all sellers MUST verify. Non-JWS values from pre-3.0 governance agents are deprecated.
This is the primary correlation key for audit and reporting across the governance lifecycle.