Skip to main content

AdCP 3.3 prerelease program

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 prerelease follows the same order as 3.2: the protocol first, then the SDKs.

Prerelease status

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). GA follows the first release candidate that meets every one of the GA criteria in #8600: SDK support for the latest prerelease, green storyboards, the closed-schema triage (#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. 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). Three features that shipped in the betas are withdrawn after beta.1, and the closed-schema triage 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. No published SDK supports rc.0 yet: rc.0 is SDK-backed once new SDK prereleases bundle it (SDK guidance).

Know which version string to use

The artifact version, wire pin, and documentation selector are related but not interchangeable: 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. The 3.3-beta documentation selector stays at beta.5, and 3.3-rc advances with each release candidate.

Test a prerelease without an SDK

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/3.3.0-rc.0/ path:
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;
  • compliance/: storyboards, test kits, vectors, and runner contracts;
  • skills/: role guidance for coding agents;
  • openapi/: published OpenAPI artifacts.
Verify the Sigstore signature before using the bundle as a build input. See Verifying protocol tarballs for the certificate-identity and issuer checks. 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-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. 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:
At the preview pin, /sales/mcp serves the experimental 3.3 surfaces the training agent implements:
  • account requests (account.requests): request_account, and account_requests on list_accounts;
  • the caller’s authorization, with authorized_at and regranted_at, and revision on each list_accounts account;
  • principal-level reporting subscriptions (media_buy.reporting_subscriptions): the reporting_subscriptions section of sync_principal and get_principal, and subscription_coverage on get_reporting_status;
  • the reporting_subscription_probe controller scenario, which revokes, reduces, and restores grants and advances a per-caller sandbox clock;
  • collection cards (media_buy.collection_cards): include_collections on get_products, list_products, request_proposals and refine_proposals, with images, samples, links, talent brand_ref and follower counts on the CreatorLoop creator channels;
  • the collection catalog (media_buy.collection_catalog): list_collections, and the collection_card.* and collection_catalog.bulk_change webhooks registered through sync_accounts;
  • the seed_collection controller scenario, which changes the caller’s cards (a sample, a removal, a follower sweep) so the card webhooks fire;
  • inventory holds (Hold policy): hold_policy on products and drafts (media_buy.hold_policy), committed proposals with hold_placed_at, ranked holds with hold_rank (media_buy.hold_ranking), per-installment holds (media_buy.installment_holds), extend_hold (media_buy.hold_extension), and the force_hold_unavailable controller scenario.
At the same pin, /brand/mcp returns collections on get_brand_identity for the creators (brand.collection_links). Holds are kept per caller and timed by the caller’s sandbox clock, so two accounts that hold the same slot are queued at positions 1 and 2. These products carry hold policies: Other products take the default: a hold that never contends. tools/list includes request_account and list_collections only when the listing is pinned to the preview (params._meta.adcp_version, as @adcp/sdk sends it). 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 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 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

An SDK support claim must name all of the following:
  • exact SDK package version;
  • exact AdCP prerelease bundle used to generate or load schemas;
  • supported roles and transports;
  • known unsupported or raw-only surfaces;
  • install command and one tested validation command.
The SDK compatibility matrix lives in 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. 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

rc.0. TypeScript and Python prereleases that adopt 3.3.0-rc.0 follow within days of the cut; see 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 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. 10.0.0b15 reads the input member of an AdCP A2A profile 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 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 for any later support statement. 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 is the SDK matrix, and it can lag the npm dist-tag.

SDK convergence

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 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 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). 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 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 lists every field, and what to do if you built from a beta. In review, not in rc.0. #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

