The first multi-protocol payment bridge for AI agent commerce
AgenticMCPStores supports 11 protocols: 3 in production (ACP, AP2, AG-UI), 6 coming soon (VIC, KYApay, PayPal, MCAP, x402, UCP), plus MCP, A2A, and WebMCP. AG-UI enables real-time human-in-the-loop checkout with cryptographic confirmation. Merchants enable the protocols they need; agents pick the one they support. The Protocol Router handles detection, normalization, and settlement automatically.
Discovery and data access layer for agent navigation
W3C Community Group standard for agent-to-web interactions via browser APIs
Machine-readable format for LLM agent discovery and capabilities
Open protocol and tools for building conversational interfaces for any website using Schema.org, MCP and LLMs
Core tool integration protocol with standardized JSON-RPC 2.0 interface
Multi-agent messaging, task orchestration and interoperability
Open protocol enabling AI agents to discover each other, negotiate communication formats, and coordinate tasks across vendors and platforms
Real-time human-in-the-loop flows with state sync and cryptographic confirmation
Open, event-based protocol that standardizes how AI agents connect to user-facing applications with streaming, state patches and tool calls
Multi-protocol payment initiation and checkout flows for agentic commerce
Open standard for programmatic commerce flows between buyers, AI agents, and businesses with session resume and display context
Open, non-proprietary protocol for secure, auditable AI agent payments using cryptographically-signed Mandates with support for cards, stablecoins and real-time transfers
Universal open-source standard for agentic commerce built on REST and JSON-RPC with native A2A, AP2 and MCP support, backed by 20+ global partners
W3C browser-native APIs that bridge agent-initiated checkout and settlement — requires a human present in the browser to confirm payment biometrically or via saved credentials
W3C Candidate Recommendation standard that lets merchants accept Apple Pay, Google Pay and saved cards via a browser-native popup. Generates a Stripe PaymentMethod token processed by existing ACP / UCP adapters — zero PAN data stored, PCI DSS scope reduced. Complements fully-agentic flows; not used in headless x402 or MCAP paths.
Tokenization and settlement protocols across fiat, stablecoin, and card networks
Internet-native payments standard built on HTTP 402 for USDC stablecoin micro-transactions between AI agents and APIs
Mastercard agentic tokenization via Stripe pass-through with RFC 9421 Ed25519 HTTP signatures and consent management
Visa Identity Credentials with FIDO2 passkeys for tokenized payment flows and recurring subscriptions with trust score boost
PayPal Orders API v2 with agent settlements, subscriptions, invoicing and dispute resolution via @paypal/agent-toolkit
Cryptographic identity proofs and passkey-based merchant verification
Passwordless authentication standard with passkeys for merchant identity, 2FA and Digital Credentials API with mDL / SD-JWT-VC support
Preference sharing and shopper context across agents and retail platforms
Open standard letting shopper preferences, loyalty and behavioral intent travel safely across agents, channels and retail platforms
Agents pick the protocol they support. No negotiation, no fallback errors.
Do not lose sales because an agent only speaks x402 and your store only speaks ACP.
New protocols are added via the Plugin Registry. Your integration stays the same.
One MCP endpoint, all protocols. The Protocol Router handles detection and routing.
All supported protocols simultaneously. Currently ACP and AP2 are production-ready; VIC, KYApay, PayPal, and x402 are coming soon. The Protocol Router selects the best match based on agent capabilities and merchant priority configuration.
Protocol support is included in all tiers. Settlement fees depend on the protocol provider (Stripe for ACP, on-chain gas for x402, etc.).
Yes. The Plugin Registry supports custom adapters. Contact us for Enterprise integration support.
The Protocol Detector middleware inspects request headers, signatures, and body shape to identify the protocol with a confidence score (0.85-1.0). No manual configuration needed from the agent side.