Skip to content
Closed
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 CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

- 8644cdf: Update the TypeScript SDK dependency and current 3.2 RC guidance, certification prompts, conformance metadata, and provenance assertions to `@adcp/sdk@14.0.0-rc.35`.
- acab756: Harden the experimental Reliable Reporting consumer-status loop. Reserve `authoritative_party` on `reporting-delivery-config.json` (sellers MUST reject `consumer` with `UNSUPPORTED_FEATURE` until a later minor defines the buyer-deposited revision task) and relax the seller-authoritative billing-feed constraint accordingly. Give a `received` status made stale only by a seller restatement a bounded `delayed` grace window before it escalates. Make the buyer's posting deadline `expected_at + automated_recovery_window_seconds` and surface unmet deadlines through `obligation_counts.consumer_status_pending`, a count that never changes seller health. Add issue lifecycle fields (`opened_at`, `issue_state`, `external_ref`) with optional `consumer_mismatch_escalation_seconds` and `operations_contact` capability advertisement. Add the `content_mismatch` consumer status with a closed `mismatch_code` for contract-fact disagreements, which are explicitly not measurement disputes. Extend the `reporting_core_lifecycle_probe` controller with `restate_after_received` so the grace projection is graded live, and make the reference seller reject the reserved `authoritative_party` value so the normative MUST has working code behind it.
- decd95f: Retire superseded 3.x beta prerelease artifacts from `dist/schemas`, `dist/compliance`, and `dist/protocol`, keeping only the `3.2.0-beta.11` schema bundle (frozen `3.2-beta` documentation selector), `3.2.0-beta.6` (the training agent's retained checkpoint), and `3.1.0-beta.7` (the TypeScript SDK side bundle). This removes about 2 GB from the repository and the runtime image, whose size gate the rc.3 release branch had started to exceed. Previously published beta URLs continue to be served from the artifact CDN on a best-effort basis; documentation now links to the `3.2.0-rc.2` bundle. The immutable-release-artifact guard now permits whole-tree deletion of tagged beta checkpoints while still rejecting in-place edits and any deletion of release-candidate or stable artifacts.
- decd95f: Retire superseded 3.x beta prerelease artifacts from `dist/schemas`, `dist/compliance`, and `dist/protocol`, keeping only the `3.2.0-beta.11` schema bundle (frozen `3.2-beta` documentation selector), `3.2.0-beta.6` (the training agent's retained checkpoint), and `3.1.0-beta.7` (the TypeScript SDK side bundle). This removes about 2 GB from the repository and the runtime image, whose size gate the rc.3 release branch had started to exceed. Previously published beta URLs continue to be served from the artifact CDN on a best-effort basis; documentation now links to the `3.2.0-rc.2` bundle. The beta removal was a one-time repository and runtime-image cleanup. Tagged beta, release-candidate, and stable artifacts that remain are immutable release records: later deletion or in-place modification is rejected.
- 8d50c0e: `scripts/run-storyboards-matrix.sh` snapshots the freshly built `dist/schemas/latest` into a temporary directory and runs every tenant against that copy, so a concurrent `npm run build:schemas` in the same tree can no longer abort a tenant with the SDK's schema-root version mismatch. The pre-push hook treats the local matrix as advisory: it is skipped when the working tree has uncommitted changes or when `ADCP_SKIP_STORYBOARD_MATRIX=1`, with the `training-agent-storyboards.yml` workflow as the authoritative gate.
- 322e39c: Update the pinned Changesets release action to v2.1.2 and refresh its vendored contract fixture and release-workflow verification.

Expand Down
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 — [open the current signed release →](https://github.com/adcontextprotocol/adcp/releases/tag/v3.2.0-rc.3)",
"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
32 changes: 19 additions & 13 deletions docs/building/by-layer/L4/choose-your-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,21 +23,23 @@ 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 |
|---|---|---|:-:|:-:|:-:|:-:|
| **`@adcp/sdk`** (TypeScript) | `14.0.0-rc.35` | Exact `3.2.0-rc.1` support | ✅ | ✅ | ✅ | ✅ |
| **`@adcp/sdk`** (TypeScript) | `14.0.0-rc.36` | Exact `3.2.0-rc.2` support | ✅ | ✅ | ✅ | ✅ |
| **`adcp`** (Python) | `8.0.0b14` | Exact `3.2.0-rc.1` schemas and types; higher-level helpers remain partial | ✅ | ⚠️ | ⚠️ | ⚠️ |
| **`adcp/v3`** (Go) | `v3.2.1` | Exact `3.2.0-rc.1` generated schemas and types; higher layers remain role-dependent | ✅ | ⚠️ | ⚠️ | ⚠️ |

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

<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.** TypeScript embeds
`3.2.0-rc.2`; Python and Go 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 @@ -89,7 +91,7 @@ documents coordinator options, continuation storage, and supported projections.
[![npm version](https://img.shields.io/npm/v/@adcp/sdk)](https://www.npmjs.com/package/@adcp/sdk)

```bash
npm install @adcp/sdk@14.0.0-rc.35
npm install @adcp/sdk@14.0.0-rc.36
```

```javascript
Expand All @@ -103,7 +105,7 @@ const client = createSingleAgentClient({
});

const products = await client.listProducts({
adcp_version: '3.2-rc.1',
adcp_version: '3.2-rc.2',
account: { account_id: 'account_123' },
criteria: {
offer_filters: { channels: ['ctv'] },
Expand Down Expand Up @@ -198,13 +200,17 @@ Both SDKs share the same positional shape: `adcp <agent> [tool] [payload]`. The
### JavaScript CLI

```bash
npx @adcp/sdk@14.0.0-rc.35 --help
npx @adcp/sdk@14.0.0-rc.35 --save-auth my-agent https://sales.example.com/mcp
npx @adcp/sdk@14.0.0-rc.35 my-agent list_products '{"adcp_version":"3.2-rc.1","account":{"account_id":"account_123"}}'
# or against the built-in public test agent:
npx @adcp/sdk@14.0.0-rc.35 test-mcp list_products '{"adcp_version":"3.2-rc.1"}'
npx @adcp/sdk@14.0.0-rc.36 --help
npx @adcp/sdk@14.0.0-rc.36 --save-auth my-agent https://sales.example.com/mcp
npx @adcp/sdk@14.0.0-rc.36 my-agent list_products '{"adcp_version":"3.2-rc.2","account":{"account_id":"account_123"}}'
# or against the built-in public test agent, which still serves "3.2-rc.1":
npx @adcp/sdk@14.0.0-rc.36 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 `3.2.0-rc.2` 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
8 changes: 5 additions & 3 deletions docs/learning/supplements/buyer-briefs-and-get-products.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,11 @@ The goal is not to make the brief verbose. The goal is to put intent in the brie

<Note>
This module teaches the AdCP 3.2 targeting-aware discovery contract. The public
training seller supports the exact `3.2-rc.1` wire bundle with
`@adcp/sdk@14.0.0-rc.35`. Verify those advertised capabilities before the lab;
unknown-field acceptance by an older seller is not evidence of support.
training seller supports the exact `3.2-rc.1` wire bundle. Drive it with
`@adcp/sdk@14.0.0-rc.36`, which embeds `3.2.0-rc.2` and therefore takes
`3.2-rc.1` as a wire pin rather than as its `adcpVersion` schema selection.
Verify those advertised capabilities before the lab; unknown-field acceptance
by an older seller is not evidence of support.
</Note>

## Mental model
Expand Down
8 changes: 6 additions & 2 deletions docs/learning/tracks/buyer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -257,7 +257,9 @@ New to running tool calls and reading JSON in a terminal? Do [A2b: Testing your

<Note>
The public training seller implements targeting-aware discovery on the exact
AdCP `3.2-rc.1` wire bundle. Pin `@adcp/sdk@14.0.0-rc.35`, verify the
AdCP `3.2-rc.1` wire bundle. Pin `@adcp/sdk@14.0.0-rc.36` and send `3.2-rc.1`
as the wire pin: RC.36 embeds `3.2.0-rc.2`, so it validates against that
bundle and its `adcpVersion` option will not accept `3.2-rc.1`. Verify the
seller's advertised version and lifecycle tools, and retain the request,
response, and package readback as assessment evidence. Do not treat an
uncapable seller silently ignoring unknown fields as validation.
Expand All @@ -281,7 +283,9 @@ To see the seller responses your agent must handle, you can inspect the test sel

```bash
# Inspects the test SELLER's get_products response — the shape your buyer agent must parse.
npx @adcp/sdk@14.0.0-rc.35 test-mcp get_products '{"adcp_version":"3.2-rc.1","idempotency_key":"550e8400-e29b-41d4-a716-446655442065","buying_mode":"brief","brief":"your campaign brief"}'
# The CLI passes adcp_version through, so "3.2-rc.1" reaches the seller even
# though @adcp/sdk@14.0.0-rc.36 embeds 3.2.0-rc.2 for its own validation.
npx @adcp/sdk@14.0.0-rc.36 test-mcp get_products '{"adcp_version":"3.2-rc.1","idempotency_key":"550e8400-e29b-41d4-a716-446655442065","buying_mode":"brief","brief":"your campaign brief"}'
```

See [Build a caller](/docs/building/by-layer/L4/build-a-caller) for client setup and [Validate Your Agent](/docs/building/verification/validate-your-agent) for the storyboard workflow.
Expand Down
2 changes: 1 addition & 1 deletion docs/media-buy/product-discovery/proposal-negotiation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -542,7 +542,7 @@ The deterministic training profiles expose the exact `3.2-rc.1` proposal-negotia
| Constrained seller | `/sales/profiles/constrained-seller/mcp` | USD floors, product conflicts, and at most two available alternatives |
| Finalization failure | `/sales/profiles/finalization-failure/mcp` | `hold_unavailable` plus `batch_aborted` siblings with no committed successors |

Pin the release candidate exactly on every call. A stable `3.2` selector intentionally negotiates to the seller's stable compatibility response instead of silently opting into prerelease behavior. SDK `14.0.0-rc.35` accepts `wireAdcpVersion: "3.2-rc.1"` on its single- and multi-agent client configuration; raw calls remain useful for inspecting the exact envelope as below.
Pin the release candidate exactly on every call. A stable `3.2` selector intentionally negotiates to the seller's stable compatibility response instead of silently opting into prerelease behavior. SDK `14.0.0-rc.36` accepts `wireAdcpVersion: "3.2-rc.1"` on its single- and multi-agent client configuration. That option sets the wire envelope only: RC.36 embeds `3.2.0-rc.2`, so request and response validation still runs against that bundle, and its `adcpVersion` option will not take `3.2-rc.1`. Raw calls remain useful for inspecting the exact envelope as below.

### Try the lifecycle with Addie or Sage

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
23 changes: 11 additions & 12 deletions docs/media-buy/task-reference/get_reporting_status.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,12 @@ description: "Check Reliable Reporting health, enumerate expected periods and re
---

<Warning>
**Reliable Reporting 1.0 is published through `3.2.0-rc.2` and remains
experimental.** RC.2 publishes the opt-in consumer-status sync and readback.
Sellers implementing that extension advertise `consumer_status_task`; it becomes
required Core only in the next eligible minor after the notice window. Sellers declare
**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 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>

Expand All @@ -18,9 +20,9 @@ usable. It does not replace [`get_media_buy_delivery`](/docs/media-buy/task-refe
as the reporting-data API.

{/* The stable /schemas/v3 alias does not expose this prerelease-only task yet. */}
**Request schema:** [`get-reporting-status-request.json`](https://adcontextprotocol.org/schemas/3.2.0-rc.2/media-buy/get-reporting-status-request.json)
**Request schema:** [`get-reporting-status-request.json`](https://adcontextprotocol.org/schemas/3.2.0-rc.3/media-buy/get-reporting-status-request.json)

**Response schema:** [`get-reporting-status-response.json`](https://adcontextprotocol.org/schemas/3.2.0-rc.2/media-buy/get-reporting-status-response.json)
**Response schema:** [`get-reporting-status-response.json`](https://adcontextprotocol.org/schemas/3.2.0-rc.3/media-buy/get-reporting-status-response.json)

<Note>
**What landed when.** RC.0 supports the `summary`, `periods`, and `revision`
Expand All @@ -29,14 +31,11 @@ pagination. RC.1 adds incremental `changes_after` repair and its checkpoint,
post-official `adjustments[]` and `adjustment_receipts[]`, and their
correction/reconciliation semantics. `3.2.0-rc.2` adds `consumer_statuses[]` for
sellers advertising `consumer_status_task` and includes those immutable records
in flat pagination and `changes_after` checkpoints. Do not infer a later
tier's additions from an earlier baseline.

Not in any published bundle yet — these ship in the next prerelease:
in flat pagination and `changes_after` checkpoints. `3.2.0-rc.3` adds
`obligation_counts.consumer_status_pending`, issue `opened_at` / `issue_state` /
`external_ref`, and the `consumer_mismatch_escalation_seconds` and
`operations_contact` capability fields. Validate those against the development
bundle served from `/schemas/latest/` rather than the rc.2 pin above.
`operations_contact` capability fields. Do not infer a later tier's additions
from an earlier baseline.
</Note>

## Views
Expand Down
Loading