Help us improve
Share bugs, ideas, or general feedback.
From acp-agentic-commerce
Implements ACP capability negotiation for dynamic discovery of shared capabilities, extensions, payment handlers, and interventions between agents and merchants.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin acp-agentic-commerceHow this skill is triggered — by the user, by Claude, or both
Slash command
/acp-agentic-commerce:acp-capability-negotiationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fetch live docs**:
Implements ACP payment handlers for tokenized cards via Stripe SPT, seller-backed methods (gift cards, points, store credit), and negotiation protocols. Use when adding pluggable payment methods.
Implements AP2 payment protocol as A2A extension in multi-agent systems: mandates DataParts in messages, Agent Cards for capabilities, payment task flows, and inter-agent communication.
Implements UCP AP2 Mandates for autonomous agent payments using SD-JWT credentials, JWS merchant signatures, and Agent Payments Protocol in 7-step flow with security lock.
Share bugs, ideas, or general feedback.
Fetch live docs:
site:github.com agentic-commerce-protocol rfcs capability_negotiation for the capability negotiation RFChttps://developers.openai.com/commerce/specs/checkout/ for how capabilities appear in checkout requests/responsessite:github.com agentic-commerce-protocol spec json-schema capabilities for the capabilities JSON schemaACP agents and merchants may support different features. Capability negotiation allows them to dynamically discover what they both support, so the session uses only mutually available features.
create request, the agent includes a capabilities object listing what it supportsThe capabilities object contains:
capabilities — Major features (checkout, orders, etc.)extensions[] — Optional add-ons (discount, intent traces, affiliate attribution)payment_handlers[] — Supported payment methodsinterventions — Structured object with sub-fields: supported, required, enforcement, display_context, redirect_context, max_redirects, max_interaction_depthExtensions declare a parent capability via extends. If the parent capability is not in the negotiated intersection, the extension is automatically pruned — no extra logic needed.
Interventions are actions that require human involvement. They are represented as a structured object (not a flat array) with sub-fields including supported, required, enforcement, display_context, redirect_context, max_redirects, and max_interaction_depth.
Intervention types include:
The agent advertises which interventions it can handle. If the merchant requires an intervention the agent can't handle, the checkout may not proceed.
discount@2026-01-27)Fetch the capability negotiation RFC for the exact capabilities object schema, extension pruning rules, and negotiation semantics before implementing.