Developer building on open commerce protocol — UCP SDK architecture

UCP 1.2 Release: What Changed for Agent Commerce

Last Updated: November 10, 2026 • Autonomous Agentic Commerce Spec v2026-08-25

Production Validated

The UCP 1.2 specification release addresses feedback from enterprise deployments that identified gaps in multi-agent coordination, spend control granularity, and fulfillment event coverage. This post covers the changes that affect production deployments and what implementation work they require. See also: How to Identify AI Agent Traffic in Google Analytics 4. See also: 2026 UCP Compliance and Risk Checklist for Merchants. See also: UCP vs ACP vs MCP. For related reading, see WebMCP Is Here. For related reading, see The Invisible Middlemen Getting Disrupted First by Agentic Commerce. For related reading, see The Trust Problem Is Not Technical. It Is Institutional..

Multi-Agent Coordination: The Authorization Delegation Model

Protocol Subsystem UCP 1.0 / 1.1 Baseline UCP 1.2 Updated Specification Breaking Change Status Migration Requirement Security / Speed Gain
Message Signing Optional SHA-256 header digest. Mandatory RFC 9421 HTTP Signatures with ES256 curve. Breaking for unsigned legacy clients. Upgrade client SDK to v2.4+. Guarantees 100% cryptographic non-repudiation.
Identity Verification DNS TXT and reverse IP lookups. W3C Decentralized Identifiers (DIDs) in manifest. Deprecated legacy network checks. Update manifest DID document. Eliminates IP spoofing and DNS cache poisoning risks.
Inventory Webhooks Hourly batch catalog feed polling. Sub-minute real-time Google Content API v2.1 webhooks. Non-breaking enhancement. Configure real-time webhook listener. Reduces out-of-stock cancellations by 94%.
Settlement Payload Variable JSON format per gateway. Standardized FIDO AP2 client assertion schema. Breaking for custom token parsers. Implement standardized AP2 schema. Enables zero-friction cross-rail clearing across card networks.
Price Floor Engine Static minimum price database field. WebAssembly edge rules evaluating dynamic pricing tiers. Non-breaking backward compatible. Deploy WASM rule file to edge CDN. Sub-5ms complex algorithmic B2B pricing evaluation.

One of the most significant changes in 1.2 is formal support for authorization delegation. In complex enterprise agent deployments, a primary orchestrator agent may spin up sub-agents to handle specific tasks — one agent for price discovery, one for checkout, one for post-purchase tracking. Under UCP 1.0 and 1.1, each of these sub-agents required separate authorization scopes, creating management overhead. UCP 1.2 introduces a delegation model: the primary agent can delegate a subset of its authorization scope to a sub-agent without requiring human re-authorization for each delegation, as long as the delegated scope is strictly narrower than the primary scope.

Spend Control Granularity Improvements

UCP 1.1 supported spend limits at the agent level and category level. Deployments running complex procurement workflows needed finer granularity — per-merchant limits, per-order limits, and time-bounded limits (daily, weekly, monthly). UCP 1.2 adds all three, giving finance teams the precise control they need to deploy agents across procurement workflows without creating open-ended spending exposure.

New Fulfillment Event Types

Based on merchant feedback, UCP 1.2 adds three new fulfillment event types to the webhook schema: FULFILLMENT_DELAYED (with estimated new delivery date), ITEM_SUBSTITUTED (when a merchant substitutes an equivalent item due to availability), and PARTIAL_SHIPMENT_CREATED (for orders split across multiple shipments). These events were previously handled as custom extensions by merchants that needed them; standardizing them enables consistent handling across all UCP-certified agents.

Migration Path from 1.1 to 1.2

UCP 1.1 implementations are backward compatible with 1.2 in all cases. The new features require explicit opt-in at the merchant and agent configuration level. Merchants that do not need delegation or the new spend control granularity can continue using their 1.1 configuration without any changes. The new fulfillment event types will simply not be emitted by 1.1-configured merchants.

Frequently Asked Questions

What are the breaking architectural changes introduced in UCP 1.2?

The two breaking changes are the mandate for RFC 9421 HTTP Message Signatures with ES256 on all POST/PUT requests and the standardization of FIDO AP2 client assertion payloads for settlement.

Why were DNS-based agent verification checks removed from the UCP specification?

DNS checks introduced 200–500ms network latency and were vulnerable to DNS spoofing and shared cloud IP false-positives; cryptographic public-key signatures provide instantaneous, tamper-proof verification.

How do developers upgrade an existing UCP 1.0 implementation to version 1.2?

Update dependencies to @ucp-protocol/sdk@^2.4, re-generate your keypair using ES256, and register your public key in your published /.well-known/ucp manifest.


by

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *