Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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/align-32-docs-rc3.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"adcontextprotocol": patch
---

Align the 3.2 docs, announcement banner, and SDK guidance with the published 3.2.0-rc.3 checkpoint and @adcp/sdk@14.0.0-rc.36.
2 changes: 1 addition & 1 deletion docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"$schema": "https://mintlify.com/schema.json",
"name": "AdCP - Ad Context Protocol",
"banner": {
"content": "AdCP 3.2 release candidate adds Reliable Reporting to the compact lifecycle — [open the current signed release →](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.2)",
"content": "The AdCP 3.2 release candidate now hardens the Reliable Reporting consumer-status loop and adds MediaBuy-level frequency caps — [see what's new →](/3.2)",
"dismissible": true
},
"description": "AdCP (Ad Context Protocol) is the open standard for agentic advertising. It defines how AI agents buy media, generate creatives, activate audiences, and enforce governance across platforms. Current stable documentation index: https://docs.adcontextprotocol.org/llms-current.md.",
Expand Down
18 changes: 13 additions & 5 deletions docs/building/by-layer/L4/choose-your-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ For the layered model behind this — what each layer contains and what an SDK a

What "shipped" means at each layer is the [L0–L3 checklist](/docs/building/cross-cutting/sdk-stack#what-an-sdk-at-each-layer-should-provide).

*Last updated: 2026-09-11.*
*Last updated: 2026-09-14.*

| SDK | Current package | 3.2 RC support | L0 | L1 | L2 | L3 |
|---|---|---|:-:|:-:|:-:|:-:|
Expand All @@ -33,11 +33,15 @@ What "shipped" means at each layer is the [L0–L3 checklist](/docs/building/cro

Legend: ✅ shipped · ⚠️ partial / role-dependent · ❌ not yet covered. The L0–L3 columns describe the current package, not a 3.2 support claim.

The current `rc` npm tag of `@adcp/sdk` is ahead of this checkpoint: it embeds `3.2.0-rc.2` and adds the seller-side reporting modules (`@adcp/sdk/reporting/source` and `@adcp/sdk/reporting/ledger`). The repository checkpoint alignment follows once the Python and Go SDKs publish matching bundles.

<Warning>
**All three maintained SDKs now embed RC.1.** Pin the exact package and wire
versions shown here for development and staging. This is not a GA signal:
production integrations should remain on 3.1 until 3.2 is released. See the
[3.2 prerelease program](/docs/reference/3-2-beta).
**No SDK embeds RC.3, the current protocol checkpoint.** All three still
embed `3.2.0-rc.1`. Pin the exact package
and wire versions shown here for development and staging, and test RC.3 from
its [signed bundle](/docs/reference/3-2-beta#use-the-rc-3-artifact-directly).
This is not a GA signal: production integrations should remain on 3.1 until
3.2 is released. See the [3.2 prerelease program](/docs/reference/3-2-beta).
</Warning>

The TypeScript SDK currently provides the broadest L0–L3 surface. Python is a
Expand Down Expand Up @@ -205,6 +209,10 @@ npx @adcp/sdk@14.0.0-rc.35 my-agent list_products '{"adcp_version":"3.2-rc.1","a
npx @adcp/sdk@14.0.0-rc.35 test-mcp list_products '{"adcp_version":"3.2-rc.1"}'
```

The `adcp_version` in the payload is a wire pin the CLI passes through, so it
can name a checkpoint other than the one the SDK embeds. Request and response
validation still uses the SDK's embedded bundle.

The CLI also drives storyboards (`adcp storyboard run`), conformance grading (`adcp grade`), and registry diagnostics. See `--help` for the full surface.

### Python CLI
Expand Down
10 changes: 6 additions & 4 deletions docs/intro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,13 @@ description: "AdCP is an open agentic advertising standard. Follow Alex's team f
<img src="/images/walkthrough/adcp-01-fragmentation.png" alt="Alex stands arms crossed in a war room of mismatched screens and tangled cables, surveying the chaos — her team hunched over laptops in the background" style={{ width: '100%', borderRadius: '12px', marginBottom: '2rem' }} />

<Info>
AdCP 3.2 is in release candidate. RC.1 is the current signed protocol bundle;
AdCP 3.2 is in release candidate. RC.3 is the current signed protocol bundle;
it combines the proposal-to-operation lifecycle, an experimental
authenticated-principal connection layer, and experimental Reliable Reporting
1.0. The TypeScript, Python, and Go SDKs now publish exact RC.1 pairings for
staging integration tests. Keep production traffic on 3.1 until 3.2 reaches GA.
authenticated-principal connection layer, a hardened experimental Reliable
Reporting consumer-status loop, and shared MediaBuy-level frequency caps. No
SDK embeds RC.3 yet — test it from its signed bundle, or run SDK-backed
staging tests against the checkpoint your SDK embeds. Keep production traffic
on 3.1 until 3.2 reaches GA.
See
[what's new in 3.2](/docs/reference/whats-new-in-3-2) and the
[prerelease program](/docs/reference/3-2-beta) before testing.
Expand Down
13 changes: 8 additions & 5 deletions docs/media-buy/reporting-core-implementation-guide.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,12 @@ Reliable Reporting is experimental in 3.2. `reporting.core` is its required
tier; `managed_delivery` and `reconciled_billing` are separately advertised
optional tiers.

The consumer-status loop is additive and opt-in in current source. Sellers
advertise `consumer_status_task` only when implemented. The active notice makes
it required Core in the next eligible minor after October 24, 2026; RC.1 and the
current public training seller remain unchanged.
The consumer-status loop is additive and opt-in. It is published in
`3.2.0-rc.2` and hardened in `3.2.0-rc.3`, and it stays opt-in until the notice
window closes on October 24, 2026. Sellers advertise `consumer_status_task`
only when implemented. The active notice makes it required Core in the next
eligible minor after that date; RC.1 and the current public training seller
remain unchanged.
</Warning>

Every buyer eventually asks one question: **"do I have definitive reporting
Expand Down Expand Up @@ -299,7 +301,8 @@ digest is intentionally retained).
received.

Reliable Reporting 1.0 is published in the RC wire bundles; the consumer-status
loop lands in `3.2.0-rc.2`. The public training sales agent serves whichever
loop is published in `3.2.0-rc.2` and hardened in `3.2.0-rc.3`. The public
training sales agent serves whichever
prerelease contract its deployment advertises, which may trail the newest
published bundle. Read the advertised version from
`get_adcp_capabilities` and put that exact negotiated value on every
Expand Down
11 changes: 6 additions & 5 deletions docs/media-buy/task-reference/get_reporting_status.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,12 @@ description: "Check Reliable Reporting health, enumerate expected periods and re

<Warning>
**Reliable Reporting 1.0 is published through `3.2.0-rc.3` and remains
experimental.** RC.2 publishes the opt-in consumer-status sync and readback;
RC.3 adds its hardening. Sellers implementing that extension advertise
`consumer_status_task`; it becomes required Core only in the next eligible minor
after the notice window. Sellers declare `media_buy.reporting_delivery` in
`get_adcp_capabilities.experimental_features`.
experimental.** RC.2 publishes the opt-in consumer-status sync and readback and
RC.3 hardens it. Sellers implementing that extension advertise
`consumer_status_task`; it stays opt-in until the notice window closes on
October 24, 2026, and becomes required Core only in the next eligible minor
after that date. Sellers declare
`media_buy.reporting_delivery` in `get_adcp_capabilities.experimental_features`.
</Warning>

`get_reporting_status` is the authoritative status surface for AdCP 3.2
Expand Down
5 changes: 3 additions & 2 deletions docs/media-buy/task-reference/sync_reporting_status.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,9 @@ description: "Tell a seller whether expected reporting was received, omitted, mi
`sync_reporting_status` is an additive, opt-in Reliable Reporting extension
published in `3.2.0-rc.2` and hardened in `3.2.0-rc.3`. RC.1 implementations do
not expose it. Sellers that implement it advertise `consumer_status_task`; the
active breaking-change notice makes it required Core only in the next eligible
minor after October 24, 2026.
task stays opt-in until the active breaking-change notice window closes on
October 24, 2026, and becomes required Core only in the next eligible minor
after that date.
</Warning>

`sync_reporting_status` closes the operational loop between what a seller says
Expand Down
Loading
Loading