Three features shipped in 3.3.0-beta.1 and are not part of 3.3. They leave the protocol after beta.1. All three add terms to commercial_terms, which is held closed until 4.0 (adcp#8501). They are planned for 4.0, where commercial_terms gets a declared extension point with must-understand. The migration guide lists every surface removed, and Planned for 4.0 keeps the designs.

Required integration evidence

Retain the exact protocol bundle, SDK package versions, capability responses, redacted requests and responses, task IDs, and account and MediaBuy identifiers for each run.
  1. Account lifecycle. Call a discovery task (get_products or list_products) with a buyer-declared natural key that was never provisioned. The seller returns ACCOUNT_NOT_FOUND (a seller that provisions lazily instead of exposing sync_accounts may answer without creating the account), and list_accounts shows no new account. Then provision, with sync_accounts or the seller’s lazy path on a provisioning task, and repeat the read.
  2. Signed traffic. Send a signed request and receive a signed webhook between two agents that publish identity.brand_json_url. Confirm agent resolution by canonical URL, and that a pinned key missing from the agent’s JWKS is rejected. Against a seller that lists an operation in required_for and a2a_invocation_skill in request_signing.operation_sources, confirm an unsigned A2A call to that operation is rejected. A 3.3 seller that lists the operation in required_for without the marker must reject it too; the marker advertises enforcement, it does not enable it.
  3. Catalog intake. For a seller that declares media_buy.features.catalog_ingestion, confirm sync_catalogs rejects an unlisted catalog type, mode, or feed format, and an explicit content_id_type outside a declared supported_content_id_types, with UNSUPPORTED_FEATURE before mutation, including on a dry run, and reports one item_issues entry per item on terminal results and discovery reads under per_item reporting.
  4. Delivery webhooks. Register a reporting_webhook with an operation_id and confirm every media_buy_delivery webhook echoes it verbatim. Register one without it and confirm the seller sends no delivery webhooks to it.
  5. End to end. Run one buyer and seller lifecycle through purchase, creative assignment, and a delivery readback.

What may still change

The 3.3.0 milestone is the live scope record for work that may still land before GA. Use these maintained GitHub views as the live record: 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-16 (four, not counting the GA tracking issue), 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 and the release notes 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 and open pull requests and drafts.

Decisions

Four records document surfaces merged for beta.0 and are accepted (decided 2026-10-30): DR-0027 (error.mutation_outcome), DR-0028 (sales-fixed-rate), DR-0029 (delivery projection), and DR-0030 (media-buy lineage). sales-fixed-rate is promoted from preview to stable in beta.5 (#8445).

Open 3.3.0 milestone issues

Closed since beta.5: match keys (#8375), which shipped in beta.5, and over-specified URL patterns (#8398), loosened in rc.0 by #8792. Also closed: Reliable Reporting push without buyer secrets (#8149, merged as #8793), the three video containers (#8107, merged as #8668), and inline submitted branches aligned with their published status files (#8856, merged as #8934), origin-only authorized_agents matching in the validator and registry (#8943, merged as #9011), and how signing_keys pins combine across matching entries (#9016, merged as #9017), and the audience_buy_flow member-push gate (#8998, merged as #9013), all in rc.0. Price adjustments (#7659) moved to the 4.0 milestone: the experimental price_adjustments table (#7955) shipped in the betas and leaves 3.3 with the triage.

Moved out of 3.3 since beta.3

These were open in the 3.3.0 milestone at beta.3 and have since moved, so they are not part of 3.3: #8010, #5683, and #8009 to 4.0, and the rest to 3.4.0. “Merged so far” names the slice that already shipped in 3.3. The issues closed since beta.3 (#8543, #7812, #8092, #8182, and #8181) shipped in the betas and are covered in What’s new. Also open, without a 3.3 milestone issue: #7958 composable delivery breakdowns and #7957 metric aggregation semantics (both drafts; their issues moved to 3.4.0), and #8346 signed creative addons (open; asks the working group to reconsider a 3.4 deferral, and WG approval is pending).

Known prerelease boundaries

  • Experimental surfaces retain their experimental-status contract. A 3.3 prerelease does not graduate them to stable. The surfaces new in 3.3 are listed in the release notes.
  • 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 prerelease issue:
  • protocol artifact version and wire pin;
  • SDK name and version, or raw wire;
  • buyer, seller, creative, signals, brand, measurement, or governance role;
  • transport and task name;
  • schema path or JSON Pointer involved;
  • expected and actual behavior;
  • minimal redacted payload and validation error;
  • whether the problem blocks interoperability on the checkpoint you tested.
Never include credentials, signed URLs, bearer tokens, private keys, or live customer payloads.