Agent Hub
Commerce Protocols
How Agents Buy From BoxNCase
Three protocols for programmatic commerce. Discover products, create checkouts, and process payments — all without a browser.
Agent Checkout Flow
AI Agent BoxNCase MCP BoxNCase Checkout
│ │ │
│ search_products │ │
│ ─────────────────────► │ │
│ ◄─── product results │ │
│ │ │
│ get_product │ │
│ ─────────────────────► │ │
│ ◄─── full details │ │
│ │ │
│ Create checkout (UCP/ACP) │
│ ──────────────────────────────────────────────► │
│ ◄────────────────── continue_url ───────────── │
│ │ │
│ Redirect buyer ──────────────────────────────► │
│ │ checkout.boxncase.com │
│ │ (BoxNCase native) │
│ ◄──────────────── order confirmation ────────── │Universal Commerce Protocol
UCP/.well-known/ucpOpen standard for AI agent commerce. Agents discover products via Catalog MCP, create checkout sessions, and redirect buyers to BoxNCase's Saleor-powered checkout.
Catalog searchCheckout sessionsCart permalinksNative checkout
Agentic Commerce Protocol
ACP/.well-known/acp.jsonOpen spec by OpenAI and Stripe for programmatic checkout. Sellers expose checkout endpoints, agents render UI, collect payment tokens, and complete purchases.
REST + MCP transportsCheckout + cartsUSD currencyAgent-driven purchase flow
x402 HTTP Payments
x402/api/x402Agent-native payments on Base mainnet. Protected endpoints return HTTP 402 with payment requirements. x402-compatible agents automatically fulfill payments to access data.
Base L2 mainnet$0.001 per requestAutomatic fulfillmentEVM wallet payments