diff --git a/.changeset/prerelease-pins-anonymous-discovery.md b/.changeset/prerelease-pins-anonymous-discovery.md new file mode 100644 index 00000000000..3b31fe47c95 --- /dev/null +++ b/.changeset/prerelease-pins-anonymous-discovery.md @@ -0,0 +1,5 @@ +--- +"adcontextprotocol": patch +--- + +Docs: state how buyers and sellers keep capability discovery working across releases. A buyer MUST send a prerelease `adcp_version` only to a peer whose `supported_versions` advertises that exact value, because a prerelease pin never negotiates down. A buyer SHOULD send discovery `get_adcp_capabilities` without a version pin, and on `VERSION_UNSUPPORTED` SHOULD retry without a pin or at a value from `supported_versions`, as the error code's recovery already says. A seller SHOULD serve `get_adcp_capabilities` without credentials; this becomes a MUST in 4.0. On MCP, a gateway or auth layer that allow-lists JSON-RPC methods SHOULD let `server/discover` (MCP `2026-07-28`), `initialize`, and `tools/list` through without credentials, so current MCP clients don't treat the agent as requiring sign-in before they can read capabilities. Covered in Versioning, Authentication, the MCP guide, the 3.3 release docs, and the 4.0 compatibility page. No schema changes. diff --git a/.changeset/refresh-3-3-release-docs-rc0.md b/.changeset/refresh-3-3-release-docs-rc0.md new file mode 100644 index 00000000000..d8d7c06685e --- /dev/null +++ b/.changeset/refresh-3-3-release-docs-rc0.md @@ -0,0 +1,5 @@ +--- +"adcontextprotocol": patch +--- + +Docs: bring the 3.3 release notes, What's new, the 3.2 to 3.3 migration guide, the prerelease program page (formerly the beta program page, same URL), Versions, and the 3.3 rows of Choose your SDK to `3.3.0-rc.0`. Adds rc.0 to the checkpoint and wire-pin tables, with the `3.3-rc` documentation selector. Covers the 2026-11-09 decision to open the schemas that were closed by accident, and the closed-schema triage that followed it: which beta fields stay in 3.3, which leave because they sit on deprecated tasks or would extend the commercial terms held closed until 4.0, and which move. Records the boolean form of `demographics` as deprecated, and covers the other rc.0 changes (origin-only `authorized_agents` URLs, declared-option creative conformance, TMP cache isolation, the registry-policy capability, video containers, carousel card image sizes, and loosened URL patterns). Replaces the remaining "closed schemas stay closed" wording in the 3.1 to 3.2 guide, the optimization-reporting page, and the daily-budget spec. Deprecated 3.3 features are described as expected to be removed in 4.0, with 3.3 supported for at least 12 months after 4.0 GA, instead of a notice-period promise. The SDK guidance records `@adcp/sdk` 17.0.0-beta.22 and Python `adcp` 10.0.0b15 on beta.5, Python `adcp` 9.6.2 with the A2A `input` fix on the 3.2 line, no SDK on rc.0 yet, and no Go or Java support for 3.3. The in-review table reflects the 3.3.0 milestone as of 2026-11-10. diff --git a/docs/building/by-layer/L0/mcp-guide.mdx b/docs/building/by-layer/L0/mcp-guide.mdx index 60ca626fa07..98126464f82 100644 --- a/docs/building/by-layer/L0/mcp-guide.mdx +++ b/docs/building/by-layer/L0/mcp-guide.mdx @@ -714,6 +714,10 @@ Buyer SDKs and generic transport wrappers may send envelope-level fields admitte A wrapper that raises `unexpected_keyword_argument` on `idempotency_key` will fail compliance against any buyer SDK that follows the envelope contract. See [security.mdx > Server-side tool wrapper conformance](/docs/building/by-layer/L1/security#server-side-tool-wrapper-conformance) for the normative rule. +### Let MCP discovery through without credentials + +A gateway or auth layer that allow-lists JSON-RPC methods SHOULD let `server/discover` (MCP `2026-07-28`), `initialize`, and `tools/list` through without credentials. A current MCP client calls them before any tool. If they require credentials, the client treats the agent as requiring sign-in and never reaches `get_adcp_capabilities`, which a seller SHOULD also serve without credentials ([Authentication](/docs/building/by-layer/L2/authentication)). Other tool calls keep their own authentication. + ### Tool Discovery ```javascript // List available tools — use get_adcp_capabilities for runtime feature detection diff --git a/docs/building/by-layer/L2/authentication.mdx b/docs/building/by-layer/L2/authentication.mdx index fcfca963717..466a5c5bf1d 100644 --- a/docs/building/by-layer/L2/authentication.mdx +++ b/docs/building/by-layer/L2/authentication.mdx @@ -5,17 +5,19 @@ description: "AdCP authentication guide: public vs authenticated operations, sta --- -AdCP uses a tiered authentication model where capability discovery is public, catalog discovery may be public, and protected reads and mutations require authentication. +AdCP uses a tiered authentication model where capability discovery should be public, catalog discovery may be public, and protected reads and mutations require authentication. ## When Authentication is Required ### Public Operations (No Authentication Required) -This operation works without credentials to bootstrap discovery: +A seller SHOULD serve this operation without credentials, so that a buyer can discover it before holding a key: - **`get_adcp_capabilities`** - Discover agent capabilities, portfolio, and supported features -**Rationale**: Publishers want potential buyers to discover their capabilities before establishing a business relationship. +**Rationale**: Publishers want potential buyers to discover their capabilities before establishing a business relationship. Buyers probe anonymously first, so a seller that requires credentials for capabilities can't be discovered by a buyer that doesn't have them yet. + +Anonymous capability discovery is a SHOULD in 3.3 and becomes a MUST in 4.0. Making it a MUST in a 3.x minor would add a new obligation on sellers. On MCP, a gateway or auth layer in front of the agent also has to let the transport's discovery methods through without credentials; see [Let MCP discovery through without credentials](/docs/building/by-layer/L0/mcp-guide#let-mcp-discovery-through-without-credentials). Product and signal discovery are seller-variable. Read `media_buy.anonymous_discovery` before calling `list_products` or `get_products` in discovery mode, and read `signals.anonymous_discovery` before calling `get_signals`. `true` means the call may succeed anonymously; `false` means credentials are required; absence means unspecified legacy behavior and the caller handles `AUTH_MISSING` if an anonymous probe is rejected. diff --git a/docs/building/by-layer/L4/choose-your-sdk.mdx b/docs/building/by-layer/L4/choose-your-sdk.mdx index bf8392305f5..fcff1d6e6c9 100644 --- a/docs/building/by-layer/L4/choose-your-sdk.mdx +++ b/docs/building/by-layer/L4/choose-your-sdk.mdx @@ -37,14 +37,17 @@ Legend: ✅ shipped · ⚠️ partial / role-dependent · ❌ not yet covered. T SDK 16 removes AdCP 2 support and moves Reliable Reporting storage out of `@adcp/sdk` into `@adcp/reporting-storage`; follow the [reporting storage package migration](https://github.com/adcontextprotocol/adcp-client/blob/main/docs/migration-reporting-storage-package.md) if you import storage from `@adcp/sdk/reporting/*`. SDK 15 tightens OAuth issuer binding and provider/storage defaults. Before upgrading an existing integration, follow the [SDK 15 OAuth migration and owner recovery guide](https://github.com/adcontextprotocol/adcp-client/blob/68614aa0ce84046c78d76dda9721ffbf9328639a/docs/migration-oauth-issuer-bindings.md). -### AdCP 3.3 beta support +### AdCP 3.3 prerelease support -Production stays on the 3.2 line and the packages above. For development and staging against the [3.3 beta](/docs/reference/3-3-beta): +Production stays on the 3.2 line and the packages above. For development and staging against the [3.3 prerelease](/docs/reference/3-3-beta): | SDK | Package | AdCP bundle | Roles and transports | Known limits | |---|---|---|---|---| | **`@adcp/sdk`** (TypeScript) | `17.0.0-beta.28` (npm `beta` dist-tag) | Signed `3.3.0-beta.6`; also bundles stable 3.2.8, 3.1.31 and 3.0.25. Earlier 3.3 betas require a matching external schema root | Buyer client and seller server, MCP and A2A | Identity and Web Bot Auth (`@adcp/sdk/identity-3.3`) remain experimental opt-ins. Use a Reliable Reporting storage release whose `@adcp/sdk` peer range matches this SDK. | | **`adcp`** (Python) | `10.0.0b17` (PyPI prerelease) | Signed `3.3.0-beta.6` | Buyer client and seller server, MCP and A2A | Negotiates only `3.3-beta.6`. Install the exact prerelease with `pip install --pre "adcp==10.0.0b17"`; for Reliable Reporting storage, use an `adcp-reporting-storage` prerelease whose `adcp` requirement matches this SDK. | +| Go, Java | — | No 3.3 prerelease | — | Not supported for 3.3. Test from these languages through raw-wire calls against the signed bundle. | + +SDK prereleases that adopt `3.3.0-rc.0` follow within days of the cut, and this table gains their rows when they publish. Until a row names rc.0, test rc.0 from its signed bundle and keep SDK-backed testing on beta.6. ```bash npm install @adcp/sdk@17.0.0-beta.28 diff --git a/docs/media-buy/media-buys/optimization-reporting.mdx b/docs/media-buy/media-buys/optimization-reporting.mdx index e12c483f505..268ad955e0c 100644 --- a/docs/media-buy/media-buys/optimization-reporting.mdx +++ b/docs/media-buy/media-buys/optimization-reporting.mdx @@ -424,7 +424,7 @@ The standard `available_metrics` enum is the closed protocol vocabulary. Vendor- A single vendor number can be built from very different inputs: set-top-box return-path data, ACR from smart TVs, a projected panel, or a fusion of them. `qualifier.attribution_methodology` says how exposure was tied to an outcome and `qualifier.completion_source` says who attested; neither says what was counted. The optional `vendor_metric_provenance[]` array on the same delivery-metrics object carries that, one entry per `vendor_metric_values` row, using the shared [`collection-mechanism`](https://adcontextprotocol.org/schemas/latest/enums/collection-mechanism.json) vocabulary: -- **Join key.** An entry carries the row's `vendor` and `metric_id` and, when the row has a `qualifier`, the identical `qualifier`. It is a sibling array rather than a field on the row because `vendor-metric-value.json` is a closed row envelope that a minor release does not extend (DR-0019, DR-0036). An entry that matches no row is ignored, and at most one entry may exist per key. +- **Join key.** An entry carries the row's `vendor` and `metric_id` and, when the row has a `qualifier`, the identical `qualifier`. It is a sibling array rather than a field on the row because 3.2.10 and earlier publish `vendor-metric-value.json` closed, so a 3.2 reader that validates strictly would reject a field on the row. The row's `qualifier` stays closed, because consumers join on it. An entry that matches no row is ignored, and at most one entry may exist per key. - `mechanisms[]` (required, at least one): the mechanisms whose events enter this row's value. A set — order carries no meaning and values MUST NOT repeat. Do not list every mechanism the vendor operates, or mechanisms used only for cross-checking. - `deduplicated` (optional boolean): `true` means the vendor deduplicated across all of the feeds behind the listed mechanisms (if only some were, omit the field and say so in the methodology). `false` means a simple union, so overlapping audiences may be double-counted; senders MUST send an explicit `false` rather than dropping it. Absent is *unspecified*, never `false`. SHOULD be omitted when the row derives from a single feed, but MAY be set on a single `mechanisms` entry when several feeds of that type were combined (e.g., return-path data from multiple MVPDs). The field does not say whether dedup was household-, person-, or device-level; that stays in the vendor's methodology documentation. - **Row scope.** An entry describes one row, and a row is one `(vendor, metric_id, qualifier)` per period, so `mechanisms` is the union across the row's aggregation scope. A vendor whose metrics draw on different mechanisms (a reach metric from STB plus panel, a tune-in metric from STB alone) is told apart per metric. Variance finer than the row, such as STB-only in dense metros and panel in thin DMAs, shows only on geo or other breakdown rows that carry their own provenance. Two rows with the same `(vendor, metric_id, qualifier)` and different provenance for the same scope are a seller bug. diff --git a/docs/reference/3-3-beta.mdx b/docs/reference/3-3-beta.mdx index 0b828240361..377cc13e99d 100644 --- a/docs/reference/3-3-beta.mdx +++ b/docs/reference/3-3-beta.mdx @@ -1,21 +1,23 @@ --- -title: AdCP 3.3 beta program -sidebarTitle: 3.3 beta program -description: "Where the AdCP 3.3 beta stands at beta.5, how to test a beta before SDK support or against the public test agent's preview, which SDK versions bundle which beta, and which proposals are still in review for 3.3." -"og:title": "AdCP — 3.3 beta program" +title: AdCP 3.3 prerelease program +sidebarTitle: 3.3 prerelease program +description: "Where the AdCP 3.3 prerelease stands at the first release candidate, rc.0: how to test it from the signed bundle or against the public test agent's preview, which SDK versions bundle which checkpoint, what left 3.3 before the release candidate, and which proposals are still in review." +"og:title": "AdCP — 3.3 prerelease program" --- -# AdCP 3.3 beta program +# AdCP 3.3 prerelease program -**Use the beta in development and staging, not production.** New production integrations should stay on AdCP 3.2 until 3.3 reaches general availability. Every beta is an immutable checkpoint, but later betas may change 3.3 surfaces before GA. +**Use the release candidate in development and staging, not production.** New production integrations should stay on AdCP 3.2 until 3.3 reaches general availability. Every prerelease is an immutable checkpoint, but a later release candidate may still change 3.3 surfaces before GA. -3.3 is a minor release with a deliberately short cycle. Its beta follows the same order as 3.2: the protocol first, then the SDKs. +3.3 is a minor release with a deliberately short cycle. Its prerelease follows the same order as 3.2: the protocol first, then the SDKs. -## Beta status +## Prerelease status -The latest checkpoint is **`3.3.0-beta.5`, published 2026-11-07**. Each beta is an immutable, signed checkpoint, and later betas may change 3.3 surfaces before GA. GA follows the first beta that meets every one of the GA criteria in [#8600](https://github.com/adcontextprotocol/adcp/issues/8600): SDK support for the latest beta, green storyboards, the closed-schema triage ([#8501](https://github.com/adcontextprotocol/adcp/issues/8501)), no open objections on consent items and decision records, and current release docs. The criteria stand as written: their consent closed on 2026-11-07 with no objections. The closed-schema triage lands after its own consent closes on 2026-11-13, and the GA-candidate beta follows in the week of 2026-11-16. +The latest checkpoint is **`3.3.0-rc.0`, the first release candidate, published 2026-11-16**. It follows seven betas, the last of them `3.3.0-beta.6` (2026-11-13). Each prerelease is an immutable, signed checkpoint. In beta.6, 3.3 opened the schemas that were closed by accident, and the closed-schema triage settled which beta features stay in 3.3 and which leave ([below](#closed-schema-triage-before-rc-0)). + +GA follows the first release candidate that meets every one of the GA criteria in [#8600](https://github.com/adcontextprotocol/adcp/issues/8600): SDK support for the latest prerelease, green storyboards, the closed-schema triage ([#8501](https://github.com/adcontextprotocol/adcp/issues/8501)), no open objections on consent items and decision records, and current release docs. The criteria stand as written: their consent closed on 2026-11-07 with no objections. The target for GA is the week of 2026-11-30, or the week of 2026-11-23 if every criterion passes first time. A later release candidate follows rc.0 if a correction needs adopter action. | Checkpoint | Published | Purpose | Who should test | |---|---|---|---| @@ -24,37 +26,39 @@ The latest checkpoint is **`3.3.0-beta.5`, published 2026-11-07**. Each beta is | `3.3.0-beta.2` | 2026-10-30 | Account change outcomes, seller offers, measurement provenance, structural capability bounds, the principal clarification, reporting-subscription convergence, and the withdrawal of definition pins, purchase rights, and installment selection | The same teams, against the withdrawn surfaces removed | | `3.3.0-beta.3` | 2026-10-31 | Live creative updates, the protocol envelope on every task response, money terms on resolved account requests, revocation as no access, and reporting-subscription coverage computable from the wire | The same teams | | `3.3.0-beta.4` | 2026-11-05 | Reporting-subscription coverage fixes (per-package `added_at`, a reduced grant as a loss of authority) and the probe reset, `replace` that transfers assignment settings, tracker-slot limits only where a format declares slots, `BUDGET_TOO_LOW` details, `creative.supports_provenance`, `opportunity` on explicit-package buys, undefined-property reporting, and the hold, account-request, and reporting-subscription storyboards | The same teams, and SDK maintainers adopting the two coverage rule changes | -| `3.3.0-beta.5` | 2026-11-07 | Experimental match keys for cross-publisher frequency capping, `sales-fixed-rate` promoted to stable, and the bundled Public Suffix List (DR-0037) | The same teams; this is the checkpoint the docs describe | +| `3.3.0-beta.5` | 2026-11-07 | Experimental match keys for cross-publisher frequency capping, `sales-fixed-rate` promoted to stable, and the bundled Public Suffix List (DR-0037) | Pinned adopters comparing beta.5 with beta.6 and rc.0 | +| `3.3.0-beta.6` | 2026-11-13 | Schemas open by default (DR-0036), the closed-schema triage, the versioning rules for what changes between releases, and every other change merged since beta.5 | SDK maintainers and adopters testing ahead of rc.0 | +| `3.3.0-rc.0` | 2026-11-16 | First release candidate: everything in beta.6, plus the prerelease pins, unpinned discovery, and anonymous capabilities guidance, declared `sync_creatives` assignment operations (#8997), audience targeting without member push (#8996), carousel card `cta_values` (#9001), inline `submitted` branches aligned with their status files (#8934), the `by_package` guidance (#8970), scope and `signing_keys` rules for several matching `authorized_agents` entries (#9011, #9017), three renamed experimental values (#8989), an omitted `human_review_required` accepted by campaign governance (#9007), compliance gates for `audience_buy_flow` and `inline_creatives_without_sync` (#9013, #9005), the public test agent's `3.3-beta.6` preview (#9018), and the Instagram, Facebook, Snapchat and X distribution identifier types (#8995) | Every team that tested a beta, SDK maintainers ingesting the bundle, and raw-wire implementers; this is the checkpoint the docs describe | -Beta.0 did not wait for the SDKs. A checkpoint is SDK-backed only after the matching SDK versions and integration evidence are published. `@adcp/sdk` 17.0.0-beta.11 is the first published SDK that bundles beta.3 ([SDK guidance](#sdk-guidance)). Three features that shipped in the betas are [withdrawn after beta.1](#withdrawn-after-beta-1). +Beta.0 did not wait for the SDKs. A checkpoint is SDK-backed only after the matching SDK versions and integration evidence are published. `@adcp/sdk` 17.0.0-beta.11 is the first published SDK that bundles beta.3 ([SDK guidance](#sdk-guidance)). Three features that shipped in the betas are [withdrawn after beta.1](#withdrawn-after-beta-1), and the [closed-schema triage](#closed-schema-triage-before-rc-0) removes further beta fields before rc.0. -`@adcp/sdk` 17.0.0-beta.18 through 17.0.0-beta.20 and Python `adcp` 10.0.0b12 support beta.4. `@adcp/sdk` 17.0.0-beta.21 through 17.0.0-beta.23 and Python `adcp` 10.0.0b13 through 10.0.0b16 support beta.5. `@adcp/sdk` 17.0.0-beta.24 and later and Python `adcp` 10.0.0b17 and later support beta.6 ([SDK guidance](#sdk-guidance)). +`@adcp/sdk` 17.0.0-beta.18 through 17.0.0-beta.20 and Python `adcp` 10.0.0b12 support beta.4. `@adcp/sdk` 17.0.0-beta.21 through 17.0.0-beta.23 and Python `adcp` 10.0.0b13 through 10.0.0b16 support beta.5. `@adcp/sdk` 17.0.0-beta.24 and later and Python `adcp` 10.0.0b17 and later support beta.6. No published SDK supports rc.0 yet: rc.0 is SDK-backed once new SDK prereleases bundle it ([SDK guidance](#sdk-guidance)). ## Know which version string to use The artifact version, wire pin, and documentation selector are related but not interchangeable: -| Surface | beta.0 | beta.1 | beta.2 | beta.3 | beta.4 | beta.5 | -|---|---|---|---|---|---|---| -| Protocol artifact | `3.3.0-beta.0` | `3.3.0-beta.1` | `3.3.0-beta.2` | `3.3.0-beta.3` | `3.3.0-beta.4` | `3.3.0-beta.5` | -| Git tag | `v3.3.0-beta.0` | `v3.3.0-beta.1` | `v3.3.0-beta.2` | `v3.3.0-beta.3` | `v3.3.0-beta.4` | `v3.3.0-beta.5` | -| `adcp_version` wire pin | `"3.3-beta.0"` | `"3.3-beta.1"` | `"3.3-beta.2"` | `"3.3-beta.3"` | `"3.3-beta.4"` | `"3.3-beta.5"` | -| Documentation selector | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | +| Surface | beta.0 | beta.1 | beta.2 | beta.3 | beta.4 | beta.5 | beta.6 | rc.0 | +|---|---|---|---|---|---|---|---|---| +| Protocol artifact | `3.3.0-beta.0` | `3.3.0-beta.1` | `3.3.0-beta.2` | `3.3.0-beta.3` | `3.3.0-beta.4` | `3.3.0-beta.5` | `3.3.0-beta.6` | `3.3.0-rc.0` | +| Git tag | `v3.3.0-beta.0` | `v3.3.0-beta.1` | `v3.3.0-beta.2` | `v3.3.0-beta.3` | `v3.3.0-beta.4` | `v3.3.0-beta.5` | `v3.3.0-beta.6` | `v3.3.0-rc.0` | +| `adcp_version` wire pin | `"3.3-beta.0"` | `"3.3-beta.1"` | `"3.3-beta.2"` | `"3.3-beta.3"` | `"3.3-beta.4"` | `"3.3-beta.5"` | `"3.3-beta.6"` | `"3.3-rc.0"` | +| Documentation selector | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-beta` | `3.3-rc` | -Only send a prerelease wire pin to a peer that advertises that exact value in `get_adcp_capabilities.adcp.supported_versions`. Prerelease pins are exact: a buyer pinned to `"3.3-beta.4"` must not silently negotiate to beta.5, and a stable `"3.2"` pin must not silently negotiate to a beta. +A buyer MUST send a prerelease wire pin only to a peer that advertises that exact value in `get_adcp_capabilities.adcp.supported_versions`. Prerelease pins are exact and never negotiate down: a peer that doesn't list `"3.3-beta.5"` answers a request pinned to it with `VERSION_UNSUPPORTED`, never with rc.0 or 3.2, and a stable `"3.2"` pin never resolves onto a prerelease. Send the discovery `get_adcp_capabilities` call without a pin (SHOULD), and on `VERSION_UNSUPPORTED` retry without a pin or at a value from `supported_versions` (SHOULD). See [Pre-release pins](/docs/reference/versioning#pre-release-pins). The `3.3-beta` documentation selector stays at beta.5, and `3.3-rc` advances with each release candidate. -## Test a beta without an SDK +## Test a prerelease without an SDK -Download the signed protocol bundle of the beta you test (the commands use the latest, `3.3.0-beta.5`; substitute another published checkpoint) rather than copying schemas from `main` or from the moving `/schemas/latest/` path: +Download the signed protocol bundle of the checkpoint you test (the commands use the latest, `3.3.0-rc.0`; substitute another published checkpoint) rather than copying schemas from `main` or from the moving `/schemas/latest/` path: ```bash -curl -fLO https://adcontextprotocol.org/protocol/3.3.0-beta.5.tgz -curl -fLO https://adcontextprotocol.org/protocol/3.3.0-beta.5.tgz.sha256 -shasum -a 256 -c 3.3.0-beta.5.tgz.sha256 -tar -xzf 3.3.0-beta.5.tgz +curl -fLO https://adcontextprotocol.org/protocol/3.3.0-rc.0.tgz +curl -fLO https://adcontextprotocol.org/protocol/3.3.0-rc.0.tgz.sha256 +shasum -a 256 -c 3.3.0-rc.0.tgz.sha256 +tar -xzf 3.3.0-rc.0.tgz ``` -The extracted `adcp-3.3.0-beta.5/` directory contains: +The extracted `adcp-3.3.0-rc.0/` directory contains: - `manifest.json`: release version, bundle contents, skills, and file count; - `schemas/`: source-shaped and bundled request/response schemas, including `schemas/manifest.json` for the task and capability inventory; @@ -69,18 +73,18 @@ Useful tests are: 1. Generate or refresh types from the pinned bundled schemas. 2. Validate representative requests and responses for the roles you implement, including the new 3.3 surfaces you plan to adopt: the `account_id` identity model and, if you support it, `request_account`; `status` on every response through the protocol envelope; `expected_confirmation_at`, vendor-metric `outcome_target` goals, `reporting_webhook.operation_id`, `media_buy.features.catalog_ingestion`, the DOOH `location` and `dooh_inventory_summary` fields, `sync_audiences` audience sizes, and the experimental spot, print, daypart, loudness, reporting-subscription, live-creative-update, match-key, and governance `budget.periods[]` fields. 3. Compare your advertised tools with `schemas/manifest.json`. -4. Exercise raw MCP or A2A calls with `adcp_version: "3.3-beta.5"` against a staging peer that advertises the same pin. -5. Run the compliance assets with a source-compatible runner if you maintain one. Do not weaken production authentication to accommodate a beta runner. +4. Exercise raw MCP or A2A calls with `adcp_version: "3.3-rc.0"` against a staging peer that advertises the same pin. +5. Run the compliance assets with a source-compatible runner if you maintain one. Do not weaken production authentication to accommodate a prerelease runner. ## Try the preview on the public test agent -The public test agent at `https://test-agent.adcontextprotocol.org` serves `3.3.0-beta.6` as an opt-in preview alongside its stable releases. It lists `"3.3-beta.6"` in `adcp.supported_versions` and serves the preview only to a request that pins exactly that value: +The public test agent at `https://test-agent.adcontextprotocol.org` serves `3.3.0-beta.6` as an opt-in preview alongside its stable releases. The preview moves to rc.0 once an `@adcp/sdk` prerelease that negotiates rc.0 publishes, which is expected within days of the cut; until then, this section describes the beta.6 preview. It lists `"3.3-beta.6"` in `adcp.supported_versions` and serves the preview only to a request that pins exactly that value: | Request | Served | |---|---| | `adcp_version: "3.3-beta.6"` | The preview. Responses echo `"3.3-beta.6"` and validate against the published `3.3.0-beta.6` schemas. | | `adcp_version: "3.2"`, `"3.3"`, or a later release | 3.2. A release pin never resolves onto a prerelease. | -| Any other 3.3 prerelease, such as the earlier preview `"3.3-beta.5"` | Never the preview. Prerelease pins match exactly. | +| Any other 3.3 prerelease, such as `"3.3-rc.0"` or the earlier preview `"3.3-beta.5"` | Never the preview. Prerelease pins match exactly. | | `adcp_major_version` alone, or no version | The route's stable default, never the preview. | ```bash @@ -121,11 +125,11 @@ Other products take the default: a hold that never contends. With `@adcp/sdk`, use 17.0.0-beta.24 or later, which negotiates exactly `3.3-beta.6`; with Python, use `adcp` 10.0.0b17 or later. Earlier 17.0.0 betas negotiate an older beta, so they settle on 3.2 with the test agent. -**The preview is experimental and can change without notice.** It follows the 3.3 beta that the current `@adcp/sdk` prerelease negotiates, so it can trail the latest published beta, and it moves when the SDK does. Once it moves, the old pin is no longer served. AAO can also switch the preview off, after which the agent serves only its stable releases. Use it to try 3.3 surfaces, not as a stable integration target. +**The preview is experimental and can change without notice.** It follows the 3.3 prerelease that the current `@adcp/sdk` prerelease negotiates, so it can trail the latest published checkpoint, and it moves when the SDK does. Once it moves, the old pin is no longer served. AAO can also switch the preview off, after which the agent serves only its stable releases. Use it to try 3.3 surfaces, not as a stable integration target. -**No 3.3 verification badge is issued from a beta.** A beta bundle is an implementation input, not a certification target, and prerelease grading runs are diagnostic, as they were for 3.2. +**No 3.3 verification badge is issued from a prerelease.** A beta or release-candidate bundle is an implementation input, not a certification target, and prerelease grading runs are diagnostic, as they were for 3.2. ## SDK support contract @@ -138,31 +142,47 @@ An SDK support claim must name all of the following: - known unsupported or raw-only surfaces; - install command and one tested validation command. -The SDK compatibility matrix lives in [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk). Until a row names support for a beta, treat that SDK's generated 3.3 types and validators for it as unavailable. Raw JSON calls may still be possible, but they are not equivalent to SDK support. +The SDK compatibility matrix lives in [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk). Until a row names support for a prerelease, treat that SDK's generated 3.3 types and validators for it as unavailable. Raw JSON calls may still be possible, but they are not equivalent to SDK support. -SDK maintainers should report protocol ambiguities against the [AdCP repository](https://github.com/adcontextprotocol/adcp/issues). Report SDK implementation bugs in the SDK's own repository. Accepted protocol fixes receive a changeset and ship in the next beta; a published beta is never rebuilt in place. +SDK maintainers should report protocol ambiguities against the [AdCP repository](https://github.com/adcontextprotocol/adcp/issues). Report SDK implementation bugs in the SDK's own repository. Accepted protocol fixes receive a changeset and ship in the next prerelease; a published prerelease is never rebuilt in place. ## SDK guidance -**TypeScript.** Use `@adcp/sdk` **17.0.0-beta.6 or later** (npm `beta` dist-tag) to test 3.3. The published prereleases bundle a signed AdCP release: 17.0.0-beta.6 bundles `3.3.0-beta.1`, 17.0.0-beta.10 bundles `3.3.0-beta.2`, 17.0.0-beta.11 through 17.0.0-beta.17 bundle `3.3.0-beta.3`, 17.0.0-beta.18 through 17.0.0-beta.20 bundle `3.3.0-beta.4`, 17.0.0-beta.21 through 17.0.0-beta.23 bundle `3.3.0-beta.5`, and 17.0.0-beta.24 and later bundle `3.3.0-beta.6`. Each negotiates only its own beta, so a buyer and seller on different betas settle on a stable release. Pin the exact SDK version, and send a prerelease `adcp_version` only to a peer that advertises that exact pin. `@adcp/sdk` 17 is a major release; read its [16 to 17 migration guide](https://github.com/adcontextprotocol/adcp-client/blob/main/docs/migration-16-to-17.md) first. +**rc.0.** TypeScript and Python prereleases that adopt `3.3.0-rc.0` follow within days of the cut; see [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk). GA needs SDK support for the latest release candidate. Until a row there names rc.0, test rc.0 from its signed bundle and keep SDK-backed testing on beta.6. + +**TypeScript.** Use `@adcp/sdk` **17.0.0-beta.6 or later** (npm `beta` dist-tag) to test 3.3. The published prereleases bundle a signed AdCP release: 17.0.0-beta.6 bundles `3.3.0-beta.1`, 17.0.0-beta.10 bundles `3.3.0-beta.2`, 17.0.0-beta.11 through 17.0.0-beta.17 bundle `3.3.0-beta.3`, 17.0.0-beta.18 through 17.0.0-beta.20 bundle `3.3.0-beta.4`, 17.0.0-beta.21 through 17.0.0-beta.23 bundle `3.3.0-beta.5`, and 17.0.0-beta.24 and later bundle `3.3.0-beta.6`. Each negotiates only its own prerelease, so a buyer and seller on different checkpoints settle on a stable release. Pin the exact SDK version, and send a prerelease `adcp_version` only to a peer that advertises that exact pin. `@adcp/sdk` 17 is a major release; read its [16 to 17 migration guide](https://github.com/adcontextprotocol/adcp-client/blob/main/docs/migration-16-to-17.md) first. -**Python.** `adcp` **10.0.0b17**, a PyPI prerelease (`pip install --pre "adcp==10.0.0b17"`), adopts the signed `3.3.0-beta.6` bundle and negotiates only `3.3-beta.6`; 10.0.0b13 through 10.0.0b16 adopt `3.3.0-beta.5`, and 10.0.0b12 adopts `3.3.0-beta.4`. Keep production-line work on the `adcp` 3.2 release. +**Python.** `adcp` **10.0.0b17**, a PyPI prerelease (`pip install --pre "adcp==10.0.0b17"`), adopts the signed `3.3.0-beta.6` bundle and negotiates only `3.3-beta.6`; 10.0.0b13 through 10.0.0b16 adopt `3.3.0-beta.5`, and 10.0.0b12 adopts `3.3.0-beta.4`. 10.0.0b15 reads the `input` member of an [AdCP A2A profile](/docs/building/by-layer/L0/a2a-profile-extension) invocation, so a Python seller answers `@adcp/sdk` buyers over A2A 1.0, and it refuses `parameters` on an activated invocation. Keep production-line work on the 3.2 line: `adcp` 9.6.2 (AdCP 3.2.7) reads `input` too, and refuses only an activated invocation that carries both members. -**Go.** Check the [adcp-go releases](https://github.com/adcontextprotocol/adcp-go/releases) for a published 3.3 support statement; this page names none. +**Go and Java.** Neither supports 3.3. No Go or Java release bundles a 3.3 prerelease, so test 3.3 from those languages through raw-wire calls against the signed bundle, and check the [adcp-go releases](https://github.com/adcontextprotocol/adcp-go/releases) for any later support statement. -Do not combine an SDK that bundles an earlier beta with a later wire pin unless that SDK explicitly documents forward compatibility. GA needs SDK support for the latest beta, so these versions will move; [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk) is the SDK matrix, and it can lag the npm dist-tag. +Do not combine an SDK that bundles an earlier prerelease with a later wire pin unless that SDK explicitly documents forward compatibility. These versions move with each checkpoint; [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk) is the SDK matrix, and it can lag the npm dist-tag. ## SDK convergence -A beta is the SDK-backed ecosystem checkpoint only when: +A prerelease is the SDK-backed ecosystem checkpoint only when: - every first-party SDK's support for it is marked supported, partial, or unavailable with an exact package version; -- accepted protocol feedback from the previous beta is merged; -- the integration scenarios below have run against the previous beta and identify any correction in the candidate; +- accepted protocol feedback from the previous checkpoint is merged; +- the integration scenarios below have run against the previous checkpoint and identify any correction in the candidate; - copy/paste installation and validation commands have been executed as published; - the cumulative migration guide and release notes describe any correction that requires adopter action. -After a beta is published, SDK maintainers ingest that signed bundle and publish an exact support statement or an explicit unsupported or partial result. Only after the matching buyer and seller scenarios pass is that beta the SDK-backed checkpoint. +After a prerelease is published, SDK maintainers ingest that signed bundle and publish an exact support statement or an explicit unsupported or partial result. Only after the matching buyer and seller scenarios pass is that prerelease the SDK-backed checkpoint. + +## Closed-schema triage before rc.0 + +On 2026-11-09 the working group decided that 3.x opens the schemas that were closed by accident ([DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md)). A schema stays closed for a structural reason, such as `oneOf` disjointness or a closed key set. `commercial_terms` and the term objects inside it, and `proposal-budget-constraint`, are held closed until 4.0. The [#8501](https://github.com/adcontextprotocol/adcp/issues/8501) triage then re-checked every beta feature that had been withdrawn because its schema was closed. A feature withdrawn only for that reason stays in 3.3. Two reasons still remove a field: it sits on a deprecated task or row (`get_products`, `create_media_buy`, `update_media_buy`, `sync_creatives` `assignments[]`), or it would extend a schema held closed until 4.0. The [migration guide](/docs/reference/migration/3-2-to-3-3#closed-schema-triage-what-stays-in-3-3) lists every field, and what to do if you built from a beta. + +| | Fields | Why | +|---|---|---| +| **Stays in 3.3** | `review_sla` on media-buy actions; minute dayparts and `time_granularity`; the spot-lifecycle capability fields; `collection_lists`; core gender targeting; `trackers` and `landing_page_url` on `assign` operations; `forced.proposal_id` and `arm: unable` on the test controller; `signing_profile` on notification configs | Their schemas open, so the withdrawal is moot | +| **Leaves 3.3** | Assignment `trackers` and `landing_page_url` on `sync_creatives` `assignments[]` and on package creative assignments; on `get_products`, `refine[].package`, the `refinement_applied[]` additions, `filters.target_audiences`, and `include_collections` with `collections`; on `create_media_buy` and `update_media_buy`, `predecessor_media_buy_id` and `lineage_reason`, `artifact_webhook.signing_profile`, `target_audiences`, and `start_requires_all_creatives_approved` | Deprecated surface. The live tasks keep these features where they already carry them: `assignment_operations`, `list_products`, `buy_products` and `accept_proposal`, and `control_media_buy` | +| **Moves within 3.3** | `execution_readiness` from `get_products` to `list_products`; `clock` and `business_calendar_id` from `sla-window` to the creative-review SLA; `available_installment_statuses` to the canonical reporting capabilities | The old home is deprecated or held closed until 4.0. `target_audiences` does not move to `list_products` `offer_filters` in 3.3; any change is 4.x | +| **Renamed in rc.0** | `input_required` → `input-required` (`media_buy.execution_readiness`), `click_through` → `clickthrough` (`creative.live_updates`), and `underdelivery` → `under_delivery` (`media_buy.delivery_projection`) ([#8989](https://github.com/adcontextprotocol/adcp/pull/8989)) | Each takes the spelling its stable or sibling counterpart already uses; there is no alias | +| **Planned for 4.0** | `metric_id` on performance standards; `price_adjustments` (`media_buy.price_adjustments`); `counting_mechanisms` on measurement terms; `target_audiences` on purchases | The legacy copy sits on a deprecated surface, and the canonical copy would extend the commercial terms, which are held closed until 4.0 | + +**In review, not in rc.0.** [#8854](https://github.com/adcontextprotocol/adcp/pull/8854) makes two of the triage's changes: it withdraws `metric_id` from `core/canonical-performance-standard.json`, `core/performance-standard.json`, and `required_performance_standards` in `core/product-offer-filters.json`, and it restores `evaluator` as a deprecated `x-entity-types` value. It has not merged, so rc.0's schemas still carry `metric_id` in those three places and still lack `evaluator`. Don't build on `metric_id`: the triage decided it leaves 3.3. ## Withdrawn after beta.1 @@ -172,7 +192,7 @@ Three features shipped in `3.3.0-beta.1` and are not part of 3.3. They leave the |---|---|---| | Definition pins: `commercial_terms.definition_pins[]`, the `definition_changed` reason, `drifted_pins[]`, `REFERENCE_DEFINITION_CHANGED`, the `definition_pin_probe` scenario, and the `definition_pin_drift` storyboard ([#7960](https://github.com/adcontextprotocol/adcp/pull/7960)) | beta.0 and beta.1 | Stop emitting and requiring them. A seller that emits pins to a peer on the later schema sends a field a closed `commercial_terms` rejects. The beta rule that sellers pin covered definitions no longer applies. | | Purchase rights (`media_buy.purchase_rights`): `purchases[].rights[]`, `brand/rights-scope.json`, and the `paid_amplification` and `content_reuse` values of `right-use` ([#8101](https://github.com/adcontextprotocol/adcp/pull/8101)) | beta.1 | Stop listing the feature id and emitting `rights[]`. Carry rights through `acquire_rights` until 4.0. | -| Installment selection (`media_buy.installment_selection`): `purchases[].installments[]` and `refine_proposals` `installment_changes` ([#8246](https://github.com/adcontextprotocol/adcp/pull/8246)) | beta.1 | Stop listing the feature id and emitting or accepting the fields. Installments on the canonical product and `holds[]` stay. | +| Installment selection (`media_buy.installment_selection`): `purchases[].installments[]` and `refine_proposals` `installment_changes` ([#8246](https://github.com/adcontextprotocol/adcp/pull/8246)) | beta.1 | Stop listing the feature id and emitting or accepting the fields. Installments on the canonical product and `holds[]` stay. rc.0 brings back the request side as experimental `media_buy.installment_refinement` (#8974); `purchases[].installments[]` stays planned for 4.0. | The [migration guide](/docs/reference/migration/3-2-to-3-3#withdrawn-from-3-3-planned-for-4-0) lists every surface removed, and [Planned for 4.0](/docs/reference/migration/v4-compatibility#planned-for-4-0-withdrawn-from-3-3) keeps the designs. @@ -188,18 +208,18 @@ Retain the exact protocol bundle, SDK package versions, capability responses, re ## What may still change -The [3.3.0 milestone](https://github.com/adcontextprotocol/adcp/milestone/10) is the live scope record for work that may still land during the beta cycle. Use these maintained GitHub views as the live record: +The [3.3.0 milestone](https://github.com/adcontextprotocol/adcp/milestone/10) is the live scope record for work that may still land before GA. Use these maintained GitHub views as the live record: - [Open 3.3 issues](https://github.com/adcontextprotocol/adcp/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.3.0) - [Open 3.3 pull requests](https://github.com/adcontextprotocol/adcp/pulls?q=is%3Aopen+milestone%3A3.3.0) - [Closed 3.3 milestone work](https://github.com/adcontextprotocol/adcp/milestone/10?closed=1) -Milestone assignment means **candidate for the 3.3 line**, not a commitment to any particular beta or GA. A change is included in a beta only when it is merged before that beta's tag. Items may be deferred, split, or moved to a later release as working groups resolve scope and interoperability risk. +Milestone assignment means **candidate for the 3.3 line**, not a commitment to any particular prerelease or GA. A change is included in a prerelease only when it is merged before that prerelease's tag. Items may be deferred, split, or moved to a later release as working groups resolve scope and interoperability risk. ### In review for 3.3 -**These are proposals, not features.** The first table lists the issues open in the 3.3.0 milestone on 2026-11-08 (six, not counting the [GA tracking issue](https://github.com/adcontextprotocol/adcp/issues/8600)), with the open pull request for each where one exists. The second lists the issues that were open at beta.3 and have since moved to a later milestone. An issue stays open while part of it is still in review, so a row can list merged work. Issues whose work has fully merged have been closed and are not listed; see [What's new](/docs/reference/whats-new-in-3-3) and the [release notes](/docs/reference/release-notes#version-3-3-0) for what they shipped. None is part of a beta unless it merges before that beta's tag. "Merged so far" names the slice that already shipped on `main`; the rest of the issue is still in review. The live lists are the [open 3.3 issues](https://github.com/adcontextprotocol/adcp/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.3.0) and [open pull requests](https://github.com/adcontextprotocol/adcp/pulls?q=is%3Aopen+is%3Apr+draft%3Afalse) and [drafts](https://github.com/adcontextprotocol/adcp/pulls?q=is%3Aopen+is%3Apr+draft%3Atrue). +**These are proposals, not features.** The first table lists the issues open in the 3.3.0 milestone on 2026-11-16 (four, not counting the [GA tracking issue](https://github.com/adcontextprotocol/adcp/issues/8600)), with the open pull request for each where one exists. The second lists the issues that were open at beta.3 and have since moved to a later milestone. An issue stays open while part of it is still in review, so a row can list merged work. Issues whose work has fully merged have been closed and are not listed; see [What's new](/docs/reference/whats-new-in-3-3) and the [release notes](/docs/reference/release-notes#version-3-3-0) for what they shipped. None is part of a prerelease unless it merges before that prerelease's tag. "Merged so far" names the slice that already shipped on `main`; the rest of the issue is still in review. The live lists are the [open 3.3 issues](https://github.com/adcontextprotocol/adcp/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.3.0) and [open pull requests](https://github.com/adcontextprotocol/adcp/pulls?q=is%3Aopen+is%3Apr+draft%3Afalse) and [drafts](https://github.com/adcontextprotocol/adcp/pulls?q=is%3Aopen+is%3Apr+draft%3Atrue). #### Decisions @@ -220,7 +240,7 @@ Four records document surfaces merged for beta.0 and are accepted (decided 2026- #### Open 3.3.0 milestone issues {/* - Regenerate at each beta cut: + Regenerate at each prerelease cut: gh issue list --repo adcontextprotocol/adcp --milestone 3.3.0 --state open --limit 200 --json number,title gh pr list --repo adcontextprotocol/adcp --state open --limit 200 --json number,title,isDraft,closingIssuesReferences,body One row per open milestone issue. Link the open PR that closes or references it, mark drafts, @@ -229,12 +249,12 @@ Four records document surfaces merged for beta.0 and are accepted (decided 2026- | Area | Issue | Topic | Open PR | Merged so far | |---|---|---|---|---| -| Commercial flow | [#7659](https://github.com/adcontextprotocol/adcp/issues/7659) | Price adjustments for buyer-selectable product dimensions | — | Experimental selection-dependent `price_adjustments` on fixed-price pricing options (#7955) | -| Delivery and measurement | [#7253](https://github.com/adcontextprotocol/adcp/issues/7253) | DOOH impression basis: typed tier, effective multiplier, and derivation link | [#8736](https://github.com/adcontextprotocol/adcp/pull/8736) (draft) | — | -| Delivery and measurement | [#8149](https://github.com/adcontextprotocol/adcp/issues/8149) | Reliable Reporting HTTPS push authenticates as the seller and holds no buyer secret | [#8793](https://github.com/adcontextprotocol/adcp/pull/8793) (draft) | — | -| Targeting and inventory | [#8375](https://github.com/adcontextprotocol/adcp/issues/8375) | Supported match keys in capabilities and `Product.identity` | — | Experimental `media_buy.supported_match_keys` and `Product.identity.match_keys` ([#8446](https://github.com/adcontextprotocol/adcp/pull/8446)), in beta.5 | -| Creative and brand | [#8107](https://github.com/adcontextprotocol/adcp/issues/8107) | `3gp`, `mpeg`, and `m4v` video containers | [#8668](https://github.com/adcontextprotocol/adcp/pull/8668) | — | -| Conformance and governance | [#8398](https://github.com/adcontextprotocol/adcp/issues/8398) | URL validation is over-specified: eight patterns where `^https://` is enough | [#8792](https://github.com/adcontextprotocol/adcp/pull/8792) | `setup_url` pattern relaxed to `^https://` with `format: uri` (#8548) | +| Delivery and measurement | [#7253](https://github.com/adcontextprotocol/adcp/issues/7253) | DOOH impression basis: typed tier, effective multiplier, and derivation link | [#8736](https://github.com/adcontextprotocol/adcp/pull/8736) | — | +| Conformance and governance | [#8501](https://github.com/adcontextprotocol/adcp/issues/8501) | Minor releases sometimes break older buyers: the closed-schema triage | [#8854](https://github.com/adcontextprotocol/adcp/pull/8854) | The versioning rules ([#8704](https://github.com/adcontextprotocol/adcp/pull/8704)), the opened schemas ([#8866](https://github.com/adcontextprotocol/adcp/pull/8866)), DR-0036 ([#8858](https://github.com/adcontextprotocol/adcp/pull/8858)), `sla-window` back to its 3.2 shape ([#8762](https://github.com/adcontextprotocol/adcp/pull/8762)), `available_installment_statuses` on the canonical product ([#8957](https://github.com/adcontextprotocol/adcp/pull/8957)), the `get_products` and `sync_creatives` `assignments[]` withdrawals ([#8758](https://github.com/adcontextprotocol/adcp/pull/8758)), and the `create_media_buy` and `update_media_buy` withdrawals ([#8767](https://github.com/adcontextprotocol/adcp/pull/8767)); the rest of the [triage](#closed-schema-triage-before-rc-0) | +| Conformance and governance | [#9014](https://github.com/adcontextprotocol/adcp/issues/9014) | Origin-only `agent_url` matching in the registry sync's authorization index | — | Origin-only matching in the validator and registry ([#9011](https://github.com/adcontextprotocol/adcp/pull/9011)) | +| Delivery and measurement | [#8987](https://github.com/adcontextprotocol/adcp/issues/8987) | Whether structural dimensions (`date`, `media_buy_id`, `account_id`) count as `unmapped_dimensions` in Reliable Reporting subscriptions | — | — | + +Closed since beta.5: match keys ([#8375](https://github.com/adcontextprotocol/adcp/issues/8375)), which shipped in beta.5, and over-specified URL patterns ([#8398](https://github.com/adcontextprotocol/adcp/issues/8398)), loosened in rc.0 by [#8792](https://github.com/adcontextprotocol/adcp/pull/8792). Also closed: Reliable Reporting push without buyer secrets ([#8149](https://github.com/adcontextprotocol/adcp/issues/8149), merged as [#8793](https://github.com/adcontextprotocol/adcp/pull/8793)), the three video containers ([#8107](https://github.com/adcontextprotocol/adcp/issues/8107), merged as [#8668](https://github.com/adcontextprotocol/adcp/pull/8668)), and inline `submitted` branches aligned with their published status files ([#8856](https://github.com/adcontextprotocol/adcp/issues/8856), merged as [#8934](https://github.com/adcontextprotocol/adcp/pull/8934)), origin-only `authorized_agents` matching in the validator and registry ([#8943](https://github.com/adcontextprotocol/adcp/issues/8943), merged as [#9011](https://github.com/adcontextprotocol/adcp/pull/9011)), and how `signing_keys` pins combine across matching entries ([#9016](https://github.com/adcontextprotocol/adcp/issues/9016), merged as [#9017](https://github.com/adcontextprotocol/adcp/pull/9017)), and the `audience_buy_flow` member-push gate ([#8998](https://github.com/adcontextprotocol/adcp/issues/8998), merged as [#9013](https://github.com/adcontextprotocol/adcp/pull/9013)), all in rc.0. Price adjustments ([#7659](https://github.com/adcontextprotocol/adcp/issues/7659)) moved to the 4.0 milestone: the experimental `price_adjustments` table (#7955) shipped in the betas and leaves 3.3 with the [triage](#closed-schema-triage-before-rc-0). #### Moved out of 3.3 since beta.3 @@ -262,18 +282,18 @@ These were open in the 3.3.0 milestone at beta.3 and have since moved, so they a | Conformance and governance | [#8093](https://github.com/adcontextprotocol/adcp/issues/8093) | Creator marketplace training fixtures | — | CreatorLoop seller and proposal fixtures (#8106) | | Conformance and governance | [#8201](https://github.com/adcontextprotocol/adcp/issues/8201) | 3.2 compact proposal storyboards and `sales-dooh` opt into fixture resolution | — | `olv` channel match for `outdoor_video_auction` discovery (#8211) | -Also open, without a 3.3 milestone issue: [#7958](https://github.com/adcontextprotocol/adcp/pull/7958) composable delivery breakdowns and [#7957](https://github.com/adcontextprotocol/adcp/pull/7957) metric aggregation semantics (both drafts; their issues moved to 3.4.0), [#7446](https://github.com/adcontextprotocol/adcp/pull/7446) TMP Context Match cache isolation (on the 3.3.0 milestone), and [#8346](https://github.com/adcontextprotocol/adcp/pull/8346) signed creative addons (open; asks the working group to reconsider a 3.4 deferral, and WG approval is pending). +Also open, without a 3.3 milestone issue: [#7958](https://github.com/adcontextprotocol/adcp/pull/7958) composable delivery breakdowns and [#7957](https://github.com/adcontextprotocol/adcp/pull/7957) metric aggregation semantics (both drafts; their issues moved to 3.4.0), and [#8346](https://github.com/adcontextprotocol/adcp/pull/8346) signed creative addons (open; asks the working group to reconsider a 3.4 deferral, and WG approval is pending). -## Known beta boundaries +## Known prerelease boundaries -- Experimental surfaces retain their [experimental-status contract](/docs/reference/experimental-status). A 3.3 beta does not graduate them to stable. The surfaces new in 3.3 are listed in the [release notes](/docs/reference/release-notes#experimental-surfaces-in-3-3). -- The `3.3-beta` documentation selector moves forward; pinned semver artifacts and documentation snapshots remain immutable. -- Stable schema aliases continue to resolve to stable releases during beta. Use pinned prerelease URLs when validating beta behavior. +- Experimental surfaces retain their [experimental-status contract](/docs/reference/experimental-status). A 3.3 prerelease does not graduate them to stable. The surfaces new in 3.3 are listed in the [release notes](/docs/reference/release-notes#experimental-surfaces-in-3-3). +- The `3.3-rc` documentation selector moves forward with each release candidate, and `3.3-beta` stays at beta.5; pinned semver artifacts and documentation snapshots remain immutable. +- Stable schema aliases continue to resolve to stable releases until 3.3 GA. Use pinned prerelease URLs when validating prerelease behavior. - The `media_buy_seller/unprovisioned_account_reference` storyboard is advisory until runner capability `14.1.0`. ## Report useful feedback -Include this information in a beta issue: +Include this information in a prerelease issue: - protocol artifact version and wire pin; - SDK name and version, or `raw wire`; @@ -282,7 +302,7 @@ Include this information in a beta issue: - schema path or JSON Pointer involved; - expected and actual behavior; - minimal redacted payload and validation error; -- whether the problem blocks interoperability on the beta you tested. +- whether the problem blocks interoperability on the checkpoint you tested. Never include credentials, signed URLs, bearer tokens, private keys, or live customer payloads. diff --git a/docs/reference/migration/3-1-to-3-2.mdx b/docs/reference/migration/3-1-to-3-2.mdx index e320c3b6616..f5671fe1606 100644 --- a/docs/reference/migration/3-1-to-3-2.mdx +++ b/docs/reference/migration/3-1-to-3-2.mdx @@ -330,12 +330,15 @@ idempotency key does not create replay identity across old and new task names. these tasks' request and response schemas closed, with `additionalProperties: false`. They also closed `canonical-proposal`, `canonical-product`, `product-discovery-criteria`, `proposal-refinement`, -`package-control`, and `opportunity-context`. -[DR-0019](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0019-closed-row-schemas-deliberate-class.md) -keeps roots and containers open, so later 3.2 patches reopen them. This is a -correction recorded in +`package-control`, and `opportunity-context`. 3.2.8 reopens them. On +2026-11-09 the working group decided that 3.x opens every schema that was +closed without a structural reason, so 3.2.11 +([#8864](https://github.com/adcontextprotocol/adcp/pull/8864)) opens the rest of the 3.2 schemas that were closed by +accident. Opening a +schema is a correction under [DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md) -([#8501](https://github.com/adcontextprotocol/adcp/issues/8501)). Every payload +([#8501](https://github.com/adcontextprotocol/adcp/issues/8501)), not a protocol +break. Every payload that was valid stays valid. A field that only the legacy Product defines, such as `format_ids`, `is_custom`, or `installments`, is still rejected on a canonical product. A root `feed_version` or `pricing_version` on a diff --git a/docs/reference/migration/3-2-to-3-3.mdx b/docs/reference/migration/3-2-to-3-3.mdx index 3ed9c320ab7..5eada5febce 100644 --- a/docs/reference/migration/3-2-to-3-3.mdx +++ b/docs/reference/migration/3-2-to-3-3.mdx @@ -1,14 +1,14 @@ --- title: Migrating from 3.2 to 3.3 sidebarTitle: 3.2 to 3.3 -description: "Role-based migration checklist for adopting the AdCP 3.3 beta while preserving 3.2 compatibility: normative narrowings, loosened guarantees, version-gated new fields, SDK-facing schema changes, experimental notices, deprecated result fields, one deprecated usage, and the deprecated account identity-rekey machinery." +description: "Role-based migration checklist for adopting the AdCP 3.3 release candidate while preserving 3.2 compatibility: normative narrowings, loosened guarantees, version-gated new fields, opened schemas, the closed-schema triage, SDK-facing schema changes, experimental notices, deprecated result fields, one deprecated usage, and the deprecated account identity-rekey machinery." "og:title": "AdCP — Migrating from 3.2 to 3.3" --- # Migrating from 3.2 to 3.3 -**3.3 is in its beta cycle.** This guide is current through `3.3.0-beta.5` (published 2026-11-07). Keep production traffic pinned to `"3.2"` while validating 3.3 in staging. See the [3.3 beta program](/docs/reference/3-3-beta) for artifact and SDK timing. +**3.3 is at its first release candidate.** This guide is current through `3.3.0-rc.0` (published 2026-11-16). Keep production traffic pinned to `"3.2"` while validating 3.3 in staging. If you built from a beta bundle, read the [closed-schema triage](#closed-schema-triage-what-stays-in-3-3) first: some beta fields leave 3.3 at rc.0. See the [3.3 prerelease program](/docs/reference/3-3-beta) for artifact and SDK timing. 3.3 is a minor release over 3.2. It adds optional fields, enum values, and capability declarations. No stable field, enum value, or task is removed; the one removal is the experimental `build_creative.evaluator.evaluator_id` source form (see [below](#experimental-creative-evaluator-drops-evaluator_id)). `seller_id` on event source and audience results is deprecated in favor of the new `platform_id` field. Natural-key account references after provisioning, the account identity-rekey machinery, and condition (b) of `request_signature_required` are also deprecated (see [Deprecations](#deprecations)). A caller opts into 3.3 only after the peer advertises the exact release in `supported_versions`. Existing 3.2 integrations that need nothing else can stay pinned to `"3.2"`. @@ -19,7 +19,7 @@ Read these first: - [Brand JSON size cap rises to 2 MiB](#brand-json-size-cap-rises-to-2-mib), [audience match counts](#audience-match-counts-may-be-absent), [audience targeting without member push](#audience-targeting-without-member-push), and the [4 MiB response-size default](#client-response-size-default-rises-to-4-mib): four loosened guarantees, so a 3.2 peer can reject or misread what a 3.3 peer sends. - [Recommended: bound agent response size](#recommended-bound-agent-response-size): a new SHOULD that tightens what an adopting buyer accepts. - [Send only to 3.3 peers](#send-only-to-3-3-peers): new fields a 3.2 validator rejects. -- [Deprecations](#deprecations): `seller_id` on event source and audience results, `principal_kind` and `expected_principal_kind` on the principal tasks, the natural-key account reference after provisioning, the account identity-rekey machinery (`identity_updates`, `operator_identity`, `ACCOUNT_MOVED`, `ACCOUNT_IDENTITY_CONFLICT`, `stable_account_id`), and condition (b) of `request_signature_required`, and the boolean form of `demographics`; removal no earlier than 4.0. +- [Deprecations](#deprecations): `seller_id` on event source and audience results, `principal_kind` and `expected_principal_kind` on the principal tasks, the natural-key account reference after provisioning, the account identity-rekey machinery (`identity_updates`, `operator_identity`, `ACCOUNT_MOVED`, `ACCOUNT_IDENTITY_CONFLICT`, `stable_account_id`), and condition (b) of `request_signature_required`, and the boolean form of `demographics`; each is expected to be removed in 4.0. - [SDK and code-generator maintainers](#sdk-and-code-generator-maintainers): schema-shape changes that alter generated types. Everything else is an optional declaration or a clarification. Agent identity (DR-0023) and demand-side grants (DR-0025) have their own role-by-role guide, [Migrating agent identity in AdCP 3.3](/docs/reference/migration/agent-identity-3-3). For the feature narrative, start with [What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3). @@ -28,15 +28,16 @@ Everything else is an optional declaration or a clarification. Agent identity (D ## Upgrade checklist + | Step | Who | Action | |---|---|---| -| 1 | Everyone | Keep production on `"3.2"`; choose an exact 3.3 beta artifact for staging. | -| 2 | SDK and codegen maintainers | Generate from the signed `3.3.0-beta.5` protocol tarball (the latest checkpoint), not `main` or `/schemas/latest/`. | +| 1 | Everyone | Keep production on `"3.2"`; choose an exact 3.3 prerelease artifact for staging. | +| 2 | SDK and codegen maintainers | Generate from the signed `3.3.0-rc.0` protocol tarball (the latest checkpoint), not `main` or `/schemas/latest/`. | | 3 | SDK and codegen maintainers | Treat `daypart_targets[].start_hour` / `end_hour` as optional in generated types (#8025). | | 4 | SDK and codegen maintainers | Resolve `#/$defs/Provenance` in bundled schemas instead of expecting inlined provenance (#7950, already in 3.2.4). | | 5 | SDK and codegen maintainers | Expect stricter response validation of `compact-task-submitted.json` (#7946, already in 3.2.4). | | 6 | Sellers and agents | Advertise the exact prerelease in `adcp.supported_versions` and echo the release actually served. | -| 7 | Buyers | Send `adcp_version: "3.3-beta.N"` only after exact capability discovery; never silently move between beta pins. | +| 7 | Buyers | Send a prerelease pin such as `adcp_version: "3.3-rc.0"` only after exact capability discovery; never silently move between prerelease pins. | | 8 | Sellers that provision accounts lazily | Move provisioning off discovery tasks. | | 9 | Signing and verifying implementations | Check agent resolution and pinned keys against the list below; apply the A2A hardening clauses. | | 10 | Verifiers that fetch brand.json | Raise the brand.json body cap from 256 KiB to 2 MiB; leave JWKS and capabilities caps unchanged. | @@ -55,7 +56,7 @@ Everything else is an optional declaration or a clarification. Agent identity (D | 23 | Sellers and buyers of event sources and audiences | Sellers emit `platform_id` and the deprecated `seller_id` with identical values; buyers prefer `platform_id`. | | 24 | Sellers with a media-buy, account or creative revision | Advance it on every committed change from any origin, including `sync_creatives` assignments and ingested connected-platform changes; add `origin` to `history` entries; optionally return `seller_revision` on `list_creatives`. | | 25 | Buyers that update media buys | Pass the latest `revision`, and expect `CONFLICT` after a seller or connected-platform change; re-read and retry. | -| 26 | Compliance operators | Use each 3.3 beta bundle for protocol feedback; as for 3.2, prerelease grading runs are diagnostic, not a badge. | +| 26 | Compliance operators | Use each 3.3 prerelease bundle for protocol feedback; as for 3.2, prerelease grading runs are diagnostic, not a badge. | | 27 | Buyers and sellers of hosted video or audio | Optionally move playback trackers from `event: custom` to the new `pixel_tracker` playback events. | | 28 | Users of the experimental `creative.evaluator` surface | Replace `evaluator_id` with an allowlisted `agent_url` or inline `exemplars` ([details](#experimental-creative-evaluator-drops-evaluator_id)). | | 29 | Creative agents that advertise `creative.supports_refinement` | Retain each leaf's compliance inputs for as long as the leaf, apply them to every refinement, and never treat a refined leaf as approved ([details](#refinement-carries-compliance-forward)). | @@ -72,9 +73,24 @@ Everything else is an optional declaration or a clarification. Agent identity (D | 40 | Agents that publish `get_adcp_capabilities` | Stay within the structural bounds; do not design to a byte figure ([details](#capabilities-are-bounded-by-structure)). | | 41 | Sellers of creatives that are serving | Optionally declare `creative.live_updates` (experimental) and refuse undeclared changes with `CREATIVE_LIVE_UPDATE_UNSUPPORTED` ([details](#live-creative-updates-experimental)). | | 42 | Buyers and sellers of reporting | Adopt principal-level reporting subscriptions (experimental) and compute coverage from the wire. From beta.4, sellers emit `packages[].added_at` on packages added after confirmation, treat a grant reduced without `get_reporting_status` as a loss of authority, and list `reset_state` with the probe ([details](#reporting-subscriptions-experimental)). | -| 43 | Sellers that adopt the commercial experiments | Gate [seller offers, price adjustments, execution readiness, gender targeting, signal pricing groups, provider-initiated delivery, and measurement provenance](#commercial-and-targeting-experiments) on the negotiated version and the feature id. | +| 43 | Sellers that adopt the commercial experiments | Gate [seller offers, execution readiness, gender targeting, signal pricing groups, provider-initiated delivery, and measurement provenance](#commercial-and-targeting-experiments) on the negotiated version and the feature id. | | 44 | Sellers that keep package records | Retain packages on canceled and completed buys, and start approved creatives by default when others are pending review ([details](#canceled-and-completed-buys-keep-their-packages)). | -| 45 | Sellers and buyers of `sync_creatives` `assignment_operations` | Sellers list exactly the operations they accept in `creative.assignment_operations`, list `replace` if they declare `creative.live_updates`, and list `assign` if they sell through `buy_products` or `accept_proposal` with a creative library. Buyers send only listed operations ([details](#sellers-declare-the-assignment-operations-they-accept)). | +| 45 | Sellers, buyers, and SDKs built from a beta bundle | Stop emitting and accepting the beta fields that leave 3.3 at rc.0, and move the ones that change home ([closed-schema triage](#closed-schema-triage-what-stays-in-3-3)). | +| 46 | SDK and codegen maintainers, and anyone with a hand-written validator | Regenerate from rc.0: most schemas are now open, so generated types gain index signatures and stop rejecting unknown fields. Keep any rejection you relied on as your own check ([SDK changes](#sdk-and-code-generator-maintainers)). | +| 47 | Buyers and sellers that use overlay demographics | Send the object form `{ "age": true }`, not boolean `demographics: true`, and keep accepting `true` ([deprecations](#deprecations)). | +| 48 | Buyers | Send a prerelease pin only to a peer that advertises it, send discovery `get_adcp_capabilities` unpinned, and retry unpinned or at a listed version on `VERSION_UNSUPPORTED` ([details](#prerelease-pins-unpinned-discovery-and-anonymous-capabilities)). | +| 49 | Sellers | Serve `get_adcp_capabilities` without credentials (a MUST in 4.0). On MCP, let `server/discover`, `initialize`, and `tools/list` through your gateway without credentials ([details](#prerelease-pins-unpinned-discovery-and-anonymous-capabilities)). | +| 50 | Sellers with a creative library | Accept a creative that conforms to the format option it targets; enforce only declared limits ([details](#sellers-accept-creatives-that-conform-to-the-declared-format-option)). | +| 51 | Validators, TMP providers, and registries that read `adagents.json` | Let an origin-only `authorized_agents[].url` authorize the agent at any path on that origin ([`adagents.json`](/docs/governance/property/adagents)). | +| 52 | Buyers, sellers, and governance agents that accept signed terms | Refuse terms carrying a member you cannot interpret (`unrecognized_terms` or `UNRECOGNIZED_TERMS`), and compute `terms_digest` over the bytes as received ([details](#accepting-signed-terms-binds-every-member)). | +| 53 | Sellers offering Reliable Reporting managed delivery | Hold no caller-issued secret for any pattern; push rows through `reporting_webhook`, and sign every `https_put` request under the Web Bot Auth profile ([details](#reliable-reporting-managed-delivery-holds-no-buyer-secret)). | +| 54 | Media-buy sellers | Optionally declare `media_buy.supported_delivery_types`, and return only products with a listed `delivery_type` when you do ([#8458](https://github.com/adcontextprotocol/adcp/pull/8458)). | +| 55 | Sellers publishing Reliable Reporting report definitions | At `contract_version` `1.2`, include `package_id` whenever `dimensions` include `media_buy_id`, and in `reporting_profile.primary_keys`. Callers pinned below 3.3 MUST be served `1.0` or `1.1` offerings ([details](#per-package-rows-in-reliable-reporting-report-definitions)). | +| 56 | Sellers that accept targeting; buyers that send it | Sellers: accept `geo_value_labels` and geo-entry `value_labels` without rejecting the request, never target from them, and compare codes only. Buyers: send `geo_value_labels` only to 3.3 peers ([details](#display-labels-for-geo-targeting-codes)). | +| 57 | Sellers and buyers of `sync_creatives` `assignment_operations` | Sellers list exactly the operations they accept in `creative.assignment_operations`, list `replace` if they declare `creative.live_updates`, and list `assign` if they sell through `buy_products` or `accept_proposal` with a creative library. Buyers send only listed operations ([details](#sellers-declare-the-assignment-operations-they-accept)). | +| 58 | Sellers that answer `get_media_buy_delivery` | Return at least one `by_package` row per media buy, one per package, and omit a buy you can't report and return an error rather than an empty `by_package` ([#8970](https://github.com/adcontextprotocol/adcp/pull/8970)). `by_package: []` stays valid in 3.x; requiring a row is proposed for 4.0 ([#8973](https://github.com/adcontextprotocol/adcp/issues/8973)). | +| 59 | Sellers, buyers, and SDKs that use `media_buy.execution_readiness`, `creative.live_updates`, or `media_buy.delivery_projection` | Send and accept the renamed values: `input-required` (was `input_required`), `clickthrough` (was `click_through`), and `under_delivery` (was `underdelivery`). There is no alias ([details](#three-experimental-values-renamed)). | +| 60 | Campaign governance agents (`governance.campaign`) | Accept a `sync_plans` plan that omits `human_review_required` and derive the flag from its resolved policies; keep rejecting an explicit `false`. Reject `flight.end` not after `flight.start`, and repeated or colliding policy IDs, with `INVALID_REQUEST` ([#9007](https://github.com/adcontextprotocol/adcp/pull/9007)). | ## Withdrawn from 3.3, planned for 4.0 @@ -97,12 +113,84 @@ A seller no longer pins definitions, re-verifies pins at finalize, or fails `acc ### Installment selection (published in beta.1, removed after beta.1) -[#8246](https://github.com/adcontextprotocol/adcp/pull/8246) merged on 2026-10-24 and shipped in `3.3.0-beta.1` as experimental `media_buy.installment_selection`: `purchases[].installments[]`, and `installment_changes` with `unsatisfied_installment_changes` on `refine_proposals`. All are removed, along with `core/installment-change-set.json` and the `installment_changes` value of `proposal_refinement.supported_dimensions`. A seller that listed the feature id stops listing it. Installments on the canonical product and `holds[]` stay in 3.3. A purchase buys the product as offered, which is its complete installment set when it declares one. +[#8246](https://github.com/adcontextprotocol/adcp/pull/8246) merged on 2026-10-24 and shipped in `3.3.0-beta.1` as experimental `media_buy.installment_selection`: `purchases[].installments[]`, and `installment_changes` with `unsatisfied_installment_changes` on `refine_proposals`. All are removed after beta.1, along with `core/installment-change-set.json` and the `installment_changes` value of `proposal_refinement.supported_dimensions`. A seller that listed `media_buy.installment_selection` stops listing it. Installments on the canonical product and `holds[]` stay in 3.3. A purchase buys the product as offered, which is its complete installment set when it declares one. + +**The request side returns in rc.0, under a new feature id.** Experimental `media_buy.installment_refinement` ([#8974](https://github.com/adcontextprotocol/adcp/pull/8974)) brings back `installment_changes` on `refine_proposals` (`core/installment-change-set.json`), `unsatisfied_installment_changes` on its result rows, and the `installment_changes` value of `supported_dimensions`, on schemas that are now open. The seller answers a selection with a product whose `installments[]` is exactly the chosen set, so `terms_digest` binds the `product_id` as before and every 3.x buyer reads the purchase the way it already does. `purchases[].installments[]` stays planned for 4.0 ([Adopt by capability](#installment-selection-and-per-installment-creatives-experimental)). ### Where the designs are kept The designs are preserved for 4.0 in [Planned for 4.0](/docs/reference/migration/v4-compatibility#planned-for-4-0-withdrawn-from-3-3) and in the merge commits of #7960, #8101, and #8246. +## Closed-schema triage: what stays in 3.3 + +On 2026-11-09 the working group decided that 3.x opens the schemas that were closed by accident ([Schemas are open by default](#schemas-are-open-by-default)). The [#8501](https://github.com/adcontextprotocol/adcp/issues/8501) triage then re-checked every beta feature that had been withdrawn, or proposed for withdrawal, because its schema was closed. It applied three reasons, in this order: + +1. **Deprecated surface.** A field on a deprecated task or row leaves, whatever its schema: `get_products`, `create_media_buy`, `update_media_buy`, `sync_creatives` `assignments[]`, and package creative assignments. The live tasks keep the feature where they already carry it. +2. **Held closed until 4.0.** `commercial-terms` and the term objects inside it, and `proposal-budget-constraint`, are held closed until 4.0. A field that would extend one of them leaves, and waits for 4.0. +3. **Closure only.** The withdrawal is moot, and the feature stays in 3.3. + +Only the fields below change between beta.5 and rc.0 because of the triage, and each change first shipped in beta.6. The three features withdrawn after beta.1 stay withdrawn ([above](#withdrawn-from-3-3-planned-for-4-0)). + +**In review, not in rc.0.** [#8854](https://github.com/adcontextprotocol/adcp/pull/8854) makes two of the triage's changes: it withdraws `metric_id` from `core/canonical-performance-standard.json`, `core/performance-standard.json`, and `required_performance_standards` in `core/product-offer-filters.json`, and it restores `evaluator` as a deprecated `x-entity-types` value. It has not merged, so rc.0's schemas still carry `metric_id` in those three places and still lack `evaluator`. Don't build on `metric_id`: the triage decided it leaves 3.3. + +### Stays in 3.3 + +| Field | Where | +|---|---| +| `review_sla` | `core/canonical-media-buy-action-fields.json` and `core/media-buy-available-action.json` | +| `start_time`, `end_time`, `time_granularity` | Daypart entries, and the overlay requirement and support objects (`media_buy.daypart_granularity`) | +| `available_statuses`, `supports_break_position` | `core/spot-reporting-capability.json` (`media_buy.spot_lifecycle`) | +| `collection_lists`, `collection_lists_exclude` | `core/targeting-overlay-requirements.json` (`media_buy.collection_lists`) | +| `gender` | Overlay `demographics` (`media_buy.gender_targeting`). Boolean `demographics` is [deprecated](#deprecations). | +| `trackers`, `landing_page_url` | The `assign` operation in `sync_creatives` `assignment_operations` | +| `forced.proposal_id`, `forced.arm: unable` | `comply_test_controller` responses | +| `signing_profile` | `core/notification-config.json` and `core/agent-notification-config.json` | + +### Leaves 3.3: deprecated surface + +| Field | Leaves | The feature stays on | +|---|---|---| +| `trackers`, `landing_page_url` | `sync_creatives` `assignments[]`, and package creative assignments (`core/creative-assignment.json`) on `create_media_buy` and `update_media_buy` | `sync_creatives` `assignment_operations` | +| `refine[].package`, and `result_product_id`, `resolved_start_time`, `resolved_end_time` on `refinement_applied[]` | `get_products` | No 3.3 task. The exact-package availability check ([#8468](https://github.com/adcontextprotocol/adcp/pull/8468)) needs a home on a live task. | +| `include_collections`, `collections` | `get_products` | `list_products`, `request_proposals`, and `refine_proposals` | +| `filters.target_audiences` | `get_products` | No 3.3 task. `list_products` `offer_filters` stays as it is in 3.3, and any change is 4.x, so `media_buy.audience_evidence_targets` has no 3.3 surface. | +| `predecessor_media_buy_id`, `lineage_reason` | `create_media_buy` | `buy_products`, `accept_proposal`, and `get_media_buys` (`media_buy.lineage`) | +| `artifact_webhook.signing_profile` | `create_media_buy` | No other task | +| `start_requires_all_creatives_approved` | Packages on `create_media_buy` and `update_media_buy` | `control_media_buy` package controls (`media_buy.features.creative_start_policy`) | +| `target_audiences` | Packages on `create_media_buy` and `update_media_buy` | Purchases, in 4.0 ([below](#leaves-3-3-held-closed-until-4-0)) | +| `metric_id` | `core/performance-standard.json`, and `required_performance_standards` in `core/product-offer-filters.json` | Performance standards, in 4.0 ([below](#leaves-3-3-held-closed-until-4-0)). Still in the rc.0 schemas: the withdrawal, [#8854](https://github.com/adcontextprotocol/adcp/pull/8854), is in review. | + +### Leaves 3.3: held closed until 4.0 + +| Field | Why it waits | +|---|---| +| `metric_id` on `core/canonical-performance-standard.json` | The canonical performance standard is one of the commercial terms held closed until 4.0. Still in the rc.0 schema: the withdrawal, [#8854](https://github.com/adcontextprotocol/adcp/pull/8854), is in review. | +| `price_adjustments` (`media_buy.price_adjustments`) | Its 3.3 home is the legacy `get_products` pricing option, a deprecated surface, and `canonical-pricing-option` is held closed until 4.0. The whole experiment waits for 4.0. | +| `counting_mechanisms` on `measurement_terms` (`media_buy.measurement_provenance`) | `measurement_terms` sits on deprecated tasks, and the canonical measurement terms are held closed until 4.0. `vendor_metric_provenance[]` on delivery metrics stays in 3.3. | +| `target_audiences` on purchases | A purchase records its terms in `product-purchase.json`, which is held closed until 4.0. | + +### Moves within 3.3 + +| Field | From | To | +|---|---|---| +| `include_execution_readiness`, `execution_readiness` | `get_products` | `list_products` (`media_buy.execution_readiness`) | +| `clock`, `business_calendar_id` | `core/sla-window.json`, which returns to its 3.2 shape because it sits inside the commercial terms held closed until 4.0 (`change_terms[].processing_sla`) | The creative-review SLA (`creative-review-sla`) | +| `available_installment_statuses` | `core/reporting-capabilities.json` | `core/canonical-reporting-capabilities.json` (`media_buy.installment_lifecycle`) | + +**If you built from a beta bundle.** Stop emitting and accepting the fields that leave, and move the ones that change home. Regenerate from the rc.0 bundle. An open schema ignores a field it no longer defines, so a stale sender is not rejected there, but the field carries no 3.3 meaning. Two cases reject it: a schema that stays closed, such as the canonical performance standard, and a deprecated row that names the field, such as `sync_creatives` `assignments[]`, which rejects `trackers` and `landing_page_url`. The fields that stay need no action. + +### Three experimental values renamed + +([#8989](https://github.com/adcontextprotocol/adcp/pull/8989), rc.0.) Three experimental values take the spelling their stable or sibling counterpart already uses. Each was added in 3.3 and existed only in the betas, from beta.0 to beta.6 at the longest, so no stable release has them. + +| Enum | Feature id | Beta spelling | rc.0 spelling | Follows | +|---|---|---|---|---| +| `enums/execution-readiness-status.json` | `media_buy.execution_readiness` | `input_required` | `input-required` | `enums/task-status.json` | +| `enums/creative-change-kind.json` | `creative.live_updates` | `click_through` | `clickthrough` | `url_type` in `enums/url-asset-type.json` | +| `enums/delivery-projection-end-state.json` | `media_buy.delivery_projection` | `underdelivery` | `under_delivery` | `enums/offer-reason.json` | + +The values are renamed in place, with no alias. A seller or buyer built from a beta bundle sends and accepts the new spelling in `readiness_status` and the product rollup, `creative.live_updates.in_place[].change`, `staged_update.change_kinds[]` and the `CREATIVE_LIVE_UPDATE_UNSUPPORTED` details, and `projection.projected_end_state`. + ## Required to claim 3.3 behavior ### Discovery tasks never provision an account @@ -163,6 +251,23 @@ On a `"3.2"` pin the fail-closed rule remains opt-in [interim guidance](/docs/bu An `authorized_agents[].url` whose canonical form has the root path and no query, such as `https://agent.example.com`, now matches any agent URL with the same canonical origin, so it authorizes an agent connected at `https://agent.example.com/mcp`. Under 3.2 it matched only an agent served at the root. An entry with a path still matches only that canonical URL. When several entries match the same agent, such as an origin-only entry and an entry with the agent's full URL, each one authorizes it and the agent's scope is the union of their scopes; a narrower entry never removes scope that another matching entry grants. A `signing_keys` pin combines the same way, over the entries that match the agent and authorize the message's scope: the agent is pinned only if every such entry carries `signing_keys`, and then it may sign with a key pinned by any of them, so an unpinned origin-only entry that covers the message leaves the agent unpinned even where its full-URL entry pins keys. An entry that authorizes nothing for the message, such as one for another country, neither pins nor unpins it. Buyers, TMP providers, and registries that check `authorized_agents[].url` MUST apply the origin-only rule. No entry that authorized an agent under 3.2 stops authorizing it. This aligns `adagents.json` with [DR-0023](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0023-agent-identity-is-an-origin.md), under which an origin hosts one agent. A host that serves several tenants' agents at different paths lists each tenant's full agent URL, not its bare origin, which would authorize all of them. See [Agent URL matching](/docs/governance/property/adagents#agent-url-matching). +### Sellers accept creatives that conform to the declared format option + +([#8941](https://github.com/adcontextprotocol/adcp/pull/8941), rc.0.) A seller MUST NOT refuse a creative, with a conformance code (`CREATIVE_SIZE_MISMATCH`, `CREATIVE_VALUE_NOT_ALLOWED`, `CREATIVE_VALIDATION_FAILED_GENERIC`, or `VALIDATION_ERROR` / `INVALID_REQUEST` against the assets), on the grounds of a declared parameter the creative satisfies, and MUST NOT enforce a narrower value than the one declared. A closed set narrows a slot only when it is declared: with no `cta_values`, the `cta` slot takes free text. Under `technical_requirements_complete: true` the seller holds no undeclared limit, so a creative that conforms to every declared parameter is accepted. Refusals outside format conformance are unchanged: `CREATIVE_REJECTED` for content review and `POLICY_VIOLATION` for advertising policy. + +**Sellers** that refused declared sizes or enforced an undeclared CTA list were already contradicting their own declaration; they now fail the new `media_buy_seller/declared_format_option_acceptance` scenario. See [Format conformance](/docs/creative/task-reference/sync_creatives#format-conformance). + +### Accepting signed terms binds every member + +([#8884](https://github.com/adcontextprotocol/adcp/pull/8884), rc.0.) `terms_digest` covers the entire `commercial_terms` JSON value: every member at every depth, including `ext` and members a party does not recognize. Several schemas inside `commercial_terms` are open, so the signed bytes can carry members a party's release does not define. Accepting the terms binds the accepting party to every member, so a party that cannot interpret every member MUST NOT accept them. + +- **Buyers** decline with the new `decline_proposals` reason `unrecognized_terms`. +- **Sellers** reject the request that carries such terms, such as a `buy_products` purchase, with the new error code `UNRECOGNIZED_TERMS`. +- **Governance agents** deny the check through their existing deny path. +- **Everyone** computes or verifies `terms_digest` over the JSON value as received, never over a re-serialized parsed model, which can drop members the model doesn't declare. A member whose schema defines it as opaque, such as `context`, is interpreted by that definition. + +The `media_buy_seller/unrecognized_terms_rejected` storyboard grades the seller side. See [Verify terms independently](/docs/media-buy/product-discovery/proposal-negotiation#3-verify-terms-independently). + ### Advertise only the measurement terms you accept A seller MUST NOT advertise, in a product's `measurement_terms`, a `measurement_window` or other term value that it would reject with `TERMS_REJECTED` when a buyer replays those terms unchanged on `create_media_buy`. An advertised window MUST reference a `window_id` declared in `reporting_capabilities.measurement_windows`. The `measurement_terms_accepted` storyboard grades a rejection of replayed advertised terms as a seller failure. See [Advertise only what you accept](/docs/media-buy/task-reference/get_products#advertise-only-what-you-accept). @@ -332,6 +437,14 @@ Once you list 3.3 in `supported_versions`, every release you list is a promise a **Buyers.** Keep parsing tolerantly, because sellers that list no release later than 3.2 aren't bound by the rule. +### Prerelease pins, unpinned discovery, and anonymous capabilities + +A 3.3 beta buyer pinned `get_adcp_capabilities` to `"3.3-beta.5"` against a seller that speaks only 3.0, got `VERSION_UNSUPPORTED`, and never retried, so the two never found the release they share. 3.3 states how each side avoids that ([Pre-release pins](/docs/reference/versioning#pre-release-pins)). + +- **Buyers** MUST send a prerelease `adcp_version` only to a peer whose `supported_versions` advertises that exact value; a prerelease pin never negotiates down. They SHOULD send the discovery `get_adcp_capabilities` call without a pin, and on `VERSION_UNSUPPORTED` SHOULD retry without a pin or at a value from `supported_versions`, the recovery the error code already names. +- **Sellers** SHOULD serve `get_adcp_capabilities` without credentials, because buyers probe anonymously before they hold a key. This is a SHOULD in 3.3 and a MUST in 4.0 ([Authentication](/docs/building/by-layer/L2/authentication)). +- **MCP sellers.** A gateway or auth layer that allow-lists JSON-RPC methods SHOULD let `server/discover` (MCP `2026-07-28`), `initialize`, and `tools/list` through without credentials. Otherwise a current MCP client treats the agent as requiring sign-in before it can read capabilities ([MCP guide](/docs/building/by-layer/L0/mcp-guide#let-mcp-discovery-through-without-credentials)). + ### Refinement carries compliance forward A `build_creative` refinement (`refine_from_build_variant_id`) inherits the parent leaf's compliance set (`required_disclosures`, `prohibited_claims`). A refine request can add to it and never remove or narrow it; `message` and `config` cannot reduce it. An instruction such as "remove the disclaimer" fails the whole call with `COMPLIANCE_UNSATISFIED`. A refined leaf gets its own `creative_id`, and neither seller nor buyer-side approval of the parent extends to it. Schemas gain no field or error code. @@ -411,7 +524,7 @@ What this means for 3.3 adopters: - **Readers ignore unknown fields** on an open schema ([versioning](/docs/reference/versioning)). A validator that hard-codes the 3.2 closures rejects 3.3 payloads, so regenerate it from the 3.3 schemas. - **Generated types can change.** A generator that reads `additionalProperties` treats the opened objects as open: json-schema-to-typescript adds an index signature, and Pydantic models generated with `extra="forbid"` stop rejecting extra fields. Code that relied on a type or validation error for an unknown key needs its own check. -- **Send a 3.3 field only to a 3.3 peer.** A strict validator on 3.2.9 or earlier still rejects it ([Send only to 3.3 peers](#send-only-to-3-3-peers)). +- **Send a 3.3 field only to a 3.3 peer.** A strict validator on 3.2.10 or earlier still rejects it ([Send only to 3.3 peers](#send-only-to-3-3-peers)). - **Features that needed new terms in `commercial_terms` stay withdrawn** ([above](#withdrawn-from-3-3-planned-for-4-0)), and seller-held change terms are planned for 4.0 instead of shipping as `commercial_terms.change_terms[]`. - **Only the creative review SLA carries a clock** ([adcp#8501](https://github.com/adcontextprotocol/adcp/issues/8501)). `core/sla-window.json` is back to its 3.2.8 shape, and `clock` and `business_calendar_id` now live on `core/creative-review-sla.json`, which `creative_policy.review_sla` uses. Sellers built on 3.3.0-beta.1 through beta.5 stop sending `clock` and `business_calendar_id` on an action's `sla`, a change term's `processing_sla`, and the escalation SLA. Those maxima are elapsed time and include weekends and non-working periods. @@ -431,7 +544,7 @@ What this means for 3.3 adopters: ### Mixed creative approval states at startup -([#8485](https://github.com/adcontextprotocol/adcp/pull/8485).) A seller keeps valid pending-review and rejected assignments and starts the eligible approved assignments by default. An optional package `start_requires_all_creatives_approved` gate, declared through `media_buy.features.creative_start_policy`, holds the start until every assignment is approved, and a structured-only `update_creative_start_policy` action sets it independently of assignment changes. The gate is consumed at first enablement for serving. A seller distinguishes its own review (`pending_start`) from buyer-actionable missing coverage or a blocking rejection (`pending_creatives`). The new pre-activation `pending_start` to `pending_creatives` transition needs corresponding SDK transition-validator support before you adopt it. Buyers assign the complete launch set atomically or keep delivery paused during staged supply. +([#8485](https://github.com/adcontextprotocol/adcp/pull/8485).) A seller keeps valid pending-review and rejected assignments and starts the eligible approved assignments by default. An optional `start_requires_all_creatives_approved` gate on `control_media_buy` package controls, declared through `media_buy.features.creative_start_policy`, holds the start until every assignment is approved, and a structured-only `update_creative_start_policy` action sets it independently of assignment changes. The gate is consumed at first enablement for serving. A seller distinguishes its own review (`pending_start`) from buyer-actionable missing coverage or a blocking rejection (`pending_creatives`). The new pre-activation `pending_start` to `pending_creatives` transition needs corresponding SDK transition-validator support before you adopt it. Buyers assign the complete launch set atomically or keep delivery paused during staged supply. ### Receivers ignore `aggregated_totals` in delivery webhooks @@ -529,7 +642,7 @@ Receivers of A2A push notifications and AdCP webhooks SHOULD bound the request b ## Send only to 3.3 peers -Many 3.3 additions sit inside objects that 3.2 closes, so a strict 3.2 validator rejects them. Send a field or value that 3.3 defines only when the negotiated `adcp_version` is 3.3 or later. The cases most likely to bite: +Many 3.3 additions sit inside objects that 3.2.10 and earlier publish closed, so a strict validator built from those schemas rejects them. 3.2.11 ([#8864](https://github.com/adcontextprotocol/adcp/pull/8864)) opens the same locations in 3.2, so a validator built from it ignores most of these fields instead, but a 3.2 peer still doesn't understand them. Either way, send a field or value that 3.3 defines only when the negotiated `adcp_version` is 3.3 or later ([DR-0024](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0024-responses-conform-to-served-release.md)). The "why" column describes 3.2.10 and earlier. The cases most likely to bite: | Sender | Field or value | Why a 3.2 peer rejects it | |---|---|---| @@ -545,17 +658,16 @@ Many 3.3 additions sit inside objects that 3.2 closes, so a strict 3.2 validator | Seller | `dooh_inventory_summary` on canonical products (`list_products`, `request_proposals`, `refine_proposals`) | 3.2 `canonical-product.json` is closed. | | Buyer | `brand`, `operator_unit`, `currency`, `timezone`, or `billing` on a `sync_accounts` settings-update entry | 3.2 `SettingsUpdateMode` forbids them. | | Seller | `proposal_initiator`, `offer_reason`, seller offers, and `proposal.offered` notifications | `proposal_initiator` is a 3.3 field on a schema reopened in 3.3. A caller with no declared pin is treated as below 3.3. | -| Seller | A `price_adjustments` table on a fixed-price pricing option | The table is a 3.3 field, never returned to a caller below 3.3. | | Seller | `credit_note` records on `get_account_financials` invoices | A pre-3.3 buyer summing `invoices[].amount` would count a credit as a charge. | | Buyer | Core `demographics.gender` targeting | 3.2 core targeting is age-only. | -| Seller | `counting_mechanisms[]` on `measurement_terms` and `vendor_metric_provenance[]` on delivery metrics | Strict older validators reject the new fields. | +| Seller | `vendor_metric_provenance[]` on delivery metrics | Strict older validators reject the new field. | | Buyer | `reporting_subscriptions` on `sync_principal` | A seller that lists only `sync_principal` in `reporting_delivery.configuration_tasks[]` serves reporting registration to 3.3 callers only. | | Buyer | `pixel_tracker` `event` values `start`, `first_quartile`, `midpoint`, `third_quartile`, `complete` | 3.2 closes the `event` enum; send them as `event: custom` until the seller negotiates 3.3 ([below](#hosted-video-and-audio-playback-trackers)). | +| Buyer | `geo_value_labels` on targeting ([#8966](https://github.com/adcontextprotocol/adcp/pull/8966)) | The field is not in 3.2, and a 3.2 seller may treat an unknown targeting key as an unsupported dimension. | | Seller | `match_keys` on `Product.identity` (experimental, beta.5) | 3.2 closes `core/product-identity.json`. `media_buy.supported_match_keys` on `get_adcp_capabilities` sits in an open object and is safe. | -New enum values (`nmo`, `videoamp`, `mxf`, `mpeg2`, `avc_intra`, `xavc`, `print_metrics` in `available-metric`, `operator_fee` in `adjustment-kind`) fall under the 3.x rule that clients tolerate unknown values, but a strict 3.2 validator still rejects them; send them only to 3.3 peers too. - -**Correction: proposal-flow schemas reopened.** 3.2 published the `list_products`, `request_proposals`, `refine_proposals`, `buy_products`, `accept_proposal`, `decline_proposals`, and `control_media_buy` request and response roots closed. It also closed `canonical-proposal`, `canonical-product`, `product-discovery-criteria`, `proposal-refinement`, `package-control`, and `opportunity-context`. [DR-0019](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0019-closed-row-schemas-deliberate-class.md) keeps roots and containers open. So 3.3 and a 3.2.x patch reopen them, as a correction recorded in [DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md). Every payload that was valid stays valid, and the rejections closure provided are kept by name. A field that only the legacy Product defines, such as `format_ids`, `is_custom`, or `product_card`, is still rejected on a canonical product. A root `feed_version` or `pricing_version` on a `request_proposals` response, and `warnings` on an error or submitted `buy_products`, `accept_proposal`, or `control_media_buy` response, are also still rejected. A strict validator on an earlier 3.2 patch still rejects new fields on them, so the rule above applies. `commercial_terms` and the purchases inside it stay closed. +New enum values (`nmo`, `videoamp`, `mxf`, `mpeg2`, `avc_intra`, `xavc`, `3gp`, `mpeg`, and `m4v` in video `containers`, `print_metrics` in `available-metric`, `operator_fee` in `adjustment-kind`, and the eight Instagram, Facebook, Snapchat and X values in `distribution-identifier-type` ([#8995](https://github.com/adcontextprotocol/adcp/pull/8995))) fall under the 3.x rule that clients tolerate unknown values, but a strict 3.2 validator still rejects them; send them only to 3.3 peers too. +**Correction: the proposal flow and the other accidentally closed schemas are open.** 3.2 published the `list_products`, `request_proposals`, `refine_proposals`, `buy_products`, `accept_proposal`, `decline_proposals`, and `control_media_buy` request and response roots closed, along with `canonical-proposal`, `canonical-product`, `product-discovery-criteria`, `proposal-refinement`, `package-control`, and `opportunity-context`. 3.2.8 reopened them first. Under the 2026-11-09 decision, 3.3 opens every schema that was closed without a structural reason, and 3.2.11 ([#8864](https://github.com/adcontextprotocol/adcp/pull/8864)) does the same for 3.2 ([Schemas are open by default](#schemas-are-open-by-default)). Opening a schema is a correction under [DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md), not a protocol break. Every payload that was valid stays valid, and the rejections closure provided are kept by name. A field that only the legacy Product defines, such as `format_ids`, `is_custom`, or `product_card`, is still rejected on a canonical product. A root `feed_version` or `pricing_version` on a `request_proposals` response, and `warnings` on an error or submitted `buy_products`, `accept_proposal`, or `control_media_buy` response, are also still rejected. A strict validator built from an earlier 3.2 patch still rejects new fields on these schemas, so the rule above applies. `commercial_terms` and the purchases inside it are held closed until 4.0. `get_adcp_capabilities` runs before negotiation, so a seller cannot gate its capability document. A 3.3 seller's `media_buy.features.catalog_ingestion` object fails a 3.2 schema that admits only booleans there. Buyers parse capabilities tolerantly, as [Versioning](/docs/reference/versioning) recommends. @@ -594,6 +706,9 @@ These change generated types or bundle shape without changing what a conformant - **Local-alignment durations (#8718, beta.4).** `core/reporting-schedule.json` and `core/reporting-schedule-offering.json` reject a `period_duration` with both a non-zero date and a non-zero time component under `account_timezone`, `source_timezone`, or `billing_cycle`. Generated validators reject `P1DT12H` there; `P1DT0H`, `P0DT12H`, and `utc` mixed durations stay valid. - **New error codes and shapes (beta.4 and beta.5).** `SUBSCRIPTIONS_REQUIRE_ACCOUNT_ID_KEY` (recovery `correctable`) for a managed-delivery offering without `account_id` in its primary keys (#8718); `budget_field`, `basis`, `constraint`, and `related_field` on `BUDGET_TOO_LOW` details (#8710); `SetAccountTimezoneResult` on the controller response (#8717); and `core/match-key.json` with `enums/match-key-use.json` (#8446). +- **Opened schemas ([#8866](https://github.com/adcontextprotocol/adcp/pull/8866), rc.0).** `additionalProperties` goes from `false` to `true` at 744 of the 859 closed locations, and nothing else in those schemas changes. Generated types change: json-schema-to-typescript gives an opened object an index signature, Pydantic models stop forbidding extra fields, and Zod validators accept unknown keys where the schema opened. Where closure also rejected a specific field, the opened schema names it in `not: { anyOf: [{ required: [...] }] }`, so a validator keeps that rejection. Code that relied on a type or validation error for any other unknown key needs its own check. See [Schemas are open by default](#schemas-are-open-by-default). +- **Withdrawn and moved beta fields (rc.0).** Regenerate to drop the fields the [closed-schema triage](#closed-schema-triage-what-stays-in-3-3) removes and to pick up the ones that change home, such as `execution_readiness` on `list_products`. `metric_id` on performance standards stays in the rc.0 schemas until [#8854](https://github.com/adcontextprotocol/adcp/pull/8854) merges. + ## Adopt by capability Optional unless noted. A seller that declares nothing keeps 3.2 behavior. @@ -622,7 +737,14 @@ Optional, two pieces with different stability. A migration note: a legacy installment that carries only the deprecated `collection_id` cannot be represented on the canonical surface. Add `collection_ref` before declaring 3.3 — a seller that drops such installments from its canonical projection is asserting run-of-collection for a product that actually sells named slots. -**Not in 3.3.** Naming the exact installments a purchase buys, and dropping or swapping one through `refine_proposals`, was merged for 3.3 and is [withdrawn to 4.0](#installment-selection-published-in-beta-1-removed-after-beta-1). A purchase buys the product as offered. +**Not in the signed purchase.** Naming the exact installments in `purchases[].installments[]` was merged for 3.3 and is [withdrawn to 4.0](#installment-selection-published-in-beta-1-removed-after-beta-1). A purchase buys the product as offered. From rc.0, a buyer chooses installments on the request side instead ([below](#installment-selection-and-per-installment-creatives-experimental)). + +### Installment selection and per-installment creatives (experimental) + +Optional, two features, each gated on its feature id in `experimental_features`. + +- **Installment selection (`media_buy.installment_refinement`, [#8974](https://github.com/adcontextprotocol/adcp/pull/8974)).** A buyer asks for specific installments with `refine_proposals` `installment_changes`: entries of `{ product_id, installment_ref, action }`, where `action` is `include` or `omit`, unique by `(product_id, installment_ref)`. A seller that supports it lists `installment_changes` in `media_buy.proposal_refinement.supported_dimensions`, which requires the feature id. The seller answers with a revised draft that buys a product whose `installments[]` is exactly the chosen set, often one it derives for the selection, and reports each change it can't satisfy, with a `reason`, in `unsatisfied_installment_changes` on the result row. A seller never changes an offered product's installments, and a buyer rejects an answer whose product doesn't match the selection. Nothing goes into `commercial_terms`: `terms_digest` binds the choice through the `product_id`. Binding the slots themselves in `purchases[].installments[]` stays a 4.0 item. See [Choose installments](/docs/media-buy/task-reference/refine_proposals#choose-installments-experimental). +- **Per-installment creatives (`media_buy.installment_creative_assignment`, [#8972](https://github.com/adcontextprotocol/adcp/pull/8972)).** `installment_refs`, a unique list of 1 to 500 canonical installment references, is optional on the `sync_creatives` `assignment_operations` `assign` and `replace` operations. It limits the assignment to those installments of the package; absent, the assignment applies to every installment, as before, and placement routing intersects with the installment scope. A seller rejects a ref outside the purchased product's installments with `VALIDATION_ERROR`, and a change past an installment's `change_cutoff` with `CREATIVE_DEADLINE_EXCEEDED`; `unassign` and `merge` reject the field by name. `get_media_buys` `packages[].creative_approvals[]` and `list_creatives` `assignments.assigned_packages[]` read it back. Buyers send it only to a seller that lists the feature id, because a seller that ignored it would run the creative on every installment; a seller without it rejects the field with `UNSUPPORTED_FEATURE`. It sits on no deprecated surface. See [Assigning to specific installments](/docs/creative/task-reference/sync_creatives#assigning-to-specific-installments-experimental). ### Creative `seller_revision` @@ -651,7 +773,7 @@ Optional. `list_creatives` may return `seller_revision` on each creative: a sell ### Assignment landing pages and trackers -A seller that declares `creative.supports_assignment_landing_page: true` (requires a creative library) accepts `landing_page_url` on a package creative assignment, `sync_creatives` `assignments[]`, and `assign` operations. The override changes the destination for one creative on one package without changing the library creative or its approval; the seller serves it everywhere it applies or rejects the assignment, and returns the actual destination from `list_creatives` and `get_media_buys`. Agents without the capability reject the field with `UNSUPPORTED_FEATURE`. Likewise, a seller that declares `creative.supports_assignment_trackers: true` accepts assignment-scoped measurement `trackers`, fires them alongside the creative's own without changing its revision or approval, enforces the format's tracker-slot limits where the format declares tracker slots (a format that declares none makes no slot-limit claim, #8713), and returns the assignment-only list from `list_creatives` and `get_media_buys` (#8220). See [Assignment landing pages](/docs/creative/task-reference/sync_creatives#assignment-landing-pages). +A seller that declares `creative.supports_assignment_landing_page: true` (requires a creative library) accepts `landing_page_url` on `sync_creatives` `assign` operations; its copies on package creative assignments and `sync_creatives` `assignments[]` are withdrawn at rc.0. The override changes the destination for one creative on one package without changing the library creative or its approval; the seller serves it everywhere it applies or rejects the assignment, and returns the actual destination from `list_creatives` and `get_media_buys`. Agents without the capability reject the field with `UNSUPPORTED_FEATURE`. Likewise, a seller that declares `creative.supports_assignment_trackers: true` accepts assignment-scoped measurement `trackers`, fires them alongside the creative's own without changing its revision or approval, enforces the format's tracker-slot limits where the format declares tracker slots (a format that declares none makes no slot-limit claim, #8713), and returns the assignment-only list from `list_creatives` and `get_media_buys` (#8220). See [Assignment landing pages](/docs/creative/task-reference/sync_creatives#assignment-landing-pages). ### Hosted video and audio playback trackers @@ -693,6 +815,12 @@ An SDK talking to a seller that does not advertise 3.3 MAY make this rewrite its Agents can report `adcp.implementation.sdks[]` with a package `name`, exact resolved `version`, and a `components` list. `components: []` reports SDK use without claiming agent-wide component coverage, such as an SDK signing helper used on only some routes. Existing agents may omit the block; buyers treat omission as unknown SDK use, while `sdks: []` explicitly reports no AdCP SDK use. Components describe the deployed server integration, including build-time type imports, rather than the package's available features. Buyers keep using AdCP version declarations for negotiation and retain all conformance obligations. Approval comes from a trusted catalog, and reducing check depth requires independently trusted evidence covering the endpoint and integration. See [implementation metadata](/docs/protocol/get_adcp_capabilities#implementation). +### Display labels for geo targeting codes + +Optional ([#8966](https://github.com/adcontextprotocol/adcp/pull/8966), beta.6). Targeting can carry display names beside its geographic codes. `geo_value_labels` maps the ISO codes in `geo_countries`, `geo_countries_exclude`, `geo_regions`, and `geo_regions_exclude` to names (`{ "DE": "Germany", "US-CA": "California" }`), and `geo_metros`, `geo_metros_exclude`, and `geo_places` entries take `value_labels` (`{ "501": "New York" }`). Every label key MUST appear in the values it labels. + +Labels are not a targeting dimension. Sellers MUST NOT resolve or apply targeting from them and MUST NOT reject a request because they are present, and MAY omit, keep, or supply their own labels in readback. Targeting equality and exact readback compare codes only, and a name in place of a code is still invalid. In create and update input, `null` clears labels the seller kept. Buyers SHOULD NOT send `geo_value_labels` to a seller on a version before 3.3 ([Send only to 3.3 peers](#send-only-to-3-3-peers)). See [Geographic Restrictions](/docs/media-buy/advanced-topics/targeting#geographic-restrictions). + ### Targeting errors A seller that rejects an unsupported or removed targeting dimension with `UNSUPPORTED_FEATURE` SHOULD use the new `error-details/unsupported-targeting-dimension.json` details shape (`unsupported_dimension`, optional `supported_dimensions`, `deprecated`, `replacement_dimension`, `product_id`, `package_index`) and point `error.field` at the targeting path (#8052). No new error code is added; adapters minting `UNSUPPORTED_TARGETING_DIMENSION` or `DEPRECATED_TARGETING_DIMENSION` should migrate. See [Rejected targeting dimensions](/docs/media-buy/advanced-topics/targeting#rejected-targeting-dimensions). @@ -769,13 +897,13 @@ Optional (`media_buy.match_keys`, [#8446](https://github.com/adcontextprotocol/a Each is optional and experimental: a seller that emits it lists the feature id in `experimental_features`, and a seller that declares nothing keeps 3.2 behavior. - **Seller offers (`media_buy.seller_offers`, [#8102](https://github.com/adcontextprotocol/adcp/pull/8102)).** A seller proposes a change to an accepted buy as a `committed` canonical proposal with `proposal_initiator: "seller"` and an `offer_reason` (`installment_postponed`, `installment_cancelled`, `preemption`, `under_delivery`, `seller_request`), a `media_buy_update` or `media_buy_cancellation` that carries `parent_proposal_id`, `media_buy_id`, and `base_media_buy_revision`. Buyers read offers through `list_proposals`, announced by the identifiers-only `proposal.offered` notification, and accept with `accept_proposal`, decline with `decline_proposals`, or revise with `refine_proposals`. `expires_at` is the response deadline; at it the signed terms stand and `accept_proposal` returns `PROPOSAL_EXPIRED`, so silence is never acceptance. A seller that lists the feature id MUST also list `media_buy.open_opportunities` and advertise `list_proposals`. Sellers MUST NOT send offers to callers served below 3.3. Pre-agreed seller changes inside `commercial_terms` are not part of 3.3. See [Seller offers](/docs/media-buy/product-discovery/proposal-negotiation#seller-offers). -- **Price adjustments (`media_buy.price_adjustments`, [#7955](https://github.com/adcontextprotocol/adcp/pull/7955), [#7659](https://github.com/adcontextprotocol/adcp/issues/7659)).** A binding fixed-price pricing option (`cpm`, `vcpm`, `cpc`, `cpcv`, `cpv`, `cpp`, `flat_rate`) can carry an ordered table of `fee` and `discount` rows, each with a `rate` or a fixed `amount`, keyed by `format_option`, `placement_selection` (needs `overlay_support.placement_selection`), or `always`, and optionally a `valid_from` and `valid_until` window evaluated at the purchase `start_time`; a flight that crosses a window boundary is rejected. Selection rows fire at most once per dimension, then each firing row applies to one running total in declared order, rounding half away from zero at every step. A table is optional: without one, the price applies only to what was quoted. A seller never returns a table to a caller below 3.3. See [Selection-dependent price adjustments](/docs/media-buy/advanced-topics/pricing-models#selection-dependent-price-adjustments). -- **Execution readiness (`media_buy.execution_readiness`, [#7934](https://github.com/adcontextprotocol/adcp/pull/7934)).** For products that declare `execution_requirements`, a `get_products` request with `account` can set `include_execution_readiness: true`. The response carries an `execution_readiness` map keyed by `product_id`, versioned independently of `wholesale_feed_version` so public wholesale catalogs keep `cache_scope: "public"`. Each product and requirement reports `ready`, `setup_required`, `selection_required`, `input-required`, or `unknown` (the seller could not check, which is not the same as the account lacking the resource), with candidates whose `resource_id` is directly usable in the existing binding field. See [Per-account execution readiness](/docs/media-buy/specification#per-account-execution-readiness-experimental). +- **Price adjustments (`media_buy.price_adjustments`, [#7955](https://github.com/adcontextprotocol/adcp/pull/7955), [#7659](https://github.com/adcontextprotocol/adcp/issues/7659)), withdrawn at rc.0 and planned for 4.0.** In the betas, a binding fixed-price pricing option (`cpm`, `vcpm`, `cpc`, `cpcv`, `cpv`, `cpp`, `flat_rate`) can carry an ordered table of `fee` and `discount` rows, each with a `rate` or a fixed `amount`, keyed by `format_option`, `placement_selection` (needs `overlay_support.placement_selection`), or `always`, and optionally a `valid_from` and `valid_until` window evaluated at the purchase `start_time`; a flight that crosses a window boundary is rejected. Selection rows fire at most once per dimension, then each firing row applies to one running total in declared order, rounding half away from zero at every step. A table is optional: without one, the price applies only to what was quoted. A seller built from a beta bundle stops emitting the table ([closed-schema triage](#closed-schema-triage-what-stays-in-3-3)). See [Selection-dependent price adjustments (withdrawn)](/docs/media-buy/advanced-topics/pricing-models#selection-dependent-price-adjustments-withdrawn). +- **Execution readiness (`media_buy.execution_readiness`, [#7934](https://github.com/adcontextprotocol/adcp/pull/7934)).** For products that declare `execution_requirements`, a `list_products` request with `account` can set `include_execution_readiness: true` (on `get_products` in the betas, moved at rc.0). The response carries an `execution_readiness` map keyed by `product_id`, versioned independently of `wholesale_feed_version` so public wholesale catalogs keep `cache_scope: "public"`. Each product and requirement reports `ready`, `setup_required`, `selection_required`, `input-required`, or `unknown` (the seller could not check, which is not the same as the account lacking the resource), with candidates whose `resource_id` is directly usable in the existing binding field. See [Per-account execution readiness](/docs/media-buy/specification#per-account-execution-readiness-experimental). - **Gender targeting (`media_buy.gender_targeting`, [#7925](https://github.com/adcontextprotocol/adcp/pull/7925)).** Core `demographics.gender` predicates with `female`, `male`, and `non_binary` value sets and an independent unknown group, whose `include_unknown` covers both unavailable gender and an explicit choice not to state it. Product-scoped capabilities, exact gender-only and mixed age and gender readback, and `sex_gender` governance classification come with it. Demographic delivery reporting stays age-only in 3.3, so a gender-targeted package has no gendered delivery readback. Buyers MUST NOT send core gender fields on a 3.2 contract. See [Core gender targeting](/docs/media-buy/advanced-topics/targeting#core-gender-targeting-3-3). - **Signal pricing groups (`signals.pricing_groups`, [#8058](https://github.com/adcontextprotocol/adcp/pull/8058), [#7898](https://github.com/adcontextprotocol/adcp/issues/7898)).** An optional `pricing_group` on `get_signals` results and on `Product.signal_targeting_options[]`, with `signal_pricing_group_rules[]` (`{pricing_group, pricing_combination: highest | each}`) on the response and on `signal_targeting_rules`, lets a seller price signals such as alternative age bands as one audience. A group with no rule and every ungrouped signal is charged `each`, and `flat_fee`, `per_unit`, `custom`, and `percent_of_media` options are always charged `each`. See [Signal pricing groups](/docs/media-buy/advanced-topics/targeting#signal-pricing-groups). - **Provider-initiated signal delivery (`signals.delivery_methods`, [#8044](https://github.com/adcontextprotocol/adcp/pull/8044), [#6552](https://github.com/adcontextprotocol/adcp/issues/6552)).** A signal agent declares `signals.delivery_methods[]` on `get_adcp_capabilities`, with the same pattern vocabulary as audience activation methods read from the send side. An `activate_signal` agent destination may pin a `delivery_method`; with no pattern and vendor intersection the destination fails with `UNSUPPORTED_FEATURE`, and a pin sent to an agent that doesn't list it is rejected the same way. Agent deployments gain `delivery_status` (`awaiting_read`, `delivered`, `failed`), a `delivery` descriptor, `delivery_error`, and an optional match outcome. A receiver field not yet established fails the destination with `ACCOUNT_SETUP_REQUIRED`. See [Declaring delivery methods](/docs/signals/tasks/activate_signal#declaring-delivery-methods). -- **Measurement provenance (`media_buy.measurement_provenance`, [#7940](https://github.com/adcontextprotocol/adcp/pull/7940)).** A shared `enums/collection-mechanism.json` vocabulary (`set_top_box`, `acr`, `panel`, `server_logs`, `client_tracker`, `sdk`) has two uses, both on open schemas: `measurement_terms.billing_measurement.counting_mechanisms[]` declares what the billing count is counted from (a seller whose own system is the named vendor SHOULD declare it; absence means undeclared), and `vendor_metric_provenance[]` on delivery metrics carries `mechanisms[]` and an optional `deduplicated` for a `vendor_metric_values[]` row, joined on `(vendor, metric_id, qualifier)`. A collection mechanism is not `measurement_source`, which stays the provider slug, and broadcast as-run logs stay airing evidence in `by_spot[]`. Sellers serving an older pin omit both fields. -- **Audience evidence targets and invoice lines.** `target_audiences[]` (`media_buy.audience_evidence_targets`, [#8215](https://github.com/adcontextprotocol/adcp/pull/8215)) names the audience a buyer wants evidence for beside `audience_evidence_requirements`, satisfied only by an admissible evidence item for exactly that audience; it is never a targeting predicate. `lines[]`, `invoice_kind`, and `adjusts_invoice_id` on `get_account_financials` invoices (`account.invoice_lines`, [#8207](https://github.com/adcontextprotocol/adcp/pull/8207)) tie an amount to the buys, packages, and reporting revisions it bills, and never settle an invoice. +- **Measurement provenance (`media_buy.measurement_provenance`, [#7940](https://github.com/adcontextprotocol/adcp/pull/7940)).** A shared `enums/collection-mechanism.json` vocabulary (`set_top_box`, `acr`, `panel`, `server_logs`, `client_tracker`, `sdk`) is used by `vendor_metric_provenance[]` on delivery metrics, which carries `mechanisms[]` and an optional `deduplicated` for a `vendor_metric_values[]` row, joined on `(vendor, metric_id, qualifier)`. A collection mechanism is not `measurement_source`, which stays the provider slug, and broadcast as-run logs stay airing evidence in `by_spot[]`. Sellers serving an older pin omit the field. `measurement_terms.billing_measurement.counting_mechanisms[]` is withdrawn at rc.0 and planned for the canonical measurement terms in 4.0. +- **Audience evidence targets (withdrawn) and invoice lines.** `target_audiences[]` (`media_buy.audience_evidence_targets`, [#8215](https://github.com/adcontextprotocol/adcp/pull/8215)) is withdrawn at rc.0 and has no 3.3 wire form; purchases gain it in 4.0. `lines[]`, `invoice_kind`, and `adjusts_invoice_id` on `get_account_financials` invoices (`account.invoice_lines`, [#8207](https://github.com/adcontextprotocol/adcp/pull/8207)) tie an amount to the buys, packages, and reporting revisions it bills, and never settle an invoice. ## Experimental surface notices @@ -791,6 +919,18 @@ The seller exposes the evaluator behind an agent that implements `get_creative_f This is a removal on an experimental surface, which the [experimental status](/docs/reference/experimental-status#contract-for-experimental-surfaces) contract allows with notice; 3.1 and 3.2 keep `evaluator_id`. The 6-week pre-landing notice is waived: beta.0 is the notice vehicle, and 3.3 GA ships no earlier than 6 weeks after the beta.0 tag. A fourth source form for conversion-outcome evaluators stays open, and `supports_evaluator_gate` and hard-gate semantics stay reserved. See [Evaluator source model](/docs/creative/buyer-attached-inputs#evaluator-source-model). +### Reliable Reporting managed delivery holds no buyer secret + +([#8793](https://github.com/adcontextprotocol/adcp/pull/8793), rc.0.) Applies to sellers that offer managed delivery under the experimental `media_buy.reporting_delivery`. For every managed pattern, the seller authenticates as itself, through its advertised `producer_identity`. A seller MUST NOT hold, request, or store a caller-issued secret of any kind (password, API key, bearer token, OAuth client secret, private key, signed URL, or shared signing key), directly or through a processor acting for it; the deprecated `reporting_webhook.authentication` block is not precedent. Rows in an HTTP request body are the Core `reporting_webhook` transport, never `file_transfer`. + +The new `https_put` `file_transfer` transport (experimental in 3.3) writes immutable objects and a manifest to a buyer HTTPS endpoint. It is conformant only when the manifest is written last, every request is signed by the seller under the Web Bot Auth profile with keys from its origin's key directory, and the endpoint passes a signed probe, carrying the seller-issued `destination_ref`, before `ready`. + +### Per-package rows in Reliable Reporting report definitions + +([#8983](https://github.com/adcontextprotocol/adcp/pull/8983), rc.0.) Applies to sellers that publish report definitions under the experimental `media_buy.reporting_delivery`. Report definitions gain `contract_version` `1.2`, which keeps every `1.1` rule. At `1.2`, a definition whose rows are scoped to a media buy names that dimension `media_buy_id`, and a definition whose `dimensions` include `media_buy_id` MUST include `package_id`; the offering's `reporting_profile.primary_keys` then MUST include `package_id`. A definition without `media_buy_id`, such as an account-level summary, is exempt at every version. + +Nothing negotiates the version: the definition states it, and the offering pins it through `report_definition_uri` and SHA-256, as for `1.1`. Callers pinned below 3.3 accept only `1.0` and `1.1`, so a seller MUST serve them offerings whose definitions are `1.0` or `1.1`. `1.0` and `1.1` keep validating unchanged; graders SHOULD report one that includes `media_buy_id` but not `package_id` as an advisory finding. Subscription selectors and offering `standard_dimensions` keep calling the breakdown `package`. The vectors are in `test-vectors/reporting-report-definition/`. See [Configuration and capabilities](/docs/media-buy/task-reference/get_reporting_status#configuration-and-capabilities). + ### Superseded reporting snapshots may be compacted @@ -830,16 +970,16 @@ Adopters of these patches have already seen these; their changesets reappear in ## Deprecations -3.3 deprecates two result fields, the principal kind field and assertion, the RFC 9421 signing profiles, one usage, the account identity-rekey machinery, and the boolean form of `demographics`; all remain functional throughout 3.x: +3.3 deprecates two result fields, the principal kind field and assertion, the RFC 9421 signing profiles, one usage, the account identity-rekey machinery, and the boolean form of `demographics`. All remain functional throughout 3.x, and each is expected to be removed in 4.0. Removals happen in a major. 3.3 stays supported for at least 12 months after 4.0 reaches GA, so a 3.3 integration keeps working while it migrates ([support window](/docs/reference/versioning#support-window-for-previous-major)). -- **`seller_id` on `sync_event_sources` and `sync_audiences` results.** Use the new optional `platform_id` for the object's ID in the seller's ad platform, matching `sync_creatives` and `sync_catalogs`. **Sellers** reporting a platform identifier in 3.3 and later 3.x responses MUST emit both fields with identical values, including discovery responses and seller-managed event sources. **Buyers** MUST prefer `platform_id` and fall back to `seller_id` only when `platform_id` is absent. Either field may be absent in legacy responses, and both may be absent when no platform identifier is available. Continue using `event_source_id` and `audience_id` in AdCP requests. The aliases keep their object-ID semantics; they are never seller identity. `adagents.json` `contact.seller_id` and publisher identifiers of type `seller_id` are unchanged. Removal is no earlier than 4.0 and subject to the [six-month notice policy](/docs/reference/versioning#deprecation-policy). See [event source migration](/docs/media-buy/task-reference/sync_event_sources#platform-identifier-migration-adcp-3-3) and [audience migration](/docs/media-buy/task-reference/sync_audiences#platform-identifier-migration-adcp-3-3) ([#8290](https://github.com/adcontextprotocol/adcp/issues/8290)). -- **`principal_kind` and `expected_principal_kind` on `sync_principal` and `get_principal`**, and the `enums/principal-kind.json` enum. A principal is the buyer agent as the seller has bound it, so the kind is always `buyer_agent` and carries no information. Sellers keep returning `principal_kind` and honoring `expected_principal_kind` throughout 3.x; buyers stop reading and sending them, and don't branch on `principal_kind`. Removal is no earlier than 4.0 and subject to the [six-month notice policy](/docs/reference/versioning#deprecation-policy). The task names are unchanged ([#8443](https://github.com/adcontextprotocol/adcp/pull/8443), [#8280](https://github.com/adcontextprotocol/adcp/issues/8280)). +- **`seller_id` on `sync_event_sources` and `sync_audiences` results.** Use the new optional `platform_id` for the object's ID in the seller's ad platform, matching `sync_creatives` and `sync_catalogs`. **Sellers** reporting a platform identifier in 3.3 and later 3.x responses MUST emit both fields with identical values, including discovery responses and seller-managed event sources. **Buyers** MUST prefer `platform_id` and fall back to `seller_id` only when `platform_id` is absent. Either field may be absent in legacy responses, and both may be absent when no platform identifier is available. Continue using `event_source_id` and `audience_id` in AdCP requests. The aliases keep their object-ID semantics; they are never seller identity. `adagents.json` `contact.seller_id` and publisher identifiers of type `seller_id` are unchanged. The aliases are expected to be removed in 4.0. See [event source migration](/docs/media-buy/task-reference/sync_event_sources#platform-identifier-migration-adcp-3-3) and [audience migration](/docs/media-buy/task-reference/sync_audiences#platform-identifier-migration-adcp-3-3) ([#8290](https://github.com/adcontextprotocol/adcp/issues/8290)). +- **`principal_kind` and `expected_principal_kind` on `sync_principal` and `get_principal`**, and the `enums/principal-kind.json` enum. A principal is the buyer agent as the seller has bound it, so the kind is always `buyer_agent` and carries no information. Sellers keep returning `principal_kind` and honoring `expected_principal_kind` throughout 3.x; buyers stop reading and sending them, and don't branch on `principal_kind`. They are expected to be removed in 4.0. The task names are unchanged ([#8443](https://github.com/adcontextprotocol/adcp/pull/8443), [#8280](https://github.com/adcontextprotocol/adcp/issues/8280)). - **The AdCP RFC 9421 signing profiles**, for requests (`adcp/request-signing/v1`) and webhooks (`adcp/webhook-signing/v1`), with keys found through brand.json and `identity.brand_json_url`. They keep working throughout 3.x and are removed in AdCP 4.0, together with the brand.json trust fields ([DR-0023](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0023-agent-identity-is-an-origin.md)). Their replacement is the experimental Web Bot Auth profile ([Web Bot Auth identities](/docs/building/by-layer/L1/security#web-bot-auth-identities); role-by-role steps in the [agent identity migration guide](/docs/reference/migration/agent-identity-3-3)): identity is the signer's origin, keys come from that origin's key directory, and no capabilities call is needed. **Signers** that serve no capabilities endpoint can move now. **Verifiers** keep accepting RFC 9421 signatures through 3.x, under the no-downgrade rule once an origin is bound. - **The natural key as the account reference after provisioning.** Sending the natural-key `AccountRef` on account-scoped tasks once the account exists is deprecated and planned for removal in AdCP 4.0 ([#7850](https://github.com/adcontextprotocol/adcp/issues/7850)). It keeps working throughout 3.x. The natural key itself stays: buyers use it to open accounts with `sync_accounts` and as a `list_accounts` filter to look up an account's ID. **Buyers** store the returned ID and send it. See [Account identity](/docs/accounts/overview#account-identity). - **The account identity-rekey machinery** ([#8474](https://github.com/adcontextprotocol/adcp/pull/8474)). The `account.identity_updates` capability is deprecated and planned for removal in AdCP 4.0, with everything it gates. That covers `operator_identity` and `destination_billing_entity` on `sync_accounts`, the `identity_change` and `identity_change_preview` fields, and the `ACCOUNT_MOVED` and `ACCOUNT_IDENTITY_CONFLICT` error codes. `account.stable_account_id` is deprecated with it. An account's identity never changes, so no rekey or former key exists. **Sellers** that implement `operator_identity` keep it working through 3.x and SHOULD declare `stable_account_id: true` while the field exists. **Buyers** change `operator_unit` as an attribute and send `account_id` without checking `stable_account_id`. - **The boolean form of `demographics`** in product `overlay_support` (`core/targeting-overlay-support.json`) and in `required_overlay_support` (`core/targeting-overlay-requirements.json`). `demographics: true` is the 3.2 shorthand for `{ "age": true }`, and every 3.2 release accepts the object form on both schemas. **Senders** MUST send the object form. **Receivers** MUST accept `true` and read it as `{ "age": true }`, so it satisfies an age requirement and never a `gender` requirement. It is planned for removal in AdCP 4.0 ([#8778](https://github.com/adcontextprotocol/adcp/issues/8778)). -3.3 also deprecates condition (b) of `request_signature_required` ([#8064](https://github.com/adcontextprotocol/adcp/pull/8064)), which exists only for the already-deprecated webhook `authentication` block. It is part of the `authentication` block's existing deprecation and is removed in 4.0 with the block. The experimental `configuration_task` field of `media_buy.reporting_delivery` is deprecated in favor of `configuration_tasks[]` and stays `"sync_accounts"` for clients pinned below 3.3 ([#8552](https://github.com/adcontextprotocol/adcp/pull/8552)). A deprecation window does not reset when a deprecated feature is modified. Other existing 3.2 deprecations keep their published removal windows. +3.3 also deprecates condition (b) of `request_signature_required` ([#8064](https://github.com/adcontextprotocol/adcp/pull/8064)), which exists only for the already-deprecated webhook `authentication` block. It is part of the `authentication` block's existing deprecation and is removed in 4.0 with the block. The experimental `configuration_task` field of `media_buy.reporting_delivery` is deprecated in favor of `configuration_tasks[]` and stays `"sync_accounts"` for clients pinned below 3.3 ([#8552](https://github.com/adcontextprotocol/adcp/pull/8552)). Changing a deprecated feature does not move its removal. Deprecations from earlier 3.x releases are likewise removed only in a major. One earlier deprecation is worth restating before 4.0. The integer request field `adcp_major_version` and the `adcp.major_versions` capability field, deprecated in 3.1 in favor of `adcp_version` and `adcp.supported_versions`, keep working through 3.x and are **removed in 4.0** ([DR-0035](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0035-adcp-major-version-removed-in-4-0.md)). Buyers send `adcp_version` on every request and keep the integer mirror until then. Sellers keep emitting `adcp.major_versions` alongside `adcp.supported_versions` through 3.x. In-house clients that send only the integer should move to `adcp_version` now. The [v4 compatibility checks](/docs/reference/migration/v4-compatibility#major_versions_removed_in_4_0) flag sellers that still rely on the integer list. @@ -854,6 +994,7 @@ One earlier deprecation is worth restating before 4.0. The integer request field - New experimental scenarios: `media_buy_seller/creative_live_updates` and `media_buy_seller/creative_live_update_refusal`, the `media_buy.execution_readiness` scenario, a gender-targeting conformance storyboard, and a stateful package-retention scenario for canceled and completed buys. The `definition_pin_drift` storyboard, the `definition_pin_probe` controller scenario, and the `definition-pins` vectors are removed with definition pins. - New controller scenario and vectors: `reporting_subscription_probe` on `comply_test_controller` (`revoke_grant`, `regrant`, `reduce_grant`, `set_account_timezone`, `advance_time`), and the canonical reporting-subscription coverage vectors with a reference model. Cross-SDK vectors for undisclosed rosters live under `static/test-vectors/product/`. - New experimental storyboards in beta.4: `account_requests` (#8677); `media_buy_seller/reporting_subscription_coverage` and `media_buy_seller/reporting_subscription_capacity` (#8680, #8724); `media_buy_seller/hold_policy_bounds`, `hold_policy_terms_only`, `hold_policy_version_gate`, `hold_unavailable_batch`, `hold_extension`, and `hold_ranking` (#8696); and `media_buy_seller/assignment_replace_transfers_settings` (#8695). The runner contract adds the advisory `owed_periods_match`, `instant_offset_within`, and `undefined_properties` checks, and `reset_state` runs before each storyboard when the seller lists it (#8717). +- `creative/policy_backed_rejections` runs only for sellers that declare the new optional `creative.supports_registry_policy_enforcement` (#8857, rc.0); a creative library alone does not imply it, and a seller that publishes a registry policy in `enforced_policies` still enforces it. `media_buy_seller/declared_format_option_acceptance` (#8941, rc.0) and `media_buy_seller/unrecognized_terms_rejected` (#8884, rc.0) are new. - `deterministic_testing` pins its fixtures and controller calls to one sandbox account (#8731, beta.5), and legacy creative fixtures come from a gated, offline test-kit catalog (#8684, beta.5). - Hosted service: grading of governance-aware sellers is covered in [AAO Verified](/docs/building/verification/aao-verified). @@ -861,12 +1002,12 @@ These change grading results, not the wire. ## Rollback -Stay on, or return to, `"3.2"`: every 3.3 declaration is optional, so removing it restores 3.2 behavior. The [required rules](#required-to-claim-3-3-behavior) are the exception: they apply as soon as you claim 3.3 behavior (for [served-release conformance](#responses-conform-to-the-served-release), as soon as you list 3.3 in `supported_versions`), so keep a 3.2-pinned route until your discovery, verification, and delivery-webhook paths pass against the beta. A seller that advances revisions from every origin while serving 3.2 callers only makes stale-`revision` updates fail sooner, which 3.2 already allowed. +Stay on, or return to, `"3.2"`: every 3.3 declaration is optional, so removing it restores 3.2 behavior. The [required rules](#required-to-claim-3-3-behavior) are the exception: they apply as soon as you claim 3.3 behavior (for [served-release conformance](#responses-conform-to-the-served-release), as soon as you list 3.3 in `supported_versions`), so keep a 3.2-pinned route until your discovery, verification, and delivery-webhook paths pass against the release candidate. A seller that advances revisions from every origin while serving 3.2 callers only makes stale-`revision` updates fail sooner, which 3.2 already allowed. ## Related - [What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3) -- [3.3 beta program](/docs/reference/3-3-beta) +- [3.3 prerelease program](/docs/reference/3-3-beta) - [Release Notes](/docs/reference/release-notes#version-3-3-0) - [Migrating from 3.1 to 3.2](/docs/reference/migration/3-1-to-3-2) - [Versions & Compatibility](/docs/reference/versions) diff --git a/docs/reference/migration/v4-compatibility.mdx b/docs/reference/migration/v4-compatibility.mdx index 8c7862804b1..1f25bc004bd 100644 --- a/docs/reference/migration/v4-compatibility.mdx +++ b/docs/reference/migration/v4-compatibility.mdx @@ -263,12 +263,14 @@ In 3.3 a seller-initiated change to a signed buy is always a [seller offer](/doc ## Changes not checked yet -A check is added once its 4.0 change is decided. These changes are still proposals or under working group review, so the suite does not grade them yet: +A check is added once its 4.0 change is decided. These changes are still proposals, under working group review, or decided without a check yet, so the suite does not grade them yet: - `channels` required on every product ([#7869](https://github.com/adcontextprotocol/adcp/issues/7869)) - `duration_ms` required on hosted video assets ([#5668](https://github.com/adcontextprotocol/adcp/issues/5668)) - the `account_id` from `sync_accounts` as the only account reference after provisioning ([#7850](https://github.com/adcontextprotocol/adcp/issues/7850)) - nested `status` renamed to `media_buy_status` ([#4905](https://github.com/adcontextprotocol/adcp/issues/4905)) +- at least one `by_package` row on each `get_media_buy_delivery` media buy (`minItems: 1`) ([#8973](https://github.com/adcontextprotocol/adcp/issues/8973)) +- `get_adcp_capabilities` served without credentials, a SHOULD in 3.3 that becomes a MUST in 4.0 ([Authentication](/docs/building/by-layer/L2/authentication)); decided, with no check yet The schemas also mark 48 deprecated fields with `x-removed-in: "4.0.0"`. The registry lists each one, either under the check that covers it or in `schema_removals_not_checked` with the reason no check covers it yet. Most uncovered fields are sent by buyers, so a seller run can't observe them. A few are seller-emitted and checkable but not graded yet: flat `valid_actions`, response-wide delivery `currency` and `aggregated_totals`, `inline_creative_management`, boolean `demographics` in product support, and the format-level build and pricing surface that `list_transformers` replaces. diff --git a/docs/reference/release-notes.mdx b/docs/reference/release-notes.mdx index 80bcf797d54..e130f881915 100644 --- a/docs/reference/release-notes.mdx +++ b/docs/reference/release-notes.mdx @@ -5,21 +5,21 @@ description: "Authoritative AdCP version-by-version release record with cumulati --- -Authoritative version-by-version release record for AdCP, with cumulative change detail, migration guidance, and per-version adoption notes. For the 3.3 beta overview, see [What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3), [Migrating from 3.2 to 3.3](/docs/reference/migration/3-2-to-3-3), and the [3.3 beta program](/docs/reference/3-3-beta). For the 3.2 adopter overview, see [What's New in AdCP 3.2](/docs/reference/whats-new-in-3-2); for the upgrade checklist, see [Migrating from 3.1 to 3.2](/docs/reference/migration/3-1-to-3-2); and for beta and RC history, see the [3.2 prerelease history](/docs/reference/3-2-beta). For the at-a-glance status of every published version, see [Versions & Compatibility](/docs/reference/versions). For source-level changelogs, see [CHANGELOG.md](https://github.com/adcontextprotocol/adcp/blob/main/CHANGELOG.md). For version stability, schema-change scope, and the 3.x guarantees see [Versioning & Governance](/docs/reference/versioning). For v2 end-of-life see the [v2 sunset page](/docs/reference/v2-sunset). +Authoritative version-by-version release record for AdCP, with cumulative change detail, migration guidance, and per-version adoption notes. For the 3.3 prerelease overview, see [What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3), [Migrating from 3.2 to 3.3](/docs/reference/migration/3-2-to-3-3), and the [3.3 prerelease program](/docs/reference/3-3-beta). For the 3.2 adopter overview, see [What's New in AdCP 3.2](/docs/reference/whats-new-in-3-2); for the upgrade checklist, see [Migrating from 3.1 to 3.2](/docs/reference/migration/3-1-to-3-2); and for beta and RC history, see the [3.2 prerelease history](/docs/reference/3-2-beta). For the at-a-glance status of every published version, see [Versions & Compatibility](/docs/reference/versions). For source-level changelogs, see [CHANGELOG.md](https://github.com/adcontextprotocol/adcp/blob/main/CHANGELOG.md). For version stability, schema-change scope, and the 3.x guarantees see [Versioning & Governance](/docs/reference/versioning). For v2 end-of-life see the [v2 sunset page](/docs/reference/v2-sunset). --- ## Version 3.3.0 -**Status:** Beta cycle. The latest checkpoint is `3.3.0-beta.5`, published 2026-11-07. 3.3 is a minor release targeting the 3.3.0 milestone. Beta.0 is the protocol-first cut used as the canonical input for SDK work; beta.1 through beta.5 incorporate integration feedback, and a checkpoint counts as SDK-backed only after SDK support for the exact bundle and integration evidence are published ([3.3 beta program](/docs/reference/3-3-beta#sdk-guidance)). No stable field, enum value, or task is removed. Three beta features, definition pins, purchase rights, and installment selection, are withdrawn after beta.1 and planned for 4.0 ([below](#withdrawn-from-3-3-planned-for-4-0)). The `seller_id` result fields on event sources and audiences, `principal_kind`, the natural-key account reference after provisioning, the account identity-rekey machinery, and condition (b) of `request_signature_required` are deprecated, and the RFC 9421 signing profiles are deprecated in favor of the experimental Web Bot Auth profile; all remain functional throughout 3.x. Normative changes that narrow conformant behavior, and the guarantees that loosen, are described under [Behavior changes to review](#behavior-changes-to-review). This section is the cumulative 3.3 narrative and is refreshed at each beta cut; `CHANGELOG.md` records what each individual cut consumed. +**Status:** Release candidate. The latest checkpoint is `3.3.0-rc.0`, the first release candidate, published 2026-11-16. 3.3 is a minor release targeting the 3.3.0 milestone. Beta.0 was the protocol-first cut used as the canonical input for SDK work, beta.1 through beta.5 incorporated integration feedback, beta.6 carried the 2026-11-09 decision to open the schemas that were closed by accident, with the closed-schema triage that followed it, and rc.0 is the first release candidate. A checkpoint counts as SDK-backed only after SDK support for the exact bundle and integration evidence are published ([3.3 prerelease program](/docs/reference/3-3-beta#sdk-guidance)). No stable field, enum value, or task is removed. Three beta features, definition pins, purchase rights, and installment selection, are withdrawn after beta.1 and planned for 4.0, and the triage removes further beta fields before rc.0 ([below](#withdrawn-from-3-3-planned-for-4-0)). The `seller_id` result fields on event sources and audiences, `principal_kind`, the natural-key account reference after provisioning, the account identity-rekey machinery, the boolean form of `demographics`, and condition (b) of `request_signature_required` are deprecated, and the RFC 9421 signing profiles are deprecated in favor of the experimental Web Bot Auth profile. All remain functional throughout 3.x and are expected to be removed in 4.0. Normative changes that narrow conformant behavior, and the guarantees that loosen, are described under [Behavior changes to review](#behavior-changes-to-review). This section is the cumulative 3.3 narrative and is refreshed at each prerelease cut; `CHANGELOG.md` records what each individual cut consumed. -**Where to start:** [What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3) is the adopter overview. [Migrating from 3.2 to 3.3](/docs/reference/migration/3-2-to-3-3) has the role-based checklist. The [3.3 beta program](/docs/reference/3-3-beta) covers artifacts, SDK timing, and the proposals still in review. +**Where to start:** [What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3) is the adopter overview. [Migrating from 3.2 to 3.3](/docs/reference/migration/3-2-to-3-3) has the role-based checklist. The [3.3 prerelease program](/docs/reference/3-3-beta) covers artifacts, SDK timing, and the proposals still in review. AdCP 3.3 lets scheduled, human-gated, and offline media run through the same buy as programmatic. Bookings can say when they will be confirmed, proposal requests can target vendor-measured outcomes, governance plans can budget by period, and delivery reports carry what linear TV, print, and DOOH sellers actually know. The release also tightens the places where two conformant 3.2 implementations could still disagree, and keeps new single-adopter surfaces experimental. - **TMP cache isolation (3.3):** evaluation namespaces isolate Context Match caches and warm hits still re-authorize. Provider model changes use the existing TTL policy, with bounded staleness and advance TTL reduction ([#7446](https://github.com/adcontextprotocol/adcp/pull/7446), [migration](/docs/reference/migration/trusted-match-context-cache)). -### Beta checkpoints +### Prerelease checkpoints | Release | Published | Purpose | SDK posture | |---|---|---|---| @@ -29,20 +29,22 @@ AdCP 3.3 lets scheduled, human-gated, and offline media run through the same buy | `3.3.0-beta.3` | 2026-10-31 | Live creative updates, the protocol envelope composed on every task response, money terms on resolved account requests, revocation as no access, and reporting-subscription coverage computable from the wire | `@adcp/sdk` 17.0.0-beta.11 through 17.0.0-beta.17 bundle this release | | `3.3.0-beta.4` | 2026-11-05 | Reporting-subscription coverage fixes (per-package `added_at`, a grant reduced without `get_reporting_status` as a loss of authority, schema-enforced durations) and the probe reset, `replace` that transfers assignment settings, tracker-slot limits only where a format declares slots, `BUDGET_TOO_LOW` details, `creative.supports_provenance`, `opportunity` on explicit-package buys, undefined-property reporting, and the hold, account-request, and reporting-subscription storyboards | `@adcp/sdk` 17.0.0-beta.18 through 17.0.0-beta.20 and Python `adcp` 10.0.0b12 support this release | | `3.3.0-beta.5` | 2026-11-07 | Experimental match keys for cross-publisher frequency capping, `sales-fixed-rate` promoted to stable, the bundled Public Suffix List (DR-0037), and offline legacy creative fixtures | `@adcp/sdk` 17.0.0-beta.21 through 17.0.0-beta.23 and Python `adcp` 10.0.0b13 through 10.0.0b16 support this release | +| `3.3.0-beta.6` | 2026-11-13 | Schemas open by default (DR-0036), the closed-schema triage that withdraws or moves the beta fields on deprecated tasks and on the commercial terms held closed until 4.0, the versioning rules for what changes between releases (#8704), origin-only `authorized_agents` URLs (#8939), declared-option creative conformance (#8941), TMP Context Match cache isolation (#7446), `creative.supports_registry_policy_enforcement` (#8857), `3gp`, `mpeg`, and `m4v` video containers (#8668), carousel `card_image_sizes` (#8937), loosened URL patterns (#8792), signed terms that bind every member (#8884), the experimental `https_put` reporting transport with no buyer secrets (#8793), `media_buy.supported_delivery_types` (#8458), display labels for geo targeting codes (#8966), experimental installment refinement (#8974) and per-installment creative assignment (#8972), and report definitions at `contract_version` `1.2` that carry `package_id` (#8983) | `@adcp/sdk` 17.0.0-beta.24 and later and Python `adcp` 10.0.0b17 and later support this release | +| `3.3.0-rc.0` | 2026-11-16 | First release candidate: everything in beta.6, plus prerelease pins, unpinned discovery, and anonymous capabilities, declared `sync_creatives` assignment operations (#8997), audience targeting without member push (#8996), carousel card `cta_values` (#9001), inline `submitted` branches aligned with their status files (#8934), the `by_package` guidance (#8970), scope and `signing_keys` rules for several matching `authorized_agents` entries (#9011, #9017), three renamed experimental values (#8989), an omitted `human_review_required` accepted by campaign governance (#9007), compliance gates for `audience_buy_flow` and `inline_creatives_without_sync` (#9013, #9005), the public test agent's `3.3-beta.6` preview (#9018), and the Instagram, Facebook, Snapchat and X distribution identifier types (#8995) | No published SDK supports it yet; new TypeScript and Python prereleases follow the cut | -Each beta is immutable. The `3.3-beta` documentation selector advances to the latest beta, while pinned protocol, schema, compliance, and documentation artifacts remain available. See the [3.3 beta program](/docs/reference/3-3-beta). +Each prerelease is immutable. The `3.3-beta` documentation selector stays at beta.5, and `3.3-rc` advances to the latest release candidate, while pinned protocol, schema, compliance, and documentation artifacts remain available. See the [3.3 prerelease program](/docs/reference/3-3-beta). ### 3.3 feature index - **Scheduled and human-gated buying:** `expected_confirmation_at` on `submitted` envelopes (#8016) and on `refine_proposals` finalize and hold extension (#8104, #8203); experimental `hold_policy`, `extend_hold`, hold ranking, and per-installment hold readback (#8140, #8097, #8255, #8257); experimental delegated composition with `product_ids_exclusive` and `terms_only` finalize (#7954); vendor-metric `outcome_target` goals (#7966); experimental governance `budget.periods[]` and `governance.supports_budget_periods` (#7965); `change_cutoff` on installment deadlines (#8054). -- **Proposals and media buys:** experimental open opportunities with later proposals, `proposal.created`, and `list_proposals`, which also reads seller offers and filters by `media_buy_ids` (#8103, #8223); seller revisions advance on every committed change from any origin, with `history[].origin` and the creative `seller_revision` (#8159, DR-0031); the stable `sales-fixed-rate` specialism for fixed-price, non-guaranteed sellers (DR-0028), with `expected_confirmation_at` on `get_media_buys` (#7963); experimental forward-only lineage with `predecessor_media_buy_id` and `lineage_reason` (#8038); `error.mutation_outcome` on failed mutations (#7935); the `operator_fee` price adjustment kind (#8356). +- **Proposals and media buys:** experimental open opportunities with later proposals, `proposal.created`, and `list_proposals`, which also reads seller offers and filters by `media_buy_ids` (#8103, #8223); seller revisions advance on every committed change from any origin, with `history[].origin` and the creative `seller_revision` (#8159, DR-0031); the stable `sales-fixed-rate` specialism for fixed-price, non-guaranteed sellers (DR-0028), with `expected_confirmation_at` on `get_media_buys` (#7963); experimental forward-only lineage with `predecessor_media_buy_id` and `lineage_reason` on `buy_products` and `accept_proposal` (#8038; withdrawn from `create_media_buy` at rc.0); `error.mutation_outcome` on failed mutations (#7935); the `operator_fee` price adjustment kind (#8356). - **Delivery reporting:** `impressions` optional on delivery rows, version-gated (#8108); experimental spot lifecycle, makegood linkage, and break position (#8017); experimental print proof of insertion and circulation (#7936); experimental delivery `projection` on `by_package[]` rows (#8043); experimental installment lifecycle and proof of publication on `by_installment[]` rows (#8116); flat totals omitted for multi-qualifier metrics (#8055); property-grain rollup capabilities (#7982); `reporting_webhook.operation_id` (#7895); `reporting_webhook.authentication` and `artifact_webhook.authentication` optional on 3.3 requests (#8177); receivers ignore `aggregated_totals` in delivery webhooks (#8053); `custody` on Reliable Reporting report definition sources (#8213). - **Channels:** structured DOOH `location` and `dooh_inventory_summary.venue_counts[]` (#7416); experimental minute-level dayparts (#8025); `nmo` and `videoamp` demographic systems, `mxf` and broadcast mezzanine codecs, and experimental `loudness` (#8019); the expanded broadcast TV guide (#8006). - **Accounts and audiences:** discovery and negotiation tasks never provision an account (#7848); the deprecation of natural-key account references after provisioning (#8123) and the `account.stable_account_id` capability (#8123, #8124), which the account identity model below deprecates; audience sizes as ranges and `match_rate_basis` (#8024); the `uids[].value` wire form per type (#8059); `invoice` records on the experimental account change feed (#8095); the change feed's `idempotency_key` echo and required `changed_paths` (#8160). - **Account identity and requests (beta.1 to beta.3):** a brand is its domain, plus `brand_id` where its `brand.json` lists several; an account is the seller's `account_id`, and `countries`, `currency`, `timezone`, `sandbox`, and `operator_unit` are attributes (#8474, #8280, #8442). Sellers MUST return and accept `account_id`; `sync_accounts` settings updates change attributes in place. The identity-rekey machinery is deprecated: `account.identity_updates`, `operator_identity`, `ACCOUNT_MOVED`, `ACCOUNT_IDENTITY_CONFLICT`, and `account.stable_account_id`. Experimental `account.requests`: `request_account` and its pending action (#8293), the single account write where supported, with `list_accounts` request reads (#8551), change outcomes `updated`, `matched`, and `created` (#8580), the opt-in `allow_separate_account` and `ACCOUNT_CHANGE_REQUIRES_NEW_ACCOUNT` (#8582), and money terms on resolved requests (#8620). - **Reporting subscriptions (experimental, beta.1 to beta.3):** `reporting_subscriptions` on `sync_principal` and exceptions-only `subscription_coverage` on `get_reporting_status`, under `media_buy.reporting_subscriptions` ([#8543](https://github.com/adcontextprotocol/adcp/issues/8543) Part B, #8552). Beta.2 and beta.3 settle the SDK findings and make coverage computable from the wire: #8585, #8588, #8593, #8596, #8607 (revocation means no access), #8613, #8616 (canonical vectors), #8617, #8618, #8619, #8621 (`reporting_subscription_probe`), and #8622. -- **Commercial experiments (beta.1 and beta.2):** seller offers against an accepted buy, `media_buy.seller_offers` (#8102); selection-dependent `price_adjustments` on fixed-price pricing options, `media_buy.price_adjustments` (#7955); per-account execution readiness on `get_products`, `media_buy.execution_readiness` (#7934); `target_audiences[]` beside audience evidence requirements, `media_buy.audience_evidence_targets` (#8215); invoice lines on `get_account_financials`, `account.invoice_lines` (#8207); `media_buy.measurement_provenance`, a `collection-mechanism` vocabulary on `counting_mechanisms[]` and `vendor_metric_provenance[]` (#7940). -- **Targeting and rosters:** experimental core gender targeting, `media_buy.gender_targeting` (#7925); an empty `publisher_properties` or `collections` list means the seller does not disclose the roster, with exclusions as the buyer's choice (#7948); optional structured package inputs for exact `get_products` availability checks (#8468). +- **Commercial experiments (beta.1 and beta.2):** seller offers against an accepted buy, `media_buy.seller_offers` (#8102); selection-dependent `price_adjustments` on fixed-price pricing options, `media_buy.price_adjustments` (#7955; withdrawn at rc.0 and planned for 4.0); per-account execution readiness, `media_buy.execution_readiness` (#7934; on `list_products` from rc.0); `target_audiences[]` beside audience evidence requirements, `media_buy.audience_evidence_targets` (#8215; withdrawn at rc.0); invoice lines on `get_account_financials`, `account.invoice_lines` (#8207); `media_buy.measurement_provenance`, a `collection-mechanism` vocabulary on `vendor_metric_provenance[]` (#7940; `counting_mechanisms[]` withdrawn at rc.0). +- **Targeting and rosters:** experimental core gender targeting, `media_buy.gender_targeting` (#7925); an empty `publisher_properties` or `collections` list means the seller does not disclose the roster, with exclusions as the buyer's choice (#7948); optional structured package inputs for exact `get_products` availability checks (#8468; withdrawn at rc.0). - **Creative:** experimental live creative updates, `creative.live_updates`, with staged activation and `CREATIVE_LIVE_UPDATE_UNSUPPORTED` (#8488); `creative.assignment_operations` declares the `sync_creatives` assignment operations a seller accepts, and a seller declaring `creative.live_updates` lists `replace` (#8933); media-buy startup with mixed creative approval states and the optional `start_requires_all_creatives_approved` gate (#8485). - **Envelope and negotiation:** `core/protocol-envelope.json` composed on every task response, with `status` required and one definition each for `message` and `task_id` (#8547); a request carrying only `adcp_major_version` is served the oldest supported release in that major, 3.0 where supported (DR-0034); the schemas that were meant to be open opened, starting with the 3.2 proposal flow (#8531), and the rest stay closed where closure enforces something, with `commercial_terms` held closed until 4.0 (DR-0036); the buyer's registration selects the webhook-signing mode (#8475); condition (b) of `request_signature_required` deprecated and JSON-RPC batch bodies rejected (#8064). - **Capabilities:** every array, string, and keyed map in the `get_adcp_capabilities` response is bounded by structure, and the 64 KiB byte cap is a receiver backstop, not a design target (#8505, #8526). @@ -71,7 +73,8 @@ Each beta is immutable. The `3.3-beta` documentation selector advances to the la - **Served-release conformance (beta.4):** senders SHOULD NOT emit properties the served release does not define, outside `ext.{namespace}` and `x-adcp-open-payload` fields, and the runner reports them through the advisory `undefined_properties` check (#8156). - **Public Suffix List (beta.5):** verifiers compute eTLD+1 with a Public Suffix List bundled with the verifier, never fetched at runtime; AdCP names no reference snapshot (#8702, DR-0037). - **Conformance (beta.4 and beta.5):** the `account_requests` storyboard (#8677); the reporting-subscription coverage and capacity storyboards with the advisory `owed_periods_match` check (#8680, #8724); six hold storyboards and the advisory `instant_offset_within` check (#8696); `media_buy_seller/assignment_replace_transfers_settings` (#8695); `sales-fixed-rate` promoted from preview to stable (#8445); `deterministic_testing` scoped to one sandbox account (#8731); offline legacy creative fixtures (#8684); and dependent observations skipped when controlled forcing is unavailable (#8642). - +- **beta.6:** the schemas that were meant to be open open, and the closed-schema triage withdraws or moves beta fields (#8866, #8501, below); an origin-only `authorized_agents[].url` in `adagents.json` authorizes the agent at that origin, whatever its path (#8939); a seller accepts a creative that conforms to the format option it targets (#8941); experimental TMP Context Match caches partition by trusted evaluation namespace (#7446); optional `creative.supports_registry_policy_enforcement` gates the policy-backed rejection storyboard (#8857); `3gp`, `mpeg`, and `m4v` video containers (#8668); optional `card_image_sizes` on `image_carousel` (#8937); seventeen URL patterns loosened to `^https://` (#8792); the rules for what changes between releases (#8704); accepting signed commercial terms binds every member, with `UNRECOGNIZED_TERMS` and the `unrecognized_terms` decline reason (#8884); Reliable Reporting managed delivery holds no buyer secret, row push is `reporting_webhook`, and an experimental `https_put` `file_transfer` transport writes signed objects to a buyer HTTPS endpoint (#8793); `media_buy.supported_delivery_types` declares whether a seller sells `guaranteed` or `non_guaranteed` inventory, or both (#8458); targeting can carry display names beside its geographic codes, `geo_value_labels` for ISO country and subdivision codes and `value_labels` on metro and place entries, and they never change what is targeted (#8966); Reliable Reporting report definitions at `contract_version` `1.2` require a `package_id` dimension whenever they include `media_buy_id` (#8983); experimental installment refinement: choose specific installments in `refine_proposals` with `installment_changes`, answered with a product whose installments are the chosen set, `media_buy.installment_refinement` (#8974), and per-installment creative assignment with `installment_refs` on `sync_creatives` `assign` and `replace` operations, `media_buy.installment_creative_assignment` (#8972). +- **rc.0:** everything in beta.6, plus prerelease pins, unpinned discovery, and anonymous capabilities; Instagram, Facebook, Snapchat and X distribution identifier types, each a canonical ID plus a handle alias (#8995); sellers declare the `sync_creatives` assignment operations they accept in `creative.assignment_operations`, and a seller declaring `creative.live_updates` lists `replace` (#8997); `media_buy.audience_targeting` promises audience overlays and discovery-only `sync_audiences`, not inline member push (#8996); optional `cta_values` on `image_carousel` constrains each card's `cta` (#9001); the inline `submitted` branches of eight tasks match their published async status files (#8934); `get_media_buy_delivery` sellers SHOULD return at least one `by_package` row, one per package, and omit a buy they can't report (#8970); when several `authorized_agents[]` entries match one agent, its scope is the union of theirs, and a `signing_keys` pin holds only if every entry that matches and authorizes the message pins keys (#9011, #9017); three experimental values take their counterparts' spelling, with no alias: `input_required` → `input-required` (`media_buy.execution_readiness`), `click_through` → `clickthrough` (`creative.live_updates`), and `underdelivery` → `under_delivery` (`media_buy.delivery_projection`) (#8989); campaign governance accepts a `sync_plans` plan that omits `human_review_required` and states two `sync_plans` validation rules (#9007); in compliance, `audience_buy_flow` pushes members only to sellers that accept inline pushes (#9013), and `inline_creatives_without_sync` sends `format_option_ref` (#9005); the public test agent's opt-in preview moves to `3.3-beta.6` (#9018). ### Behavior changes to review - **Discovery never provisions (#7848).** Discovery and negotiation tasks MUST NOT create or activate an account or accept default terms. A lazily provisioning seller provisions only on a task that commits spend or creates account-owned resources. This narrows the 3.2 wording "first account-scoped request". Schemas are unchanged. @@ -109,6 +112,17 @@ Each beta is immutable. The `3.3-beta` documentation selector advances to the la - **Assignment operations are declared (#8933).** A seller lists the `sync_creatives` `assignment_operations` it accepts in `creative.assignment_operations` and rejects any other with `UNSUPPORTED_FEATURE`. Absent from a response served at 3.3, the seller accepts none and buyers MUST NOT send `assignment_operations`; a 3.2 response cannot carry the list. A seller declaring the experimental `creative.live_updates` MUST list `replace`, a seller that exposes `buy_products` or `accept_proposal` with a creative library MUST list `assign`, and `supports_assignment_merge: true` requires `merge` in the list. A recovery names `replace` only where the seller lists it. Error suggestions SHOULD name only operations and fields the agent accepts. - **Senders don't emit undefined properties (#8156).** A sender SHOULD NOT emit a property the served release does not define, except under `ext.{namespace}` or inside `x-adcp-open-payload` fields: a misnamed field is silently ignored, and on `get_adcp_capabilities` it reads as the field's default. - **The Public Suffix List is bundled (#8702, DR-0037).** Verifiers compute eTLD+1 with a list bundled with the verifier and refreshed through dependency updates, never fetched at runtime. Two verifiers on different list versions are no longer non-conformant against each other. On the trust-record path, a verifier whose list lacks a newly added PRIVATE suffix fails closed. +- **Schemas are open by default (#8866, DR-0036, rc.0).** 744 of the 859 closed locations in the 3.3 schemas open. 115 stay closed: most for a structural reason such as `oneOf` disjointness or a closed key set, and the nodes inside `commercial_terms`, with `proposal-budget-constraint`, are held closed until 4.0. Every payload that was valid stays valid. Where closure also rejected a specific field, the opened schema names it, so that payload is still rejected. Generated types change: opened objects gain index signatures in TypeScript, Pydantic models stop forbidding extra fields, and Zod validators accept unknown keys. A strict validator built from 3.2.10 or earlier still rejects 3.3 fields, so send them only to 3.3 peers. 3.2.11 (#8864) opens the same locations in 3.2. See [Schemas are open by default](/docs/reference/migration/3-2-to-3-3#schemas-are-open-by-default). +- **Prerelease pins and anonymous discovery (rc.0).** A buyer MUST send a prerelease `adcp_version` only to a peer that advertises that exact value, SHOULD discover unpinned, and SHOULD retry unpinned or at a listed version on `VERSION_UNSUPPORTED`. A seller SHOULD serve `get_adcp_capabilities` without credentials (a MUST in 4.0), and an MCP gateway SHOULD let `server/discover`, `initialize`, and `tools/list` through without credentials. See the [migration guide](/docs/reference/migration/3-2-to-3-3#prerelease-pins-unpinned-discovery-and-anonymous-capabilities). +- **Closed-schema triage (#8501, rc.0).** Beta fields on deprecated tasks, and fields that would extend a schema held closed until 4.0, leave 3.3; fields withdrawn only because their schema was closed stay. See [Closed-schema triage](/docs/reference/migration/3-2-to-3-3#closed-schema-triage-what-stays-in-3-3) for every field. The `metric_id` withdrawal and the `evaluator` restoration (#8854) are in review, not in rc.0. +- **Sellers accept creatives that conform to the declared format option (#8941, rc.0).** A seller MUST NOT refuse a creative with a conformance code on the grounds of a declared parameter the creative satisfies, and MUST NOT enforce a narrower value than the one declared. A closed set such as `cta_values` narrows a slot only when declared. A seller that enforced undeclared limits now fails `media_buy_seller/declared_format_option_acceptance`. See [the migration guide](/docs/reference/migration/3-2-to-3-3#sellers-accept-creatives-that-conform-to-the-declared-format-option). +- **Accepting signed terms binds every member (#8884, rc.0).** `terms_digest` covers the whole `commercial_terms` value, including members under the open schemas inside it and members a party does not recognize. A party that cannot interpret every member MUST NOT accept: a buyer declines with the `unrecognized_terms` reason, a seller rejects the request with `UNRECOGNIZED_TERMS`, and a governance agent denies the check. Compute or verify the digest over the JSON value as received, never over a re-serialized model. See [Verify terms independently](/docs/media-buy/product-discovery/proposal-negotiation#3-verify-terms-independently). +- **Reliable Reporting holds no buyer secret (#8793, rc.0, experimental).** For every managed delivery pattern the seller authenticates as itself, through its advertised `producer_identity`, and MUST NOT hold, request, or store a caller-issued secret of any kind (password, API key, bearer token, OAuth client secret, private key, signed URL, or shared signing key), directly or through a processor. Rows in an HTTP request body are the Core `reporting_webhook` transport, never `file_transfer`. The new `https_put` transport is conformant only when the manifest is written last, every request is signed under the Web Bot Auth profile, and the endpoint passes a signed probe before `ready`. +- **Report definitions at `contract_version` `1.2` (#8983, rc.0, experimental).** A `1.2` Reliable Reporting report definition keeps every `1.1` rule. When its `dimensions` include `media_buy_id`, they MUST include `package_id`, so every row names the buyer-visible package, and the offering's `reporting_profile.primary_keys` includes `package_id`. A definition without `media_buy_id`, such as an account-level summary, is exempt. `1.0` and `1.1` definitions are unchanged, and graders SHOULD flag a missing `package_id` there as advisory. Callers pinned below 3.3 accept only `1.0` and `1.1`, so a seller MUST serve them `1.0` or `1.1` offerings. Subscription selectors still call the breakdown `package`. +- **Three experimental values renamed (#8989, rc.0, experimental).** `input_required` → `input-required` (`media_buy.execution_readiness`), `click_through` → `clickthrough` (`creative.live_updates`), and `underdelivery` → `under_delivery` (`media_buy.delivery_projection`). The betas are immutable, so an implementation built from a beta bundle changes to the new spelling; there is no alias. +- **Loosened: an omitted `human_review_required` is accepted (#9007, rc.0, experimental).** A `sync_plans` plan that declares a regulated policy category or `eu_ai_act_annex_iii` may omit `human_review_required`, and the governance agent derives it from the plan's resolved policies; an explicit `false` is still rejected. `human_review_required` loses its `default: false`. `flight.end` must be later than `flight.start`, and policy IDs must not repeat or collide, else `INVALID_REQUEST`; the schema does not enforce these two rules in 3.x. +- **Delivery reports carry a row per package (#8970, rc.0).** `get_media_buy_delivery` sellers SHOULD return at least one `media_buy_deliveries[].by_package` row, one per package in the buy, and SHOULD omit a buy they can't report and return an error rather than an empty `by_package`. `by_package: []` stays valid in 3.x; requiring at least one row (`minItems: 1`) is proposed for 4.0 in #8973. +- **Loosened: origin-only `authorized_agents[].url` (#8939, rc.0).** An entry with the root path and no query authorizes the agent at any path on that canonical origin. An entry with a path still matches only that URL. Matching only widens: no entry that authorized an agent under 3.2 stops authorizing it, but a 3.2 validator rejects an agent a 3.3 validator accepts. - **Loosened: tracker slots (#8715).** A seller applies tracker-slot limits only when the effective format declares a tracker slot. Against a format that declares none, such as canonical `image`, it no longer rejects an assignment tracker for lack of a slot; it fires every accepted tracker or rejects the assignment. - **Loosened: brand.json cap 2 MiB (#8057).** A verifier still enforcing 256 KiB rejects a brand.json a 3.3 verifier accepts. - **Loosened: audience match counts (#8024).** A `ready` audience no longer promises `matched_count` and `effective_match_rate`. @@ -119,15 +133,16 @@ Each beta is immutable. The `3.3-beta` documentation selector advances to the la - **Loosened: attestation and reporting URL patterns (#8398).** Seventeen `format: uri` fields in the `core/attestation-*` schemas, `core/product-audience-evidence-requirements.json`, and the `core/reporting-*` schemas check the `https` scheme only. The attestation URLs no longer refuse a fragment or userinfo, and the reporting document URIs and `operations_contact.url` no longer refuse an IP literal, `localhost`, or a single-label host. A 3.2 sender's value still validates. Fetchers still reject those values under the [attestation fetch contract](/docs/building/by-layer/L1/security#attestation-resolution-fetch-contract), `safe_schema_fetch`, `safe_attestation_fetch`, and the general SSRF rules. `operations_contact.url` is never fetched, and it still never carries credentials or userinfo. The origin-shaped fields and `source_repository` keep their patterns. - **Loosened: product rosters (#7948).** `publisher_properties` and `collections` lose `minItems: 1`, so generated types change for every product (a TypeScript non-empty tuple becomes `T[]`). - **Deprecated: RFC 9421 signing profiles (#8162).** `adcp/request-signing/v1` and `adcp/webhook-signing/v1` keep working through 3.x and are removed in 4.0. The replacement is the experimental Web Bot Auth profile; see the [agent identity migration guide](/docs/reference/migration/agent-identity-3-3). -- **Deprecated: `seller_id` on event source and audience results (#8290).** Use `platform_id`; the alias keeps working through 3.x, removal no earlier than 4.0. +- **Deprecated: `seller_id` on event source and audience results (#8290).** Use `platform_id`; the alias keeps working through 3.x and is expected to be removed in 4.0. - **Deprecated: natural-key account references after provisioning (#8123).** They keep working through 3.x and are planned for removal in 4.0; sellers SHOULD declare `account.stable_account_id`. See [Deprecations](/docs/reference/migration/3-2-to-3-3#deprecations). - **Deprecated: the account identity-rekey machinery (#8474).** `account.identity_updates`, `operator_identity` and `destination_billing_entity` on `sync_accounts`, `identity_change` and `identity_change_preview`, `ACCOUNT_MOVED`, `ACCOUNT_IDENTITY_CONFLICT`, and `account.stable_account_id` keep working through 3.x and are planned for removal in 4.0. An account's identity never changes, so there is nothing to rekey. - **Deprecated: `principal_kind` and `expected_principal_kind` (#8443).** A principal is the buyer agent as the seller has bound it, so the kind is always `buyer_agent`. Sellers keep returning and honoring them through 3.x, and `enums/principal-kind.json` is deprecated with them. - **Deprecated: condition (b) of `request_signature_required` (#8064).** It exists only for the deprecated webhook `authentication` block and is removed in 4.0 with it. - **Deprecated: `configuration_task` in `media_buy.reporting_delivery` (experimental, #8552).** Sellers list accepted registration tasks in `configuration_tasks[]`; `configuration_task` stays `"sync_accounts"` for callers pinned below 3.3. +- **Deprecated: the boolean form of `demographics` (#8866, from #8772).** In product `overlay_support` and in `required_overlay_support`, `demographics: true` is the 3.2 shorthand for `{ "age": true }`. Senders MUST send the object form. Receivers MUST accept `true` and read it as `{ "age": true }`, so it satisfies an age requirement and never a `gender` requirement. It is planned for removal in 4.0 ([#8778](https://github.com/adcontextprotocol/adcp/issues/8778)). - **Reminder, not new in 3.3: `adcp_major_version` is removed in 4.0 ([DR-0035](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0035-adcp-major-version-removed-in-4-0.md)).** The integer request field and the `adcp.major_versions` capability field have been deprecated since 3.1. They keep working through 3.x, and 4.0 removes both. Send `adcp_version` on every request, keeping the `adcp_major_version` mirror through 3.x. In-house clients that still send only the integer should switch before 4.0. The compliance grader already blocks sellers that do not echo `adcp_version` or emit `adcp.supported_versions`, and at 4.0 rejects the legacy fields. -Each is detailed in the [migration guide](/docs/reference/migration/3-2-to-3-3#required-to-claim-3-3-behavior) and recorded in [3.3 exceptions to 3.x compatibility](/docs/reference/versioning#3-3-exceptions-to-3-x-compatibility-beta). Fields that a 3.2 validator rejects, and so are sent only on a negotiated 3.3 version, are listed in [Send only to 3.3 peers](/docs/reference/migration/3-2-to-3-3#send-only-to-3-3-peers). Schema-shape changes for SDK generators are in [SDK and code-generator maintainers](/docs/reference/migration/3-2-to-3-3#sdk-and-code-generator-maintainers). 3.3 removes no stable field, task, or enum value. It deprecates a few result fields and capabilities (`seller_id`, `principal_kind`, the identity-rekey machinery), one usage, one signing condition, and the RFC 9421 signing profiles, listed above. The `adcp_major_version` reminder restates an existing 3.1 deprecation. +Each is detailed in the [migration guide](/docs/reference/migration/3-2-to-3-3#required-to-claim-3-3-behavior) and recorded in [3.3 exceptions to 3.x compatibility](/docs/reference/versioning#3-3-exceptions-to-3-x-compatibility-beta). Fields that a 3.2 validator rejects, and so are sent only on a negotiated 3.3 version, are listed in [Send only to 3.3 peers](/docs/reference/migration/3-2-to-3-3#send-only-to-3-3-peers). Schema-shape changes for SDK generators are in [SDK and code-generator maintainers](/docs/reference/migration/3-2-to-3-3#sdk-and-code-generator-maintainers). 3.3 removes no stable field, task, or enum value. It deprecates a few result fields and capabilities (`seller_id`, `principal_kind`, the identity-rekey machinery), the boolean form of `demographics`, one usage, one signing condition, and the RFC 9421 signing profiles, listed above, each expected to be removed in 4.0. The `adcp_major_version` reminder restates an existing 3.1 deprecation. ### Experimental surfaces in 3.3 @@ -145,9 +160,9 @@ Per the [experimental status contract](/docs/reference/experimental-status#gradu | `account.agent_onboarding` | `account.agent_onboarding` on `get_adcp_capabilities` and the buyer posture in trust.json (#8170) | New in 3.3; experimental | The mode and requirement vocabulary may change as sellers publish it. `open` needs the Web Bot Auth profile. | | `security.profiles` | `security_profiles` on `get_adcp_capabilities` and the `adcp-prod-security-3.3` profile (#8155) | New in 3.3; experimental | Requirements may change as the seller and buyer storyboards land; a changed requirement ships under a new profile id. Rejecting non-conforming counterparties becomes a MUST in 4.0. | | `media_buy.open_opportunities` | `list_proposals`, `opportunity.later_proposals`, `proposal.created`, `opportunity.status: "open"` on `accept_proposal` and `buy_products`, and the capability block (#8103); seller-offer reads and the `media_buy_ids` filter (#8223) | New in 3.3; experimental | The default consent limits, the disposition vocabulary, and the 30-day terminal retention may change once sellers and buyers run it. | -| `media_buy.lineage` | `predecessor_media_buy_id` and `lineage_reason` on buy creation and `get_media_buys`, and the `predecessor_media_buy_id` filter (#8038) | New in 3.3; experimental | The `lineage_reason` vocabulary may grow; the same-account scope and the `UNSUPPORTED_FEATURE` rejection may change. | +| `media_buy.lineage` | `predecessor_media_buy_id` and `lineage_reason` on `buy_products`, `accept_proposal`, and `get_media_buys`, and the `predecessor_media_buy_id` filter (#8038; withdrawn from `create_media_buy` at rc.0) | New in 3.3; experimental | The `lineage_reason` vocabulary may grow; the same-account scope and the `UNSUPPORTED_FEATURE` rejection may change. | | `media_buy.delivery_projection` | `projection` on top-level `by_package[]` delivery rows (#8043) | New in 3.3; experimental, advisory | The `basis` vocabulary is expected to grow, and the `complete` / `early_exhaustion` split needs field experience. | -| `media_buy.installment_lifecycle` | `installment_status` and `publication` on `by_installment[]` rows, and `available_installment_statuses` (#8116) | New in 3.3; experimental | A publish notification is planned for 3.4 and may reshape how buyers learn of publication. Rows with new statuses are omitted for callers below 3.3. | +| `media_buy.installment_lifecycle` | `installment_status` and `publication` on `by_installment[]` rows, and `available_installment_statuses` on the canonical product's `reporting_capabilities` (#8116; moved from the legacy product's in rc.0, #8957) | New in 3.3; experimental | A publish notification is planned for 3.4 and may reshape how buyers learn of publication. Rows with new statuses are omitted for callers below 3.3. | | `media_buy.collection_lists` | `collection_lists` and `collection_lists_exclude` targeting with `max_references` (#8061) | New in 3.3; experimental | The intersection and union semantics and the `max_references` shape are not yet ratified. The singular `collection_list` fields are stable and unchanged. | | `signals.signal_lifecycle` | `signal_status` and `source_audience_id` on `get_signals` results, and `signals.features.signal_lifecycle` (#8036) | New in 3.3; experimental | The wholesale-feed-version and buyer-scoping rules may change as more signal agents build segments. | | `protocol.principal` | Adds `relationship` status on `get_principal` and the `relationship_changed` and `relationship_expiring` reasons on `principal.changed` (#8168) | Still experimental; additive change | No graduation planned for 3.3. | @@ -158,28 +173,32 @@ Per the [experimental status contract](/docs/reference/experimental-status#gradu | `media_buy.installment_holds` | The committed proposal's `holds` array (#8257) | New in 3.3; experimental, readback only | Per-entry `expires_at` only if partial holds are ever allowed. Omitted for callers below 3.3. | | `media_buy.hold_extension` | `refine_proposals` `extend_hold` and `proposal_refinement.hold_extension` (#8097) | New in 3.3; experimental | Interaction with per-installment holds may reshape the action and result. | | `media_buy.delegated_composition` | `criteria.product_ids_exclusive`, `supports_exclusive_product_ids`, `hold_semantics: "terms_only"` (#7954) | New in 3.3; experimental, no validated adopters | The acceptance-only `accept_proposal` variant, the governance trigger, and a reference-based product universe are open. | -| `media_buy.collection_cards` | Collection `images`, `sample_content`, `url`; talent `brand_ref`; `distribution[].followers`; response `collections` with `include_collections` (#8094, #8098, #8141) | New in 3.3; experimental | Array bounds, the copy-wins field list, and follower-count placement may change. | +| `media_buy.collection_cards` | Collection `images`, `sample_content`, `url`; talent `brand_ref`; `distribution[].followers`; response `collections` with `include_collections` on `list_products`, `request_proposals`, and `refine_proposals` (#8094, #8098, #8141; withdrawn from `get_products` at rc.0) | New in 3.3; experimental | Array bounds, the copy-wins field list, and follower-count placement may change. | | `media_buy.collection_catalog` | `list_collections`, `collections_version` tokens, and collection card webhook events (#8279) | New in 3.3; experimental, no emitting agent yet | Requires `media_buy.collection_cards`; webhook shape may change. | | `brand.collection_links` | `collections` on `get_brand_identity` and `publisher_domain` on brand.json collection links (#8141) | New in 3.3; experimental | Link shape, visibility, and `seller_agent_url` may change. | | `creative.evaluator` | The `evaluator_id` source form on `build_creative.evaluator` is removed and the `list_evaluators` follow-on is withdrawn (#5241). Sources are inline `exemplars` or an allowlisted `agent_url`. | Still experimental; breaking removal | The 6-week pre-landing notice is waived: beta.0 is the notice vehicle, and GA ships no earlier than 6 weeks after the beta.0 tag ([migration](/docs/reference/migration/3-2-to-3-3#experimental-creative-evaluator-drops-evaluator_id)). A fourth source form for conversion-outcome evaluators stays open until an adopter appears. | -| `media_buy.reporting_delivery` | Reliable Reporting 1.0; `REVISION_UNREADABLE` shipped in 3.2.4 (#8099); `custody` on report definition sources (#8213) | Still experimental; two active breaking-change notices | The [consumer-status requirement](/docs/reference/migration/reliable-reporting-status-loop) has not merged; it may land no earlier than the first minor after October 24, 2026. [Superseded snapshot compaction](/docs/reference/migration/3-2-to-3-3#superseded-reporting-snapshots-may-be-compacted) (#8100) takes effect no earlier than the first minor after November 20, 2026, so not in 3.3 if 3.3 ships before then. | +| `media_buy.reporting_delivery` | Reliable Reporting 1.0; `REVISION_UNREADABLE` shipped in 3.2.4 (#8099); `custody` on report definition sources (#8213); no buyer secrets for managed delivery and the `https_put` `file_transfer` transport (#8793, rc.0); report definition `contract_version` `1.2`, which requires `package_id` with `media_buy_id` (#8983, rc.0) | Still experimental; two active breaking-change notices | The [consumer-status requirement](/docs/reference/migration/reliable-reporting-status-loop) has not merged; it may land no earlier than the first minor after October 24, 2026. [Superseded snapshot compaction](/docs/reference/migration/3-2-to-3-3#superseded-reporting-snapshots-may-be-compacted) (#8100) takes effect no earlier than the first minor after November 20, 2026, so not in 3.3 if 3.3 ships before then. | | `account.requests` | `request_account` (open or change an account), `request_id`, `include_requests`, and `account_requests[]` on `list_accounts`, the `account_request.changed` webhook, `request_id` and `resolution` on `sync_accounts` results (#8293, #8551); change outcomes, `allow_separate_account`, and `ACCOUNT_CHANGE_REQUIRES_NEW_ACCOUNT` (#8580, #8582); money terms, `effective_at`, and `not_carried_over` on resolved requests (#8620) | New in 3.3; experimental, no adopter yet | The pending-action kinds, the 30-day retention floor, the deduplication guidance, and how requests compose with agent onboarding and operator grants need working-group review. `sync_accounts` stays stable; its formal deprecation follows this surface leaving experimental status. | | `media_buy.reporting_subscriptions` | `reporting_subscriptions` on `sync_principal`, `subscription_coverage` on `get_reporting_status`, offering `standard_dimensions`, `configuration_tasks[]` (#8552); the beta.2 and beta.3 convergence: owed confirmation period, `inactive` coverage, billing stubs, `flight_history` and `regranted_at` on the wire, deterministic admission and resolution, revocation as no access (the PRs are in the [feature index](#3-3-feature-index)); the beta.4 coverage fixes: per-package `added_at`, a reduced grant as a loss of authority, `SUBSCRIPTIONS_REQUIRE_ACCOUNT_ID_KEY`, and `reset_state` (#8718, #8717) | New in 3.3; experimental, no adopter yet | The dimension vocabulary, `exact` as the default match, backfill on re-grant, and whether billing feeds may use all-accounts scope are open. `reporting_subscription_probe` and the canonical coverage vectors let a seller test against the reference model. Builds on `media_buy.reporting_delivery`. | | `media_buy.seller_offers` | `proposal_initiator` on canonical proposals, `offer_reason` on `list_proposals` rows, the `proposal.offered` notification (#8102) | New in 3.3; experimental. Requires `media_buy.open_opportunities` | The `offer_reason` values and the `expired` disposition may change once sellers run real offers. Pre-agreed seller changes inside `commercial_terms` are planned for 4.0 with the other withdrawn features. Never sent to callers below 3.3. | | `creative.live_updates` | The `creative.live_updates` capability, `staged_update` on `list_creatives` and `sync_creatives`, `creative.staged_update_changed`, and `CREATIVE_LIVE_UPDATE_UNSUPPORTED` (#8488) | New in 3.3; experimental, one reference implementation | The change-kind taxonomy, the serving-mode ranking, and per-package review during a staged update need ad-server field evidence. | -| `media_buy.measurement_provenance` | `enums/collection-mechanism.json`, `billing_measurement.counting_mechanisms[]` on `measurement_terms`, and `vendor_metric_provenance[]` on delivery metrics (#7940) | New in 3.3; experimental, no production adopter yet | The vocabulary stays experimental until two parties have used it. `counting_mechanisms` reaches the closed canonical terms in 4.0. Sellers omit the fields toward callers pinned below 3.3. | -| `media_buy.audience_evidence_targets` | `target_audiences[]` beside `audience_evidence_requirements` on `get_products` filters and `create_media_buy` packages (#8215) | New in 3.3; experimental | Exact-match audience rules, AND across targets, and units of `minimum_value` may change. The closed purchase schemas gain the field in 4.0. | +| `media_buy.measurement_provenance` | `enums/collection-mechanism.json` and `vendor_metric_provenance[]` on delivery metrics (#7940); `billing_measurement.counting_mechanisms[]` on `measurement_terms` is withdrawn at rc.0 | New in 3.3; experimental, no production adopter yet | The vocabulary stays experimental until two parties have used it. `counting_mechanisms` is planned for the canonical measurement terms in 4.0. Sellers omit `vendor_metric_provenance[]` toward callers pinned below 3.3. | +| `media_buy.audience_evidence_targets` | `target_audiences[]` beside `audience_evidence_requirements`, on `get_products` filters and `create_media_buy` packages in the betas (#8215) | Withdrawn at rc.0; no 3.3 wire form, and sellers stop listing the feature id | Purchases gain the field in 4.0; any change to `list_products` `offer_filters` is 4.x. | | `account.invoice_lines` | `lines[]`, `invoice_kind`, and `adjusts_invoice_id` on `get_account_financials` invoices (#8207) | New in 3.3; experimental, reference only | Credit notes as `invoice_kind: credit_note` with a non-negative `amount` may change. Credit-note records are never sent to callers pinned below 3.3. | -| `media_buy.price_adjustments` | An ordered `price_adjustments` table of fee and discount rows on fixed-price pricing options (#7955) | New in 3.3; experimental, one pilot | Position in break, audience, activation method, and measurement vendor have no selectable anchor yet. A table is never returned to callers below 3.3. | -| `media_buy.execution_readiness` | `include_execution_readiness` on `get_products` and the response-level `execution_readiness` map (#7934) | New in 3.3; experimental. Pairs with the existing `media_buy.execution_requirements` | Identity selection, lead-form and messaging-destination requirements, and proposal bindings are not specified yet. | +| `media_buy.price_adjustments` | An ordered `price_adjustments` table of fee and discount rows on the legacy fixed-price pricing options, in the betas (#7955) | Withdrawn at rc.0; no 3.3 wire form | Planned for the canonical pricing option in 4.0. | +| `media_buy.execution_readiness` | `include_execution_readiness` on `list_products` and the response-level `execution_readiness` map (#7934; moved from `get_products` at rc.0) | New in 3.3; experimental. Pairs with the existing `media_buy.execution_requirements` | Identity selection, lead-form and messaging-destination requirements, and proposal bindings are not specified yet. | | `media_buy.gender_targeting` | Core `demographics.gender` targeting and product gender capabilities (#7925) | New in 3.3; experimental | Canonical demographic delivery reporting stays age-only in 3.3, so a gender-targeted package has exact targeting readback and no gendered delivery readback. Buyers never send core gender fields on a 3.2 contract. | | `signals.pricing_groups` | `pricing_group` on signal listings and `signal_pricing_group_rules[]` (#8058) | New in 3.3; experimental | The `signal_charges[]` echo of per-signal charges is a follow-up. A group with no rule is charged `each`. | | `signals.delivery_methods` | `signals.delivery_methods[]` capability, the `delivery_method` pin, and `delivery_status` on agent deployments (#8044) | New in 3.3; experimental, one implementer | Rail-selection authority, the arrival-state vocabulary, and match-outcome placement need integration experience. | | `media_buy.match_keys` | `core/match-key.json`, `enums/match-key-use.json`, `media_buy.supported_match_keys` on `get_adcp_capabilities`, `Product.identity.match_keys` (extending `media_buy.product_identity`), and `match_keys` on TMP provider registration (extending `trusted_match.core`) (#8446) | New in beta.5; experimental | Stays experimental at 3.3 GA. Graduation needs the conformance coverage in [#8451](https://github.com/adcontextprotocol/adcp/issues/8451); a `required_match_keys` filter on `get_products` is [#8450](https://github.com/adcontextprotocol/adcp/issues/8450). | -| `measurement.core`, `measurement.gateway`, `trusted_match.verified_identity`, `sponsored_intelligence.core`, `creative.signal_fanout`, `media_buy.audience_activation`, `media_buy.execution_requirements` | Unchanged in 3.3 | Still experimental | None merged. Open proposals that touch them are in the [3.3 beta program](/docs/reference/3-3-beta#in-review-for-3-3). | +| `media_buy.installment_refinement` | `installment_changes` (`include` or `omit`) on `refine_proposals`, `unsatisfied_installment_changes` on its result rows, and `installment_changes` in `proposal_refinement.supported_dimensions`; the seller answers with a product whose `installments[]` is the chosen set (#8974) | New in rc.0; experimental | Naming installments in the signed `purchases[].installments[]` waits for 4.0, with the `commercial_terms` extension point. | +| `media_buy.installment_creative_assignment` | `installment_refs` on `sync_creatives` `assign` and `replace` operations, read back on `get_media_buys` and `list_creatives` (#8972) | New in rc.0; experimental | Needs adopters before it can graduate. | +| `measurement.core`, `measurement.gateway`, `trusted_match.verified_identity`, `sponsored_intelligence.core`, `creative.signal_fanout`, `media_buy.audience_activation`, `media_buy.execution_requirements` | Unchanged in 3.3 | Still experimental | None merged. Open proposals that touch them are in the [3.3 prerelease program](/docs/reference/3-3-beta#in-review-for-3-3). | The [canonical list](/docs/reference/experimental-status#current-experimental-surfaces) is authoritative. +The closed-schema triage changed six of these rows at rc.0: `media_buy.price_adjustments` and `media_buy.audience_evidence_targets` are withdrawn, `media_buy.measurement_provenance` loses `counting_mechanisms[]` to 4.0, `media_buy.execution_readiness` moves to `list_products`, `media_buy.lineage` leaves `create_media_buy`, and `media_buy.collection_cards` leaves `get_products`. See [Closed-schema triage](/docs/reference/migration/3-2-to-3-3#closed-schema-triage-what-stays-in-3-3). + ### Already shipped in 3.2.2, 3.2.3, and 3.2.4 These merged on `main` during the 3.3 cycle and were also released on the 3.2 line. Their changesets appear again in the 3.3.0 changelog but are not new to 3.2.4 adopters. @@ -194,13 +213,23 @@ Three features are not part of 3.3. All three add terms to `commercial_terms`, w - **Definition pins (#7960), published in `3.3.0-beta.0` and `3.3.0-beta.1`, removed after beta.1.** `commercial_terms.definition_pins[]`, the `definition_changed` refinement reason with `drifted_pins[]`, `REFERENCE_DEFINITION_CHANGED`, the `definition_pin_probe` controller scenario, the `definition_pin_drift` storyboard, and the `definition-pins` test vectors are removed. The beta rule that sellers MUST pin covered third-party definitions no longer applies. This is a beta-to-beta change, not a change to any stable release. - **Purchase rights (#8101), published in `3.3.0-beta.1` as experimental `media_buy.purchase_rights` and removed after beta.1.** `purchases[].rights[]`, `brand/rights-scope.json` (so `brand/rights-terms.json` returns to its 3.2 form), and the `paid_amplification` and `content_reuse` values of `right-use` are removed. -- **Installment selection (#8246), published in `3.3.0-beta.1` as experimental `media_buy.installment_selection` and removed after beta.1.** `purchases[].installments[]`, `refine_proposals` `installment_changes`, and `unsatisfied_installment_changes` are removed. Installments on the canonical product and `holds[]` stay in 3.3. +- **Installment selection (#8246), published in `3.3.0-beta.1` as experimental `media_buy.installment_selection` and removed after beta.1.** `purchases[].installments[]`, `refine_proposals` `installment_changes`, and `unsatisfied_installment_changes` are removed. Installments on the canonical product and `holds[]` stay in 3.3. The request side returns in rc.0 as experimental `media_buy.installment_refinement` (#8974): the buyer asks for installments with `refine_proposals` `installment_changes`, and the seller answers with a product that declares exactly those installments, so `commercial_terms` doesn't change. Naming installments in the signed `purchases[].installments[]` stays planned for 4.0. See the [migration guide](/docs/reference/migration/3-2-to-3-3#withdrawn-from-3-3-planned-for-4-0) for what to remove, and [Planned for 4.0](/docs/reference/migration/v4-compatibility#planned-for-4-0-withdrawn-from-3-3) for the preserved designs. +### Closed-schema triage before rc.0 + +After the working group opened the schemas that were closed by accident (2026-11-09, DR-0036), the [#8501](https://github.com/adcontextprotocol/adcp/issues/8501) triage re-checked every beta feature withdrawn because its schema was closed. A feature withdrawn only for that reason stays in 3.3. A field on a deprecated task or row leaves, and so does a field that would extend `commercial_terms`, the term objects inside it, or `proposal-budget-constraint`, which are held closed until 4.0. The [migration guide](/docs/reference/migration/3-2-to-3-3#closed-schema-triage-what-stays-in-3-3) lists every field. + +- **Stays in 3.3:** `review_sla` on media-buy actions, minute dayparts and `time_granularity`, the spot-lifecycle capability fields, `collection_lists`, core gender targeting, `trackers` and `landing_page_url` on `assign` operations, `forced.proposal_id` on the test controller, and `signing_profile` on notification configs. +- **Leaves 3.3 (deprecated surface):** assignment `trackers` and `landing_page_url` on `sync_creatives` `assignments[]` and package creative assignments; `refine[].package`, the `refinement_applied[]` additions, `filters.target_audiences`, and `include_collections` on `get_products`; `predecessor_media_buy_id`, `lineage_reason`, `artifact_webhook.signing_profile`, `target_audiences`, and `start_requires_all_creatives_approved` on `create_media_buy` and `update_media_buy`. +- **Moves within 3.3:** `execution_readiness` to `list_products`, `clock` and `business_calendar_id` from `sla-window` to the creative-review SLA, and `available_installment_statuses` to the canonical reporting capabilities. +- **Planned for 4.0 (held closed until 4.0):** `metric_id` on performance standards (#8436), `price_adjustments` (#7955), `counting_mechanisms` (#7940), and `target_audiences` on purchases (#8215). +- **In review, not in rc.0:** #8854 withdraws `metric_id` and restores `evaluator` as a deprecated `x-entity` value. It has not merged, so rc.0's schemas still carry `metric_id` and still lack `evaluator`. + ### In review for 3.3 -Proposals still in review, and not part of any beta until they merge, are listed in the [3.3 beta program](/docs/reference/3-3-beta#in-review-for-3-3). +Proposals still in review, and not part of any prerelease until they merge, are listed in the [3.3 prerelease program](/docs/reference/3-3-beta#in-review-for-3-3). --- diff --git a/docs/reference/versioning.mdx b/docs/reference/versioning.mdx index 3fa28166dbb..0ebcd37f831 100644 --- a/docs/reference/versioning.mdx +++ b/docs/reference/versioning.mdx @@ -95,6 +95,8 @@ Releases before 3.3 did not have this rule, so a seller that lists no release la Pre-release tags (`"3.1-beta"`, `"3.1-rc.1"`) are matched **exactly** against `supported_versions`. They are not range-resolved: a buyer pinning `"3.1-beta"` against a server that lists `["3.0", "3.1"]` (no beta in the list) gets `VERSION_UNSUPPORTED`, not a downshift to `"3.0"`. Servers MUST NOT downshift a release pin onto a pre-release (`"3.1"` → `"3.1-beta"`); when both are advertised, the release wins exact match. +**Buyers** MUST send a pre-release `adcp_version` only to a peer whose `supported_versions` advertises that exact value. A pre-release pin never negotiates down, so sending one to any other peer gets `VERSION_UNSUPPORTED`, not a served release. Buyers SHOULD send the discovery `get_adcp_capabilities` call without a version pin, so a peer on any release can answer it. On `VERSION_UNSUPPORTED`, buyers SHOULD retry without a pin, or at a value from the error's `supported_versions` (described below), which is the recovery the `VERSION_UNSUPPORTED` error code names. A buyer that pins discovery to `"3.3-beta.5"` against a seller that speaks only 3.0, and stops at the error, never learns that the two could talk at 3.0. + #### `VERSION_UNSUPPORTED` error data When the seller can't honor a pin, `error.data` follows [`error-details/version-unsupported.json`](https://github.com/adcontextprotocol/adcp/blob/main/static/schemas/source/error-details/version-unsupported.json): diff --git a/docs/reference/versions.mdx b/docs/reference/versions.mdx index 6235f4fd6c3..282da997974 100644 --- a/docs/reference/versions.mdx +++ b/docs/reference/versions.mdx @@ -13,7 +13,7 @@ description: "Every published AdCP version, its status, and its end-of-life date | Status | Versions | Wire pin | What it means | |---|---|---|---| -| **Pending beta** | 3.3 (`beta.0` protocol-first; beta.1 converges protocol and SDKs) | Exact prerelease after publication, such as `"3.3-beta.0"` | Development and staging only. Follow the [3.3 beta program](/docs/reference/3-3-beta). | +| **Release candidate** | 3.3 (current prerelease: `rc.0`) | `"3.3-rc.0"` | Development and staging only. The first release candidate, after seven betas; no published SDK bundles it yet. Follow the [3.3 prerelease program](/docs/reference/3-3-beta). | | **Active** | 3.2 (current stable: 3.2.1) | `"3.2"` | Current production minor release, published 2026-09-30. `3.2.0` was never released. TypeScript `@adcp/sdk@14.0.0` and Python `adcp==8.0.0` ship alongside it and embed it. See [What's new in AdCP 3.2](/docs/reference/whats-new-in-3-2) and the [3.1 to 3.2 migration guide](/docs/reference/migration/3-1-to-3-2). | | **Maintained** | 3.1 (current stable: 3.1.24) | `"3.1"` | Supported previous minor. Receives security and critical fixes on the `3.1.x` line for a maintainer-decided window. See [What's New in AdCP 3.1](/docs/reference/whats-new-in-3-1). | | **Maintained** | 3.0 (current stable: 3.0.26) | `"3.0"` | Supported previous minor for existing production integrations. Receives compatibility and security patches. | @@ -24,12 +24,6 @@ description: "Every published AdCP version, its status, and its end-of-life date *Status legend: Pending beta = announced but not yet published. Beta and release candidate = immutable prerelease checkpoints for development and staging. A one-time cleanup on 2026-09-14 retired some historical 3.x beta bundles from the repository and runtime image; remaining and future published prerelease artifacts stay immutable, and retired beta URLs are served from the artifact CDN on a best-effort basis only. Active = current stable generation. Maintained = supported previous minor. Security-only = patches for security issues only, no features. End of life = no patches. Planned = not yet released.* -## Pending prerelease - -| Version | Status | Notes | -|---|---|---| -| 3.3.0-beta.0 | Pending first cut | Protocol-first beta input for SDK work. Do not use the artifact or the `"3.3-beta.0"` wire pin until the GitHub prerelease and signed bundle are published. Move this row into the published prerelease table with its release date in the beta.0 Version Packages PR. | - ## All published versions ### 3.x — current generation @@ -57,6 +51,11 @@ Supported patches don't change stable wire surfaces. Upgrading among supported 3 | Version | Released | Notes | |---|---|---| +| **3.3.0-rc.0** | 2026-11-16 | **Current 3.3 prerelease**, the first release candidate. Carries beta.6, plus the prerelease pins, unpinned discovery, and anonymous capabilities guidance, declared `sync_creatives` assignment operations (#8997), audience targeting without member push (#8996), carousel card `cta_values` (#9001), inline `submitted` branches aligned with their status files (#8934), the `by_package` guidance (#8970), scope and `signing_keys` rules for several matching `authorized_agents` entries (#9011, #9017), three renamed experimental values (#8989), an omitted `human_review_required` accepted by campaign governance (#9007), compliance gates for `audience_buy_flow` and `inline_creatives_without_sync` (#9013, #9005), the public test agent's `3.3-beta.6` preview (#9018), and the Instagram, Facebook, Snapchat and X distribution identifier types (#8995). No published SDK bundles it yet. See the [3.3 prerelease program](/docs/reference/3-3-beta). | +| 3.3.0-beta.6 | 2026-11-13 | Superseded. Opens the schemas that were closed by accident (DR-0036) and applies the closed-schema triage, which removes or moves the beta fields on deprecated tasks and on the commercial terms held closed until 4.0. `@adcp/sdk` 17.0.0-beta.24 and later and Python `adcp` 10.0.0b17 and later embed it. | +| 3.3.0-beta.5 | 2026-11-07 | Superseded. Experimental match keys, `sales-fixed-rate` promoted to stable, and the bundled Public Suffix List. `@adcp/sdk` 17.0.0-beta.21 through 17.0.0-beta.23 and Python `adcp` 10.0.0b13 through 10.0.0b16 embed it. | +| 3.3.0-beta.4 | 2026-11-05 | Superseded. Reporting-subscription coverage fixes, assignment `replace` settings transfer, and the hold, account-request, and reporting-subscription storyboards. `@adcp/sdk` 17.0.0-beta.18 through 17.0.0-beta.20 and Python `adcp` 10.0.0b12 embed it. | +| 3.3.0-beta.0 through beta.3 | 2026-10-22 to 2026-10-31 | Superseded. Beta.0 was the protocol-first input for SDK work; beta.1 to beta.3 added the account identity model, principal-level reporting subscriptions, live creative updates, and the protocol envelope on every response, and beta.2 withdrew definition pins, purchase rights, and installment selection. | | 3.2.0-rc.7 | 2026-09-27 | Final release candidate, superseded by 3.2.1. Published as [`v3.2.0-rc.7`](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.7). Adds the `viewable_rate` metric optimization goal with a required viewability `standard` and optional measurement `vendor`, lets `viewed_seconds` goals name a standard and vendor, and declares the deprecated `account` field on the media-buy `list_creative_formats` request. TypeScript `@adcp/sdk@14.0.0-rc.50` and Python `adcp==8.0.0b18` embed it exactly. Move `"3.2-rc.7"` pins to `"3.2"`. | | 3.2.0-rc.6 | 2026-09-23 | Superseded. Published as [`v3.2.0-rc.6`](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.6). Carries the RC.5 changes (shared MediaBuy `name` on `buy_products` and `accept_proposal`, seller-policy decline reasons, the request-signing error vocabulary, and the streaming-TV, retail-media, and exchange sales specialisms) plus the Reliable Reporting waiver reconciliation. TypeScript SDK RC.48 embeds it exactly. | | 3.2.0-rc.5 | — | Not published. The release process withheld this bundle, and RC.6 superseded it. | @@ -116,8 +115,8 @@ Targeted for early 2027. 3.x is mid-cycle — see the [planned releases table](/ | If you are… | Use | |---|---| | Building a new production integration today | **3.2**. Pin `"3.2"` on the wire with `@adcp/sdk@14.0.0` or `adcp==8.0.0`, and fall back to `"3.1"` for peers that don't advertise 3.2. | -| Implementing or testing 3.3 before SDK support | After publication, use **3.3 beta.0** artifacts with raw-wire or code-generation workflows. Follow the [3.3 beta program](/docs/reference/3-3-beta). | -| Running an SDK-backed 3.3 integration test | Use only the exact beta named by the SDK support matrix. Beta.1 is SDK-backed only after its post-publication SDK refresh completes. | +| Implementing or testing 3.3 before SDK support | Use the signed **3.3 rc.0** artifacts with raw-wire or code-generation workflows, and the exact pin `"3.3-rc.0"`. Follow the [3.3 prerelease program](/docs/reference/3-3-beta). | +| Running an SDK-backed 3.3 integration test | Use only the exact prerelease named by the [SDK support matrix](/docs/building/by-layer/L4/choose-your-sdk). Until an SDK bundles rc.0, that is beta.5 with `@adcp/sdk` 17.0.0-beta.22 or Python `adcp` 10.0.0b15. | | Implementing 3.2 without an SDK | Generate from the signed [`3.2.1` tarball](https://adcontextprotocol.org/protocol/3.2.1.tgz). See [Verifying protocol tarballs](/docs/reference/verifying-protocol-tarballs). | | Pinned to a 3.2 beta or release candidate | Move to `"3.2"`. See the [3.2 prerelease history](/docs/reference/3-2-beta) for what changed after RC.7. | | Running an existing 3.0 integration | Stay on **3.0** while you migrate, or move to **3.2** (or 3.1) when your SDK and validation are ready. | @@ -132,8 +131,8 @@ Targeted for early 2027. 3.x is mid-cycle — see the [planned releases table](/ - **[v2 Sunset](/docs/reference/v2-sunset)** — full v2 end-of-life timeline and migration paths - **[What's new in v3](/docs/reference/whats-new-in-v3)** — feature-by-feature summary of what 3.0 adds - **[What's New in AdCP 3.1](/docs/reference/whats-new-in-3-1)** — final 3.1 feature set and adopter actions -- **[What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3)** — 3.3 beta feature set and adopter actions -- **[3.3 beta program](/docs/reference/3-3-beta)** — beta.0 artifacts, SDK handoff, and beta.1 gates +- **[What's new in AdCP 3.3](/docs/reference/whats-new-in-3-3)** — 3.3 release-candidate feature set and adopter actions +- **[3.3 prerelease program](/docs/reference/3-3-beta)** — checkpoints, SDK pairings, the closed-schema triage, and proposals still in review - **[What's new in AdCP 3.2](/docs/reference/whats-new-in-3-2)** — 3.2 feature set and adopter actions - **[3.2 prerelease history](/docs/reference/3-2-beta)** — beta and RC checkpoints, SDK pairings, and changes after RC.7 - **[Release Notes](/docs/reference/release-notes)** — curated narrative for each version diff --git a/docs/reference/whats-new-in-3-3.mdx b/docs/reference/whats-new-in-3-3.mdx index 0ae9ab05396..bb17355dca5 100644 --- a/docs/reference/whats-new-in-3-3.mdx +++ b/docs/reference/whats-new-in-3-3.mdx @@ -1,23 +1,56 @@ --- title: What's new in AdCP 3.3 sidebarTitle: What's new in 3.3 -description: "Adopter overview of the AdCP 3.3 beta: scheduled, human-gated, and offline media in the same buy as programmatic, honest delivery data for linear TV, print, and DOOH, and the places 3.2 implementations could still disagree, now closed." +description: "Adopter overview of the AdCP 3.3 release candidate: scheduled, human-gated, and offline media in the same buy as programmatic, honest delivery data for linear TV, print, and DOOH, schemas open by default, and the places 3.2 implementations could still disagree, now closed." "og:title": "AdCP — What's New in 3.3" --- # What's new in AdCP 3.3 -**3.3 is in its beta cycle.** The latest checkpoint is `3.3.0-beta.5`, published 2026-11-07. Beta.0 publishes the protocol artifacts before SDK support, and beta.1 through beta.5 incorporate integration feedback; a beta is SDK-backed only after SDK support for its exact bundle is published. Use the beta in development and staging, and read the [3.3 beta program](/docs/reference/3-3-beta) before testing. This page lists only what has merged; it is refreshed at each beta cut. +**3.3 is at its first release candidate.** The latest checkpoint is `3.3.0-rc.0`, published 2026-11-16, after seven betas. A prerelease is SDK-backed only after SDK support for its exact bundle is published. Use the release candidate in development and staging, and read the [3.3 prerelease program](/docs/reference/3-3-beta) before testing. This page lists only what has merged; it is refreshed at each prerelease cut. -**Three features that shipped in the betas are withdrawn after beta.1: definition pins (beta.0 and beta.1), purchase rights, and installment selection (both beta.1).** All three wait for 4.0, because `commercial-terms` stays closed within 3.x ([details](#withdrawn-from-3-3-planned-for-4-0)). +**Three features that shipped in the betas are withdrawn after beta.1: definition pins (beta.0 and beta.1), purchase rights, and installment selection (both beta.1).** All three wait for 4.0, because `commercial-terms` stays closed within 3.x ([details](#withdrawn-from-3-3-planned-for-4-0)). **The closed-schema triage removes further beta fields at rc.0**, mostly 3.3 additions to deprecated tasks ([details](#new-in-rc-0)). AdCP 3.3 lets scheduled, human-gated, and offline media run through the same buy as programmatic. A booking can say when it will be confirmed. A proposal request can target a vendor-measured outcome, and a governance plan can budget by period. Products, audiences, and delivery reports can carry what a linear-TV, print, or DOOH seller actually knows: spot lifecycle and makegoods, break position, print proof of insertion and circulation, structured DOOH location, property-grain rollups, and audience sizes as honest ranges. Minute-level dayparts, broadcast mezzanine formats, and the NMO and VideoAmp demographic systems fill in the TV edges. Around that, 3.3 tightens the places where two conformant 3.2 implementations could still disagree: discovery never provisions an account, one agent-resolution rule covers every signing surface, `required_for` is enforced over A2A with its hardening clauses required, and `reporting_webhook.operation_id` correlation fails closed. Catalog intake becomes an optional declaration, verifiers can advertise A2A `required_for` enforcement through `request_signing.operation_sources`, and `ext.adcp` becomes a reserved namespace. New single-adopter surfaces ship as experimental, so 3.4 can reshape them without breaking stable integrations. -No stable field, enum value, or task is removed. Two result fields, one usage, the principal kind field, the account identity-rekey machinery, and the RFC 9421 signing profiles are deprecated, all functional throughout 3.x. They are `seller_id` on event source and audience results (use `platform_id`), and the natural key as the account reference after provisioning. They also include `account.identity_updates`, `operator_identity`, `ACCOUNT_MOVED`, `ACCOUNT_IDENTITY_CONFLICT`, and `account.stable_account_id` (use `account_id`), `principal_kind` and `expected_principal_kind` (a bound principal is always `buyer_agent`), and the RFC 9421 profiles (use the experimental Web Bot Auth profile). 3.3 adds optional fields, enum values, and capability declarations. Schema-valid 3.2 messages stay schema-valid except for the new domain identifier format, and unless they already used a name 3.3 now defines with a different shape; the list is in the [migration guide](/docs/reference/migration/3-2-to-3-3#what-can-fail-validation). The normative narrowings are recorded in [Versioning and governance](/docs/reference/versioning#3-3-exceptions-to-3-x-compatibility-beta) and lead the [migration guide](/docs/reference/migration/3-2-to-3-3#required-to-claim-3-3-behavior). +No stable field, enum value, or task is removed. Two result fields, one usage, the principal kind field, the account identity-rekey machinery, the boolean form of `demographics`, and the RFC 9421 signing profiles are deprecated. All remain functional throughout 3.x and are expected to be removed in 4.0. They are `seller_id` on event source and audience results (use `platform_id`), and the natural key as the account reference after provisioning. They also include `account.identity_updates`, `operator_identity`, `ACCOUNT_MOVED`, `ACCOUNT_IDENTITY_CONFLICT`, and `account.stable_account_id` (use `account_id`), `principal_kind` and `expected_principal_kind` (a bound principal is always `buyer_agent`), `demographics: true` (send `{ "age": true }`), and the RFC 9421 profiles (use the experimental Web Bot Auth profile). 3.3 adds optional fields, enum values, and capability declarations. Schema-valid 3.2 messages stay schema-valid except for the new domain identifier format, and unless they already used a name 3.3 now defines with a different shape; the list is in the [migration guide](/docs/reference/migration/3-2-to-3-3#what-can-fail-validation). The normative narrowings are recorded in [Versioning and governance](/docs/reference/versioning#3-3-exceptions-to-3-x-compatibility-beta) and lead the [migration guide](/docs/reference/migration/3-2-to-3-3#required-to-claim-3-3-behavior). + +## New in rc.0 + +rc.0 (2026-11-16) is the first release candidate. Its main changes since beta.5 open the schemas that were closed by accident and settle which beta features stay in 3.3. Most of it first shipped in `3.3.0-beta.6` (2026-11-13), cut for SDK testing ahead of rc.0. New in rc.0 itself: the guidance on prerelease pins, unpinned discovery, and anonymous capabilities; the [declared assignment operations](#sellers-declare-the-assignment-operations-they-accept) ([#8997](https://github.com/adcontextprotocol/adcp/pull/8997)); audience targeting without member push ([#8996](https://github.com/adcontextprotocol/adcp/pull/8996)); [carousel card CTA values](#carousel-card-cta-values) ([#9001](https://github.com/adcontextprotocol/adcp/pull/9001)); the `by_package` guidance ([#8970](https://github.com/adcontextprotocol/adcp/pull/8970)); the scope and `signing_keys` rules for several matching `authorized_agents` entries ([#9011](https://github.com/adcontextprotocol/adcp/pull/9011), [#9017](https://github.com/adcontextprotocol/adcp/pull/9017)); three renamed experimental values ([#8989](https://github.com/adcontextprotocol/adcp/pull/8989)); an omitted `human_review_required` in campaign governance ([#9007](https://github.com/adcontextprotocol/adcp/pull/9007)); inline `submitted` branches that match their published status files ([#8934](https://github.com/adcontextprotocol/adcp/pull/8934)); compliance gates for `audience_buy_flow` and `inline_creatives_without_sync` ([#9013](https://github.com/adcontextprotocol/adcp/pull/9013), [#9005](https://github.com/adcontextprotocol/adcp/pull/9005)); the public test agent's `3.3-beta.6` preview ([#9018](https://github.com/adcontextprotocol/adcp/pull/9018)); and the Instagram, Facebook, Snapchat and X distribution identifier types ([#8995](https://github.com/adcontextprotocol/adcp/pull/8995)). +**Schemas are open by default ([#8866](https://github.com/adcontextprotocol/adcp/pull/8866), [DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md), decided 2026-11-09).** Closing a schema only breaks validators that hard-code it, so 3.x opens the schemas that were meant to be open: 744 of the 859 closed locations in the 3.3 schemas. 115 stay closed. Most have a structural reason, such as unions told apart by key presence, join keys, privacy clamps, and `trust.json`. The nodes inside `commercial_terms`, with `proposal-budget-constraint`, are held closed until 4.0. +- Every payload that was valid stays valid. Where closure also rejected a specific field, the opened schema rejects it by name. +- Generated types change. TypeScript types gain index signatures, Pydantic models stop forbidding extra fields, and Zod validators accept unknown keys where the schema opened. +- A strict validator built from 3.2.10 or earlier still rejects 3.3 fields, so send them only to 3.3 peers. 3.2.11 ([#8864](https://github.com/adcontextprotocol/adcp/pull/8864)) opens the same locations in 3.2. +- A minor adds to open schemas and adds nothing to a schema that stays closed. See [Schemas are open by default](/docs/reference/migration/3-2-to-3-3#schemas-are-open-by-default). + +**What stays and what leaves ([#8501](https://github.com/adcontextprotocol/adcp/issues/8501)).** Features withdrawn from the betas only because their schema was closed stay in 3.3. They include `review_sla` on media-buy actions, `signing_profile` on notification configs, and `trackers` and `landing_page_url` on `assign` operations. +- **Deprecated tasks.** Fields the betas added to deprecated tasks and rows leave: `refine[].package`, `include_collections`, and `filters.target_audiences` on `get_products`; lineage, the creative start gate, and `target_audiences` on `create_media_buy` and `update_media_buy`; and assignment `trackers` and `landing_page_url` on `sync_creatives` `assignments[]`. The live tasks keep those features where they already carry them, and `execution_readiness` moves to `list_products`. +- **Commercial terms.** Fields that would extend the commercial terms, which are held closed until 4.0, wait for 4.0: `metric_id` on performance standards, `price_adjustments`, `counting_mechanisms`, and `target_audiences` on purchases. The last three are out of rc.0. The `metric_id` withdrawal ([#8854](https://github.com/adcontextprotocol/adcp/pull/8854)) is in review, so rc.0's schemas still carry it. +- The [migration guide](/docs/reference/migration/3-2-to-3-3#closed-schema-triage-what-stays-in-3-3) lists every field and what to do if you built from a beta. + +**The boolean form of `demographics` is deprecated ([#8866](https://github.com/adcontextprotocol/adcp/pull/8866), from [#8772](https://github.com/adcontextprotocol/adcp/pull/8772)).** In product `overlay_support` and in `required_overlay_support`, `demographics: true` is the 3.2 shorthand for `{ "age": true }`. Senders MUST send the object form. Receivers MUST accept `true` and read it as `{ "age": true }`, so it satisfies an age requirement and never a `gender` requirement. It is planned for removal in 4.0 ([#8778](https://github.com/adcontextprotocol/adcp/issues/8778)). + +**The rules for what changes between releases ([#8704](https://github.com/adcontextprotocol/adcp/pull/8704)).** The [versioning page](/docs/reference/versioning) now opens with them. A minor only adds. A replaced field is emitted alongside its replacement until the next major. Removals and breaking changes happen in a major. A fourth rule keeps a field off a mutating request in a minor when an older seller that ignored it would commit to something different, unless the field ships behind a capability the seller declares. Wire behavior is unchanged. + +**Version negotiation and anonymous discovery.** A buyer MUST send a prerelease `adcp_version` only to a peer that advertises that exact value, SHOULD send the discovery `get_adcp_capabilities` call without a pin, and SHOULD retry without a pin or at a listed version on `VERSION_UNSUPPORTED`. A seller SHOULD serve `get_adcp_capabilities` without credentials, which becomes a MUST in 4.0. On MCP, a gateway that allow-lists methods SHOULD let `server/discover`, `initialize`, and `tools/list` through without credentials. See the [migration guide](/docs/reference/migration/3-2-to-3-3#prerelease-pins-unpinned-discovery-and-anonymous-capabilities). + +**Also in rc.0.** + +- **Installments (experimental).** A buyer can ask for specific installments of a product through `refine_proposals` `installment_changes` (`media_buy.installment_refinement`, [#8974](https://github.com/adcontextprotocol/adcp/pull/8974)), and the seller answers with a product that declares exactly those installments, so nothing new goes into `commercial_terms` and binding the slots themselves stays a 4.0 item ([Choose installments](/docs/media-buy/task-reference/refine_proposals#choose-installments-experimental)). `installment_refs` on a `sync_creatives` `assign` or `replace` operation limits the assignment to those installments of the package, with readback on `get_media_buys` and `list_creatives` (`media_buy.installment_creative_assignment`, [#8972](https://github.com/adcontextprotocol/adcp/pull/8972)); see [Assigning to specific installments](/docs/creative/task-reference/sync_creatives#assigning-to-specific-installments-experimental). +- **Three experimental values renamed ([#8989](https://github.com/adcontextprotocol/adcp/pull/8989)).** `input_required` → `input-required` (`media_buy.execution_readiness`), `click_through` → `clickthrough` (`creative.live_updates`), and `underdelivery` → `under_delivery` (`media_buy.delivery_projection`), each the spelling its stable or sibling counterpart already uses. There is no alias, so an implementation built from a beta bundle changes to the new spelling. See [Three experimental values renamed](/docs/reference/migration/3-2-to-3-3#three-experimental-values-renamed). +- **Origin-only agent URLs ([#8939](https://github.com/adcontextprotocol/adcp/pull/8939)).** An origin-only `authorized_agents[].url` in `adagents.json` authorizes the agent at that origin, whatever its path. An entry with a path still matches only that URL. When several entries match one agent, its scope is the union of theirs, and a `signing_keys` pin holds only if every entry that matches and authorizes the message pins keys ([#9011](https://github.com/adcontextprotocol/adcp/pull/9011), [#9017](https://github.com/adcontextprotocol/adcp/pull/9017)). +- **Declared-option conformance ([#8941](https://github.com/adcontextprotocol/adcp/pull/8941)).** A seller accepts a creative that conforms to the format option it targets, and enforces only the limits it declared. See [Format conformance](/docs/creative/task-reference/sync_creatives#format-conformance). +- **Signed terms bind every member ([#8884](https://github.com/adcontextprotocol/adcp/pull/8884)).** Accepting signed commercial terms binds a party to every member `terms_digest` covers, including members it does not recognize, so a party that cannot interpret one declines (`unrecognized_terms`) or rejects (`UNRECOGNIZED_TERMS`) instead of accepting. See [Verify terms independently](/docs/media-buy/product-discovery/proposal-negotiation#3-verify-terms-independently). +- **Reporting without buyer secrets ([#8793](https://github.com/adcontextprotocol/adcp/pull/8793), experimental).** Reliable Reporting managed delivery authenticates as the seller for every pattern, and a seller never holds a caller-issued secret such as an API key, bearer token, or signed URL. Rows pushed in an HTTP body use `reporting_webhook`. A new `https_put` `file_transfer` transport writes immutable objects and a manifest to a buyer HTTPS endpoint, with every request signed under the Web Bot Auth profile and a signed probe before `ready`. +- **Per-package report rows ([#8983](https://github.com/adcontextprotocol/adcp/pull/8983), experimental).** Reliable Reporting report definitions gain `contract_version` `1.2`: a `1.2` definition whose `dimensions` include `media_buy_id` MUST include `package_id`, so a buyer that bills, caps, or reconciles per package can split a buy-level revision without guessing. `1.0` and `1.1` are unchanged, and a seller MUST serve callers pinned below 3.3 `1.0` or `1.1` offerings. See [Configuration and capabilities](/docs/media-buy/task-reference/get_reporting_status#configuration-and-capabilities). +- **TMP cache isolation ([#7446](https://github.com/adcontextprotocol/adcp/pull/7446), experimental).** Context Match caches partition by trusted evaluation namespace, and warm hits re-authorize. See [the migration](/docs/reference/migration/trusted-match-context-cache). +- **Smaller additions.** The optional `creative.supports_registry_policy_enforcement` capability gates the policy-backed rejection storyboard ([#8857](https://github.com/adcontextprotocol/adcp/pull/8857)). Video asset requirements accept `3gp`, `mpeg`, and `m4v` containers ([#8668](https://github.com/adcontextprotocol/adcp/pull/8668)). `image_carousel` gains optional `card_image_sizes` ([#8937](https://github.com/adcontextprotocol/adcp/pull/8937), [below](#carousel-card-image-size)). Seventeen attestation and reporting URL patterns check only the `https` scheme ([#8792](https://github.com/adcontextprotocol/adcp/pull/8792)). `media_buy.supported_delivery_types` lets a seller declare `guaranteed`, `non_guaranteed`, or both ([below](#optional-declarations), [#8458](https://github.com/adcontextprotocol/adcp/pull/8458)). Targeting can carry display names beside its geographic codes, `geo_value_labels` for ISO codes and `value_labels` on metro and place entries, so a package or audit log shows "New York" next to `501`; sellers never target from them ([#8966](https://github.com/adcontextprotocol/adcp/pull/8966), [Geographic Restrictions](/docs/media-buy/advanced-topics/targeting#geographic-restrictions)). `distribution-identifier-type` adds Instagram, Facebook, Snapchat and X, so a creator's social channels can be listed in `collection.distribution[].identifiers` instead of `platform_channel_id`: `instagram_account_id`, `facebook_page_id`, `snapchat_profile_id` and `x_user_id` are the canonical identifiers, and `instagram_handle`, `facebook_page_handle`, `snapchat_handle` and `x_handle` are discovery aliases that registries compare as `@` plus the lowercased name, like `youtube_channel_handle` ([#8995](https://github.com/adcontextprotocol/adcp/pull/8995)). `get_media_buy_delivery` sellers SHOULD return at least one `by_package` row per media buy, one per package, and SHOULD omit a buy they can't report and return an error rather than an empty `by_package`. `by_package: []` stays valid in 3.x, and requiring a row is proposed for 4.0 ([#8970](https://github.com/adcontextprotocol/adcp/pull/8970), [#8973](https://github.com/adcontextprotocol/adcp/issues/8973)). Experimental campaign governance accepts a `sync_plans` plan that omits `human_review_required`, deriving it from the plan's policies, and states two validation rules for flight order and policy-ID uniqueness ([#9007](https://github.com/adcontextprotocol/adcp/pull/9007)). +**Conformance.** The dependency-impairment storyboards skip their image-creative phases for sellers whose format option is not an image format ([#8841](https://github.com/adcontextprotocol/adcp/pull/8841)). The signal-targeting storyboards run only for sellers that support wholesale discovery for both media buys and signals ([#8838](https://github.com/adcontextprotocol/adcp/pull/8838)). Legacy inline creative manifests are built from the captured format's exact required slots ([#8798](https://github.com/adcontextprotocol/adcp/pull/8798)). ## New in beta.5 @@ -91,17 +124,17 @@ These shipped before beta.3 and are summarized here with the rest. Everything ma - **Capabilities are bounded by structure ([#8505](https://github.com/adcontextprotocol/adcp/pull/8505), [#8526](https://github.com/adcontextprotocol/adcp/pull/8526)).** Every array, string, and keyed map in `get_adcp_capabilities` has a limit, enforced on new and experimental fields and annotated for 4.0 on fields that were stable before 3.3. Those bounds are the protocol's limit, and agents MUST NOT design to a byte figure. `MAX_CAPABILITIES_BYTES` (64 KiB) is a receiver backstop and deployment guidance, not a protocol rule on senders. - **Undisclosed rosters ([#7948](https://github.com/adcontextprotocol/adcp/pull/7948), beta.1).** A product's `publisher_properties` or `collections` can be `[]`, which means the seller does not disclose the roster. There is no new field and no partial state. Allow lists may be accepted against it and cover only what the seller matches. Exclusion lists are the buyer's choice, because the buyer sees the undisclosed roster at discovery: a seller that accepts one applies it to its full internal roster, and a seller that cannot rejects it with `UNSUPPORTED_FEATURE`. A seller serving a release below 3.3 never returns such a product. Buyers treat the roster as opaque and may refuse the product. See [Roster coverage](/docs/media-buy/product-discovery/media-products#roster-coverage). - **Canceled and completed buys keep their packages ([#8467](https://github.com/adcontextprotocol/adcp/pull/8467), beta.1).** From 3.3 a seller retains packages on terminal buys, with stable identities, platform mappings, and the latest committed configuration, and discloses irrecoverable history through nonfatal errors instead of returning an incomplete list. -- **Mixed creative approval states at startup ([#8485](https://github.com/adcontextprotocol/adcp/pull/8485), beta.1).** A seller keeps pending-review and rejected assignments and starts the approved ones by default. The optional package `start_requires_all_creatives_approved` gate holds the start until every assignment is approved, and `media_buy.features.creative_start_policy` declares support. +- **Mixed creative approval states at startup ([#8485](https://github.com/adcontextprotocol/adcp/pull/8485), beta.1).** A seller keeps pending-review and rejected assignments and starts the approved ones by default. The optional `start_requires_all_creatives_approved` gate on `control_media_buy` package controls holds the start until every assignment is approved, and `media_buy.features.creative_start_policy` declares support. The gate's copies on `create_media_buy` and `update_media_buy` packages are withdrawn at rc.0. - **Review and escalation commitments ([#8417](https://github.com/adcontextprotocol/adcp/pull/8417), beta.1).** Products can declare creative-review timing in elapsed time or in business time on a seller calendar. Every other SLA stays elapsed time, as in 3.2. `report_media_buy_issue` and `get_media_buy_issue` give a human acknowledgement and resolution status for a critical report. - **Seller offers (experimental, `media_buy.seller_offers`, [#8102](https://github.com/adcontextprotocol/adcp/pull/8102), beta.2).** A seller can propose a change to an accepted buy: a postponed or canceled installment, a preemption, under-delivery. The offer is a `committed` canonical proposal with `proposal_initiator: "seller"` and an `offer_reason`, read through `list_proposals` and announced by the identifiers-only `proposal.offered` notification. The buyer accepts, declines, or revises it with the existing tasks. At `expires_at` the signed terms stand, and silence is never acceptance. Sellers never send offers to callers below 3.3. See [Seller offers](/docs/media-buy/product-discovery/proposal-negotiation#seller-offers). -- **Price adjustments (experimental, `media_buy.price_adjustments`, [#7955](https://github.com/adcontextprotocol/adcp/pull/7955), beta.1).** A fixed-price pricing option can publish an ordered table of fee and discount rows keyed by format option, placement selection, or always, so a buyer computes the price of what it selects. The table is optional, and its resolution order and rounding are normative. See [Selection-dependent price adjustments](/docs/media-buy/advanced-topics/pricing-models#selection-dependent-price-adjustments). -- **Execution readiness (experimental, `media_buy.execution_readiness`, [#7934](https://github.com/adcontextprotocol/adcp/pull/7934), beta.1).** A `get_products` request with `account` can set `include_execution_readiness: true` to learn, per product and per `execution_requirements` entry, whether the account is `ready`, `setup_required`, `selection_required`, `input-required`, or `unknown`, with candidates whose `resource_id` fits the existing binding field. See [Per-account execution readiness](/docs/media-buy/specification#per-account-execution-readiness-experimental). +- **Price adjustments (experimental, `media_buy.price_adjustments`, [#7955](https://github.com/adcontextprotocol/adcp/pull/7955), beta.1).** A fixed-price pricing option can publish an ordered table of fee and discount rows keyed by format option, placement selection, or always, so a buyer computes the price of what it selects. The table is optional, and its resolution order and rounding are normative. **Withdrawn at rc.0** and planned for 4.0 ([New in rc.0](#new-in-rc-0)); see [Selection-dependent price adjustments (withdrawn)](/docs/media-buy/advanced-topics/pricing-models#selection-dependent-price-adjustments-withdrawn). +- **Execution readiness (experimental, `media_buy.execution_readiness`, [#7934](https://github.com/adcontextprotocol/adcp/pull/7934), beta.1).** A `list_products` request with `account` (a `get_products` request in the betas) can set `include_execution_readiness: true` to learn, per product and per `execution_requirements` entry, whether the account is `ready`, `setup_required`, `selection_required`, `input-required`, or `unknown`, with candidates whose `resource_id` fits the existing binding field. See [Per-account execution readiness](/docs/media-buy/specification#per-account-execution-readiness-experimental). - **Signals (experimental).** Signal pricing groups (`signals.pricing_groups`, [#8058](https://github.com/adcontextprotocol/adcp/pull/8058)) let a seller price alternative age bands, for example, as one audience: `pricing_group` on a listing and `signal_pricing_group_rules[]` choose `highest` or `each`. See [Signal pricing groups](/docs/media-buy/advanced-topics/targeting#signal-pricing-groups). Provider-initiated delivery (`signals.delivery_methods`, [#8044](https://github.com/adcontextprotocol/adcp/pull/8044)) lets a signal agent declare the methods it can send over, a buyer pin one with `delivery_method`, and agent deployments report `delivery_status`. See [Declaring delivery methods](/docs/signals/tasks/activate_signal#declaring-delivery-methods). - **Gender targeting (experimental, `media_buy.gender_targeting`, [#7925](https://github.com/adcontextprotocol/adcp/pull/7925), beta.1).** Core `demographics.gender` targeting with female, male, and non_binary values, an independent unknown group, product-scoped capabilities, and exact readback for gender-only and mixed age and gender targeting. 3.3 reports demographic delivery by age only, so a gender-targeted package has no gendered delivery readback. Buyers never send core gender fields on a 3.2 contract. See [Core gender targeting](/docs/media-buy/advanced-topics/targeting#core-gender-targeting-3-3). -- **Measurement provenance (experimental, `media_buy.measurement_provenance`, [#7940](https://github.com/adcontextprotocol/adcp/pull/7940), beta.2).** A shared `collection-mechanism` vocabulary (`set_top_box`, `acr`, `panel`, `server_logs`, `client_tracker`, `sdk`) says what a count is built from: `billing_measurement.counting_mechanisms[]` on `measurement_terms`, and `vendor_metric_provenance[]` on delivery metrics. Sellers serving an older pin omit both. -- **Audience evidence targets (experimental, `media_buy.audience_evidence_targets`, [#8215](https://github.com/adcontextprotocol/adcp/pull/8215), beta.1).** `target_audiences[]` names the audience a buyer wants evidence for, beside `audience_evidence_requirements`. A product satisfies a target only through an admissible evidence item for exactly that audience. A target never targets delivery. See [Target audiences](/docs/media-buy/task-reference/get_products#target-audiences-experimental). +- **Measurement provenance (experimental, `media_buy.measurement_provenance`, [#7940](https://github.com/adcontextprotocol/adcp/pull/7940), beta.2).** A shared `collection-mechanism` vocabulary (`set_top_box`, `acr`, `panel`, `server_logs`, `client_tracker`, `sdk`) says what a count is built from: `vendor_metric_provenance[]` on delivery metrics. `billing_measurement.counting_mechanisms[]` on `measurement_terms` is withdrawn at rc.0 and planned for the canonical terms in 4.0. Sellers serving an older pin omit `vendor_metric_provenance[]`. +- **Audience evidence targets (experimental, `media_buy.audience_evidence_targets`, [#8215](https://github.com/adcontextprotocol/adcp/pull/8215), beta.1).** `target_audiences[]` names the audience a buyer wants evidence for, beside `audience_evidence_requirements`. A product satisfies a target only through an admissible evidence item for exactly that audience. A target never targets delivery. **Withdrawn at rc.0**: no 3.3 wire form remains, and sellers stop listing the feature id; purchases gain the field in 4.0. See [Target audiences (withdrawn)](/docs/media-buy/task-reference/get_products#target-audiences-withdrawn). - **Invoice lines (experimental, `account.invoice_lines`, [#8207](https://github.com/adcontextprotocol/adcp/pull/8207), beta.1).** `get_account_financials` invoices can carry `lines[]` that tie an amount to media buys, packages, and reporting revisions, plus `invoice_kind` (`credit_note` carries a non-negative `amount`) and `adjusts_invoice_id`. Lines are reference only and never settle an invoice. See [Invoice lines](/docs/accounts/tasks/get_account_financials#invoice-lines-experimental). -- **Smaller additions.** Exact pre-booking availability checks through structured package inputs on product-scoped `get_products` refinement ([#8468](https://github.com/adcontextprotocol/adcp/pull/8468)); an optional display `name` on measurement catalog metrics ([#8437](https://github.com/adcontextprotocol/adcp/pull/8437)); an optional `metric_id` on performance standards ([#8436](https://github.com/adcontextprotocol/adcp/pull/8436)); one delegation-chain rule for demand-side grants ([#8473](https://github.com/adcontextprotocol/adcp/pull/8473)). +- **Smaller additions.** Exact pre-booking availability checks through structured package inputs on product-scoped `get_products` refinement ([#8468](https://github.com/adcontextprotocol/adcp/pull/8468), withdrawn at rc.0); an optional display `name` on measurement catalog metrics ([#8437](https://github.com/adcontextprotocol/adcp/pull/8437)); an optional `metric_id` on performance standards ([#8436](https://github.com/adcontextprotocol/adcp/pull/8436)); one delegation-chain rule for demand-side grants ([#8473](https://github.com/adcontextprotocol/adcp/pull/8473)). **Version negotiation and closed schemas.** A request that carries only `adcp_major_version` is served the oldest release the seller supports in that major, 3.0 where it is supported ([DR-0034](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0034-major-only-requests-are-served-the-oldest-release.md), accepted 2026-10-26). In practice that caller is a 3.0 buyer, so it is no longer answered in a shape its validator rejects. A buyer that wants newer behavior sends `adcp_version`. Schemas are open by default. 3.3 opens the schemas that were meant to be open, starting with the 3.2 proposal flow ([#8531](https://github.com/adcontextprotocol/adcp/pull/8531)), and keeps the rest closed where closure is the contract, such as a join key or a privacy boundary. `commercial_terms` and the term objects inside it are held closed until 4.0. A minor adds to open schemas and adds nothing to closed ones ([DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md), decided 2026-11-09; [what opened](/docs/reference/migration/3-2-to-3-3#schemas-are-open-by-default)). @@ -114,7 +147,7 @@ These shipped before beta.3 and are summarized here with the rest. Everything ma - **Holds you can plan and extend (experimental).** Products and proposals can carry a `hold_policy` (`media_buy.hold_policy`), and `refine_proposals` `extend_hold` lengthens a committed hold without re-finalizing (`media_buy.hold_extension`). See [Hold policy](/docs/media-buy/task-reference/refine_proposals#hold-policy-experimental). - **Delegated composition (experimental).** A platform that owns the catalog can make `product_ids` the complete composable universe with `criteria.product_ids_exclusive`, and a seller that holds no inventory can declare `terms_only` finalize (`media_buy.delegated_composition`). See [delegated composition](/docs/media-buy/product-discovery/delegated-composition). - **Fixed-price, non-guaranteed sellers.** The new stable `sales-fixed-rate` specialism covers sellers in any medium, digital or linear TV, that publish a fixed price, reserve no inventory, make no delivery commitment, and may hold a buy for review. `get_media_buys` can carry `expected_confirmation_at` while a buy is provisional (`confirmed_at: null`). See [Choosing a sales specialism](/docs/building/verification/compliance-catalog#choosing-a-sales-specialism). -- **Renewal and replacement lineage (experimental).** A new buy can name the buy it succeeds with `predecessor_media_buy_id` and `lineage_reason` (`renewal`, `terms_change`, `migration`, `sunset`, `replacement`). The link is forward-only and same-account; the predecessor is never mutated. Feature id `media_buy.lineage`. See [Media Buy Lineage](/docs/media-buy/specification#media-buy-lineage). +- **Renewal and replacement lineage (experimental).** A new buy made through `buy_products` or `accept_proposal` can name the buy it succeeds with `predecessor_media_buy_id` and `lineage_reason` (`renewal`, `terms_change`, `migration`, `sunset`, `replacement`). The link is forward-only and same-account; the predecessor is never mutated. Feature id `media_buy.lineage`. See [Media Buy Lineage](/docs/media-buy/specification#media-buy-lineage). - **Did a failed mutation apply?** `core/error.json` can carry `mutation_outcome` (`not_applied`, `unknown`, `applied`), so a buyer knows whether to re-plan after a failed state-changing request. See [Mutation outcome](/docs/building/by-layer/L3/error-handling#mutation-outcome). - **Operator fees.** The `operator_fee` price adjustment kind lets an agency's buying platform show a fee it keeps out of the advertiser's budget without changing the seller's price. Sellers never author it. See [Operator fees](/docs/media-buy/advanced-topics/pricing-models#operator-fees). - **Change cutoff.** Installment deadlines can carry `change_cutoff`, the last moment a creative swap, pause, or stop still takes effect (traffic log close, posting-cycle lock, print issue close). See [Installment deadlines](/docs/media-buy/product-discovery/collections-and-installments#installment-deadlines). @@ -169,13 +202,13 @@ A seller lists the `sync_creatives` `assignment_operations` it accepts in the ne ## Platform object IDs have one name -`sync_event_sources` and `sync_audiences` results now use optional `platform_id` for the object's ID in the seller's ad platform, matching creatives and catalogs. A seller reporting this ID in 3.3 and later 3.x responses MUST emit both `platform_id` and the deprecated `seller_id` alias with identical values, including discovery responses. Buyers MUST prefer `platform_id` and fall back to `seller_id` only when the new field is absent. Continue using `event_source_id` and `audience_id` in AdCP requests. The aliases keep working throughout 3.x; removal is no earlier than 4.0 under the six-month notice policy. Seller identity in `adagents.json` and publisher identifiers is unchanged. See [Deprecations](/docs/reference/migration/3-2-to-3-3#deprecations). +`sync_event_sources` and `sync_audiences` results now use optional `platform_id` for the object's ID in the seller's ad platform, matching creatives and catalogs. A seller reporting this ID in 3.3 and later 3.x responses MUST emit both `platform_id` and the deprecated `seller_id` alias with identical values, including discovery responses. Buyers MUST prefer `platform_id` and fall back to `seller_id` only when the new field is absent. Continue using `event_source_id` and `audience_id` in AdCP requests. The aliases keep working throughout 3.x and are expected to be removed in 4.0. Seller identity in `adagents.json` and publisher identifiers is unchanged. See [Deprecations](/docs/reference/migration/3-2-to-3-3#deprecations). ## Installments on the compact product lifecycle For scheduled media the installment *is* the thing being sold — a slot in a creator's upcoming video, a podcast episode, a sponsored newsletter issue. The canonical Product that `list_products` and the proposal lifecycle read had no `installments`, so a proposal could name the creator but not which slot, when it publishes, or its material deadlines. 3.3 adds `installments[]` of the new `core/canonical-installment.json`, whose identity is the `(collection_ref, installment_id)` tuple alone. Request it in `fields`; omitting it on a product that declares `collections` still means run-of-collection. -A purchase buys the product as offered. Naming the exact slots a purchase buys, and dropping or swapping one through `refine_proposals`, was merged for 3.3 and is withdrawn to 4.0 ([below](#withdrawn-from-3-3-planned-for-4-0)). See [Installments in the compact lifecycle](/docs/media-buy/product-discovery/collections-and-installments#installments-in-the-compact-lifecycle). +A purchase buys the product as offered. Naming the exact slots a purchase buys, and dropping or swapping one through `refine_proposals`, was merged for 3.3 and is withdrawn to 4.0 ([below](#withdrawn-from-3-3-planned-for-4-0)). From rc.0, a buyer can ask for specific slots through `refine_proposals` (experimental `media_buy.installment_refinement`, [#8974](https://github.com/adcontextprotocol/adcp/pull/8974)), and the seller answers with a product that declares exactly those slots; naming slots in the signed purchase itself stays a 4.0 item. See [Choosing installments](/docs/media-buy/product-discovery/collections-and-installments#choosing-installments-experimental). See [Installments in the compact lifecycle](/docs/media-buy/product-discovery/collections-and-installments#installments-in-the-compact-lifecycle). ## Tightened rules @@ -199,7 +232,7 @@ These narrow what a conformant implementation may do. Each is detailed in the [m - **Multi-qualifier metrics omit flat totals.** When a buy's packages report a metric under more than one qualifier set, such as viewability at `mrc` and `groupm`, the seller omits that metric's flat carrier from buy and window `totals`; read the package rows. See [the migration guide](/docs/reference/migration/3-2-to-3-3#multi-qualifier-metrics-omit-flat-totals). - **Refinement carries compliance forward.** A `build_creative` refinement keeps the parent leaf's required disclosures and prohibited claims, and a refined leaf never inherits approval. See [the migration guide](/docs/reference/migration/3-2-to-3-3#refinement-carries-compliance-forward). -Two more guarantees loosen here, and the response-size default a third ([below](#bounded-agent-responses)): a 3.2 verifier can reject a brand.json between 256 KiB and 2 MiB that a 3.3 verifier accepts, and a `ready` audience no longer promises match counts. Separately, `reporting_webhook.authentication` and `artifact_webhook.authentication` become optional on requests served at 3.3, so an integration can drop HMAC before 4.0 ([details](/docs/reference/migration/3-2-to-3-3#reporting-and-artifact-webhooks-can-omit-authentication)). Many new fields sit inside objects 3.2 closes, so send them only to peers that negotiated 3.3; see [Send only to 3.3 peers](/docs/reference/migration/3-2-to-3-3#send-only-to-3-3-peers). +Two more guarantees loosen here, and the response-size default a third ([below](#bounded-agent-responses)): a 3.2 verifier can reject a brand.json between 256 KiB and 2 MiB that a 3.3 verifier accepts, and a `ready` audience no longer promises match counts. Separately, `reporting_webhook.authentication` and `artifact_webhook.authentication` become optional on requests served at 3.3, so an integration can drop HMAC before 4.0 ([details](/docs/reference/migration/3-2-to-3-3#reporting-and-artifact-webhooks-can-omit-authentication)). Many new fields sit inside objects that 3.2.10 and earlier publish closed, so send them only to peers that negotiated 3.3; see [Send only to 3.3 peers](/docs/reference/migration/3-2-to-3-3#send-only-to-3-3-peers). ## Optional declarations @@ -269,7 +302,9 @@ Three changes need no new rule. Schema validation now refuses a `period_duration ## Experimental in 3.3 -New feature ids are `media_buy.spot_lifecycle`, `media_buy.daypart_granularity`, `creative.broadcast_loudness`, `media_buy.hold_policy`, `media_buy.hold_ranking`, `media_buy.installment_holds`, `media_buy.hold_extension`, `media_buy.delegated_composition`, `media_buy.collection_cards`, `media_buy.collection_catalog`, `brand.collection_links`, `media_buy.open_opportunities`, `media_buy.lineage`, `media_buy.delivery_projection`, `media_buy.installment_lifecycle`, `media_buy.collection_lists`, `media_buy.offline_delivery_metrics`, `signals.signal_lifecycle`, `signing.web_bot_auth`, `account.agent_onboarding`, `account.requests`, `media_buy.reporting_subscriptions`, `creative.live_updates`, `media_buy.seller_offers`, `media_buy.price_adjustments`, `media_buy.execution_readiness`, `media_buy.gender_targeting`, `media_buy.measurement_provenance`, `media_buy.audience_evidence_targets`, `account.invoice_lines`, `signals.pricing_groups`, `signals.delivery_methods`, `security.profiles`, and `identity.trust_json`. `media_buy.purchase_rights` and `media_buy.installment_selection` shipped in beta.1 and are withdrawn, so they are not registered. `media_buy.offline_delivery_metrics` registers the new `print_metrics` block together with the 3.2 `ooh_metrics` block. `identity.trust_json` publishes the `trust.json` v1 schemas, identifying agents by origin with no keys in the record; the Web Bot Auth profile reads it, and publishers declare nothing ([trust.json](/docs/reference/trust-json)). Governance budget periods extend the existing `governance.campaign` cluster, `get_principal` relationship status extends `protocol.principal`, and rights channel restrictions extend `brand.rights_lifecycle`. The `creative.evaluator` surface on `build_creative` drops its account-arranged `evaluator_id` source form and withdraws the `list_evaluators` follow-on: sources are now inline `exemplars` or an allowlisted `agent_url`, and a seller's house evaluator is an agent it lists in `creative_policy.accepted_verifiers[]` ([migration](/docs/reference/migration/3-2-to-3-3#experimental-creative-evaluator-drops-evaluator_id)). Reliable Reporting carries a new breaking-change notice: older superseded snapshots [may be compacted](/docs/reference/migration/3-2-to-3-3#superseded-reporting-snapshots-may-be-compacted) no earlier than the first minor after November 20, 2026. The per-surface status table is in the [release notes](/docs/reference/release-notes#experimental-surfaces-in-3-3). +New feature ids are `media_buy.spot_lifecycle`, `media_buy.daypart_granularity`, `creative.broadcast_loudness`, `media_buy.hold_policy`, `media_buy.hold_ranking`, `media_buy.installment_holds`, `media_buy.hold_extension`, `media_buy.delegated_composition`, `media_buy.collection_cards`, `media_buy.collection_catalog`, `brand.collection_links`, `media_buy.open_opportunities`, `media_buy.lineage`, `media_buy.delivery_projection`, `media_buy.installment_lifecycle`, `media_buy.collection_lists`, `media_buy.offline_delivery_metrics`, `signals.signal_lifecycle`, `signing.web_bot_auth`, `account.agent_onboarding`, `account.requests`, `media_buy.reporting_subscriptions`, `creative.live_updates`, `media_buy.seller_offers`, `media_buy.execution_readiness`, `media_buy.gender_targeting`, `media_buy.measurement_provenance`, `account.invoice_lines`, `signals.pricing_groups`, `signals.delivery_methods`, `security.profiles`, and `identity.trust_json`. `media_buy.purchase_rights` and `media_buy.installment_selection` shipped in beta.1 and are withdrawn, so they are not registered, and `media_buy.price_adjustments` and `media_buy.audience_evidence_targets` shipped in the betas and are withdrawn at rc.0. `media_buy.offline_delivery_metrics` registers the new `print_metrics` block together with the 3.2 `ooh_metrics` block. `identity.trust_json` publishes the `trust.json` v1 schemas, identifying agents by origin with no keys in the record; the Web Bot Auth profile reads it, and publishers declare nothing ([trust.json](/docs/reference/trust-json)). Governance budget periods extend the existing `governance.campaign` cluster, `get_principal` relationship status extends `protocol.principal`, and rights channel restrictions extend `brand.rights_lifecycle`. The `creative.evaluator` surface on `build_creative` drops its account-arranged `evaluator_id` source form and withdraws the `list_evaluators` follow-on: sources are now inline `exemplars` or an allowlisted `agent_url`, and a seller's house evaluator is an agent it lists in `creative_policy.accepted_verifiers[]` ([migration](/docs/reference/migration/3-2-to-3-3#experimental-creative-evaluator-drops-evaluator_id)). Reliable Reporting carries a new breaking-change notice: older superseded snapshots [may be compacted](/docs/reference/migration/3-2-to-3-3#superseded-reporting-snapshots-may-be-compacted) no earlier than the first minor after November 20, 2026. The per-surface status table is in the [release notes](/docs/reference/release-notes#experimental-surfaces-in-3-3). + +rc.0 adds `media_buy.installment_refinement` and `media_buy.installment_creative_assignment` ([New in rc.0](#new-in-rc-0)). Beta.5 adds `media_buy.match_keys` ([above](#new-in-beta-5)), which stays experimental at 3.3 GA and extends the experimental `Product.identity` declaration and TMP provider registration with match keys. @@ -305,7 +340,8 @@ These merged on `main` during the 3.3 cycle and were also released on the 3.2 li | A fixed-price, non-guaranteed seller | Claim `sales-fixed-rate`; keep a held buy in `pending_start` until you confirm or reject it. | | A seller that wants to send proposals after the first response | Opt in to `media_buy.open_opportunities`: advertise `list_proposals` first, then `later_proposals` with a `max_open_duration`, and honor buyer consent and limits. | | A linear TV, print, or DOOH seller | Adopt the delivery fields you can populate; gate 3.3-only rows and fields on the negotiated version. | -| An SDK maintainer | Generate from the signed `3.3.0-beta.5` tarball, not `main`, and check the [SDK-facing changes](/docs/reference/migration/3-2-to-3-3#sdk-and-code-generator-maintainers). | +| An SDK maintainer | Generate from the signed `3.3.0-rc.0` tarball, not `main`, and check the [SDK-facing changes](/docs/reference/migration/3-2-to-3-3#sdk-and-code-generator-maintainers), including the opened schemas, which change generated types. | +| A seller, buyer, or SDK built from a beta bundle | Drop the beta fields that leave 3.3 at rc.0 and move the ones that change home; see the [closed-schema triage](/docs/reference/migration/3-2-to-3-3#closed-schema-triage-what-stays-in-3-3). | | A seller that opens buyer-declared accounts | Return `account_id` from `sync_accounts`, accept it on every account-scoped task, and never change it; update countries and other attributes in place. | | A seller supporting `account.requests` | Return `account`, with its money terms, on every request that resolves `matched` or `created`; send `effective_at` on money changes and `not_carried_over` on a separate account; refuse `currency` or `timezone` changes you don't list in `changeable_attributes`. | | A seller advertising `media_buy.reporting_subscriptions` | Publish `cancellation_effective_at`, `flight_history`, per-package `reporting_delivery_offering_ids`, `authorization.regranted_at`, and offering `available_from` / `withdrawn_at`; owe billing stubs at cutovers; deliver only inside a buy's flight; key managed-delivery rows on `account_id`; emit `packages[].added_at` on packages added after confirmation; treat a grant reduced without `get_reporting_status` as a loss of authority; list `reset_state` with `reporting_subscription_probe`. | @@ -321,13 +357,13 @@ These merged on `main` during the 3.3 cycle and were also released on the 3.2 li | A seller that registers webhooks | Sign with the profile `signing_profile` names, default `adcp/webhook-signing/v1`; with `legacy_hmac_fallback: false`, reject an `authentication` block with `UNSUPPORTED_FEATURE`. | | A seller that returns product rosters | Return `publisher_properties: []` or `collections: []` only to callers served 3.3 or later; apply any exclusion list you accept against your full internal roster. | | A seller with canceled or completed buys | Keep the packages, with stable identities and the latest committed configuration, and disclose irrecoverable history through nonfatal errors. | -| A seller or SDK that builds task responses | Compose the protocol envelope on every response, include `status`, and truncate (MUST, not fail) a `message` over 2,000 characters. Regenerate types from the beta.5 schemas. | +| A seller or SDK that builds task responses | Compose the protocol envelope on every response, include `status`, and truncate (MUST, not fail) a `message` over 2,000 characters. Regenerate types from the rc.0 schemas. | | An in-house client that sends only `adcp_major_version` | You are served the oldest supported release in that major (3.0 where supported). Send `adcp_version` to get newer behavior. | | A seller that advertises `get_adcp_capabilities` fields | Stay within the structural bounds; do not design to a byte figure. | | A seller that wants to offer a change to a signed buy | Opt in to `media_buy.seller_offers` after `media_buy.open_opportunities`; send offers only to callers served 3.3. | | A seller of signals | Declare `signals.delivery_methods` before accepting a `delivery_method` pin; publish `signal_pricing_group_rules[]` if listings share a `pricing_group`. | | A seller with live creatives | Declare `creative.live_updates` per change kind, list `replace` in `creative.assignment_operations`, and refuse the rest with `CREATIVE_LIVE_UPDATE_UNSUPPORTED`. | -| A compliance operator | Treat each 3.3 beta bundle as an implementation input. As for 3.2, prerelease grading runs are diagnostic, not a badge. | +| A compliance operator | Treat each 3.3 prerelease bundle as an implementation input. As for 3.2, prerelease grading runs are diagnostic, not a badge. | | A seller that accepts `assignment_operations` | List exactly the operations you accept in `creative.assignment_operations` and reject any other with `UNSUPPORTED_FEATURE`; buyers send nothing to a 3.3 seller that lists none. Transfer the replaced assignment's settings on `replace`, rejecting the request rather than dropping one, and apply tracker-slot limits only where the effective format declares a tracker slot. | | A buyer that sends `assignment_operations` | Send only the operations the seller lists in `creative.assignment_operations`, and follow a refusal's recovery only through operations the seller lists. | | Any agent that sends AdCP responses | Emit only properties the served release defines, plus `ext.{namespace}` and open-payload fields. | @@ -343,13 +379,15 @@ Three features are not part of 3.3. All three add terms to `commercial_terms`, w |---|---|---| | **Definition pins** (`commercial_terms.definition_pins[]`, the `definition_changed` refinement reason, `REFERENCE_DEFINITION_CHANGED`, #7960) | Published in `3.3.0-beta.0` and `3.3.0-beta.1` | Removed after beta.1. Stop emitting pins and the reason and code, and stop requiring them. The `definition_pin_drift` storyboard and the controller `definition_pin_probe` scenario are removed with them. | | **Purchase rights** (`purchases[].rights[]`, `media_buy.purchase_rights`, #8101) | Published in `3.3.0-beta.1` (experimental) | Removed after beta.1, together with the `brand/rights-scope.json` hoist and the `paid_amplification` and `content_reuse` values of `right-use`. `brand/rights-terms.json` returns to its 3.2 form. | -| **Installment selection** (`purchases[].installments[]`, `refine_proposals` `installment_changes`, `media_buy.installment_selection`, #8246) | Published in `3.3.0-beta.1` (experimental) | Removed after beta.1. Installments on the canonical product and `holds[]` stay in 3.3. | +| **Installment selection** (`purchases[].installments[]`, `refine_proposals` `installment_changes`, `media_buy.installment_selection`, #8246) | Published in `3.3.0-beta.1` (experimental) | Removed after beta.1. Installments on the canonical product and `holds[]` stay in 3.3. rc.0 brings back the request side as experimental `media_buy.installment_refinement` (#8974); `purchases[].installments[]` stays planned for 4.0. | The designs are kept for 4.0: see [Planned for 4.0](/docs/reference/migration/v4-compatibility#planned-for-4-0-withdrawn-from-3-3). +The closed-schema triage adds four more fields to the 4.0 list at rc.0, because each would extend the commercial terms held closed until 4.0: `metric_id` on performance standards, `price_adjustments`, `counting_mechanisms`, and `target_audiences` on purchases ([New in rc.0](#new-in-rc-0)). The `metric_id` withdrawal ([#8854](https://github.com/adcontextprotocol/adcp/pull/8854)) is in review, not in rc.0. + ## In review for 3.3 -Open 3.3 proposals are not part of any beta until they merge. Six working-group decisions are ratified or accepted, and their normative text has merged: +Open 3.3 proposals are not part of any prerelease until they merge. Six working-group decisions are ratified or accepted, and their normative text has merged: - **Agent identity is an origin ([DR-0023](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0023-agent-identity-is-an-origin.md)).** Merged: the [Web Bot Auth profile](/docs/building/by-layer/L1/wba-profile) [#7894](https://github.com/adcontextprotocol/adcp/pull/7894), Web Bot Auth identities and the deprecation of the RFC 9421 brand.json profile [#8162](https://github.com/adcontextprotocol/adcp/pull/8162), first-contact binding [#8168](https://github.com/adcontextprotocol/adcp/pull/8168), the buyer walkthrough and migration guide [#8172](https://github.com/adcontextprotocol/adcp/pull/8172), the experimental production security profile [#8155](https://github.com/adcontextprotocol/adcp/pull/8155), seller onboarding posture [#8170](https://github.com/adcontextprotocol/adcp/pull/8170), and the R7/R8 erratum [#8219](https://github.com/adcontextprotocol/adcp/pull/8219). `request_account` [#8293](https://github.com/adcontextprotocol/adcp/pull/8293), then the single account write and reporting subscriptions ([#8543](https://github.com/adcontextprotocol/adcp/issues/8543): [#8551](https://github.com/adcontextprotocol/adcp/pull/8551), [#8552](https://github.com/adcontextprotocol/adcp/pull/8552)). - **Responses conform to the served release ([DR-0024](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0024-responses-conform-to-served-release.md), [#8117](https://github.com/adcontextprotocol/adcp/pull/8117)).** Merged. The rule is in [Serving an older pin](/docs/reference/versioning#serving-an-older-pin); advisory grading of undefined properties merged in [#8156](https://github.com/adcontextprotocol/adcp/pull/8156) (beta.4). @@ -362,7 +400,7 @@ Records DR-0027 to DR-0030 (mutation outcome, `sales-fixed-rate`, delivery proje ## Start here -1. Read the [3.3 beta program](/docs/reference/3-3-beta). +1. Read the [3.3 prerelease program](/docs/reference/3-3-beta). 2. Follow [Migrating from 3.2 to 3.3](/docs/reference/migration/3-2-to-3-3). 3. Choose the exact package and support level in [Choose your SDK](/docs/building/by-layer/L4/choose-your-sdk). 4. Use the [Release Notes](/docs/reference/release-notes#version-3-3-0) for the cumulative record. diff --git a/specs/daily-budget-constraints.md b/specs/daily-budget-constraints.md index 4d65f1ed660..93bf947c2d4 100644 --- a/specs/daily-budget-constraints.md +++ b/specs/daily-budget-constraints.md @@ -19,11 +19,12 @@ without the same planning information. Any legacy projection retained in 4.0 should preserve the same constraints, subject to the negotiated schema. Do not add a temporary second home for minimums merely to fit them into 3.3. -`core/canonical-pricing-option.json`, `media-buy/product-purchase-input.json`, -`media-buy/product-purchase.json`, and `media-buy/commercial-terms.json` were -published closed. The repository's additive-minor gate rejects new properties -there. DR-0036 is proposed but its rule is enforced by that gate; these new -budget semantics do not qualify as a correction of already-required behavior. +`core/canonical-pricing-option.json`, `media-buy/product-purchase.json`, and +`media-buy/commercial-terms.json` are held closed until 4.0 (DR-0036, decided +2026-11-09). A minor adds nothing to them, and the additive-minor gate rejects +new properties there. `media-buy/product-purchase-input.json` opens in 3.3, +but a minimum accepted there would have no home in the purchase it produces, +so these budget semantics still wait for 4.0. ## Recommended release sequence