Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
e88d198
docs(reference): bring the 3.3 release docs to 3.3.0-rc.0
bokelley Nov 10, 2026
f63fb12
docs(reference): state the 12-month 3.3 support window after 4.0 GA
bokelley Nov 10, 2026
8af6fcd
docs(reference): describe the commercial terms as held closed until 4.0
bokelley Nov 10, 2026
005fd23
docs(reference): prerelease pins, unpinned discovery, and anonymous c…
bokelley Nov 12, 2026
e65d27c
docs(reference): follow #8866 and the other rc.0 merges in the 3.3 re…
bokelley Nov 12, 2026
7012b7f
docs(sdk): keep the SDK matrix on the installed @adcp/sdk prerelease
bokelley Nov 12, 2026
f0f4087
docs(reference): resolve the #8858 and #8864 markers in the 3.3 relea…
bokelley Nov 12, 2026
3509430
docs(reference): point the available_installment_statuses markers at …
bokelley Nov 12, 2026
236affd
docs(reference): resolve the #8762 and #8957 markers in the 3.3 relea…
bokelley Nov 12, 2026
cf32851
docs(reference): resolve the #8758 markers in the 3.3 release docs
bokelley Nov 12, 2026
61389cd
docs(reference): resolve the #8767 markers and describe the withdrawn…
bokelley Nov 12, 2026
2767143
docs(reference): add the rc.0 installment experiments, with dependenc…
bokelley Nov 13, 2026
ee24bd3
docs(reference): cover #8884's signed-terms acceptance rule in the rc…
bokelley Nov 13, 2026
6f68a45
docs(reference): describe #8972, per-installment creative assignment,…
bokelley Nov 13, 2026
8ead486
docs(reference): describe #8974, installment refinement, in the rc.0 …
bokelley Nov 13, 2026
a4c2386
docs(reference): cover #8793 and #8458 in the rc.0 docs
bokelley Nov 13, 2026
4895456
docs(reference): resolve the 3.2.11 markers
bokelley Nov 13, 2026
3cc61dd
docs(reference): resolve the #8974 markers
bokelley Nov 13, 2026
7699284
docs(reference): describe #8983, report definitions at contract_versi…
bokelley Nov 13, 2026
89c02f9
docs(reference): resolve the #8972 markers
bokelley Nov 13, 2026
a433284
docs(reference): resolve the #8983 markers
bokelley Nov 13, 2026
414bb55
docs(reference): add 3.3.0-beta.6 ahead of rc.0
bokelley Nov 13, 2026
4bba82e
docs(reference): describe #8966, display labels for geo targeting cod…
bokelley Nov 13, 2026
a83bcd9
docs(reference): resolve the beta.6 date markers
bokelley Nov 13, 2026
c9ae2ba
docs(reference): describe #8995, social distribution identifier types…
bokelley Nov 13, 2026
72ce6b6
docs(reference): resolve the #8995 markers and fold #8997 into the rc…
bokelley Nov 14, 2026
0bbe988
docs(reference): add #8970 and the other post-beta.6 merges to the rc…
bokelley Nov 14, 2026
fb9b942
docs(reference): write #8854 up as in review, not in rc.0
bokelley Nov 15, 2026
7f07705
docs(reference): take #9018's beta.6 SDKs and test-agent preview, and…
bokelley Nov 15, 2026
e7578cc
docs(reference): fold #8989, #9007 and the last post-beta.6 changeset…
bokelley Nov 16, 2026
bd832f0
docs(reference): resolve the rc.0-cut markers
bokelley Nov 16, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/prerelease-pins-anonymous-discovery.md
Original file line number Diff line number Diff line change
@@ -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.
5 changes: 5 additions & 0 deletions .changeset/refresh-3-3-release-docs-rc0.md
Original file line number Diff line number Diff line change
@@ -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.
4 changes: 4 additions & 0 deletions docs/building/by-layer/L0/mcp-guide.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
8 changes: 5 additions & 3 deletions docs/building/by-layer/L2/authentication.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
7 changes: 5 additions & 2 deletions docs/building/by-layer/L4/choose-your-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/media-buy/media-buys/optimization-reporting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading
Loading