ShopBridge & UCP Framework Hub
Welcome to ShopBridge
ShopBridge demonstrates how an AI shopping agent can browse, secure mandates, and finalize transactions on behalf of users securely and seamlessly without the friction of traditional web wrappers.
Navigate using the **dark sidebar** on the left to inspect detailed specifications, execute API call simulations, test security handshakes, and debug sandbox features.
Architecture Overview
UCP serves as an abstraction layer separating the AI agent platform from merchant catalog and ordering systems. Transactions flow across structured transport profiles, validating capabilities through intersection rules, securing authorization cryptographically, and publishing orders cleanly.
AGENT UCP BRIDGE MERCHANT APIS
Get Started Instantly
For an accelerated walkthrough of every single section working in concert:
UCP Profiles Discovery
UCP onboarding begins with standard profile JSON objects residing at well-known endpoints. This establishes capabilities, supported payment gateways, keys, and endpoint locations.
NovaMart (Merchant) Profile
Provides endpoint paths for REST, MCP (JSON-RPC tools), App-to-App (A2A), and Embedded Web Checkout protocols, alongside payment specs.
ShopBridge Agent Profile
Advertises capabilities supporting programmatic checkout, fulfillment resolution, cart state syncing, and OAuth credential scopes.
Capability Negotiation Engine
This panel displays the execution of the UCP Intersection Algorithm. It resolves mutual capabilities, chooses mutual semantic versions, and prunes orphaned child capabilities.
Intersection Logic Checklist
- Compute baseline intersection of matching names.
- Filter by mutual supported versions (highest mutual selected).
- Prune child extensions missing required root parents.
Catalog Capability
The agent queries product indices programmatically. Test catalog filters or drill down to see UCP format properties in minor units (cents).
Cart Capability
UCP Carts represent stateful checkout prep containers. Try adding products, adjusting quantities, and testing discount coupons.
Active Cart
Checkout Lifecycle Stepper
Identity Linking
This implements `dev.ucp.common.identity_linking`. AI agents securely bind client context to merchant accounts using OAuth 2.0 authorization rules.
Discovery Details
The authorization endpoints are advertised inside the /.well-known directory, establishing client secret formats and token grant mechanics.
Identity Connection State
Order Lifecycles & Webhooks
Post-checkout webhooks broadcast order modifications. Simulate carrier operations and returns using the controls below.
Timeline Simulator
Payment Handler Playground
UCP abstracts tokenization. Inspect mutual card configurations, mandate rules, and scope topologies.
Available Instrument Resolution (Intersection Algorithm)
Merchant Card Config
["VISA", "MASTERCARD", "AMEX", "DISCOVER"]
Agent Platform Config
["VISA", "MASTERCARD", "JCB"]
3 Integration Scenarios
A. Digital Wallet / Google Pay
Merchant config references direct gateway keys. The platform requests, executes, and yields encrypted payloads.
B. Direct Tokenization (Visa/MC)
Demonstrates direct card entry and 3DS authorization challenges.
C. Autonomous AP2 Mandate Flow
Secures signed user mandates authorizing scheduled agent pull payments without continuous interaction.
AI Platform
No RAW Credentials (Out of Scope)
PSP Gateway
Vaults Cards (Direct Scope)
Merchant App
Consumes Secure Tokens Only
Multi-Transport Configurations
UCP payloads remain constant across physical network layers. Inspect identical Checkout operations mapped to REST, MCP, A2A, and Embedded formats.
Error Simulator & Fallbacks
UCP specifies precise error payloads to instruct automated agents on fallback procedures. Test error handling parameters here.
Trigger Sandbox Errors
Agent continue_url Fallback Flow
When automated negotiations fail, UCP allows graceful exit by directing users to a secure web form.
UCP Security & Signals
UCP Signals collect context (IP, User Agent, custom metadata, and cryptographic device attestations) to enable silent fraud checks.
Signals Inspector
Namespace Governance Map
| Prefix Namespace | governing body |
|---|---|
| dev.ucp.* | ucp.dev Core WG |
| com.{vendor}.* | Vendor Private Specs |
| org.{org}.* | Organization Custom |
UCP endpoints require authorization headers conforming to the HTTP Message Signatures spec. Allows permissionless verification via keys advertised in profiles.
Signature: ucp-sig=:MEQCID1vXfP4...:
Versioning & Compatibility
UCP utilizes chronological versioning strings (e.g. YYYY-MM-DD). Platforms negotiate version parameters during onboarding handshakes.
Interactive Version Handshake
Select Agent Platform Profile Version
Backwards Compatibility Matrix
| Safe (Non-Breaking) Changes | Breaking (Renegotiate) |
|---|---|
| Adding Optional parameters | Renaming Capability Names |
| Adding Payment Handlers | Changing Minor Unit Scale |
| New API Services (Transports) | Removing Required Keys |