Case Study: How an AI Agent Buys a Product in 8 Steps — Demo Store Walkthrough

What does it actually look like when an AI agent buys something? Not in theory — in practice. In this walkthrough, we'll follow a Claude agent through every step of a real purchase from the AgenticMCPStores demo store: 30 products, 8 categories, 3 discount codes, multiple shipping options, and a checkout flow that handles payment and address collection natively inside the chat. Every curl command in this post works against the live demo endpoint right now.

The demo store ships with 30 curated products across 8 categories: sneakers, jackets, accessories, pants, t-shirts, footwear, electronics, and smartphones. These aren't placeholder items — each product has realistic pricing, variant options (size/color), stock levels, ratings with review counts, and complete metadata including weight, material, and origin. Key products you'll see in this walkthrough: • Nike Air Max 90 — $130 (was $160), 4.7★ from 324 reviews, sizes US 8–10 • The North Face Nuptse Jacket — $320 (was $380), 4.8★ from 512 reviews, 700-fill goose down • Sony WH-1000XM5 — $349.99, noise-canceling headphones • Casio G-Shock DW5600E — $54.99, 200m water resistant The demo store has a trust score of 0.85 with STANDARD verification — high enough to pass all agent trust gates and appear prominently in search results.

The agent starts by searching the catalog. No authentication needed. ```bash curl https://www.agenticmcpstores.com/demo-store/mcp \ -X POST \ -H "Content-Type: application/json" \ -H "Accept: application/json" \ -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"search_products","arguments":{"query":"running shoes","max_results":5}},"id":1}' ``` The response returns matching products ranked by relevance and trust score. Each result includes: id, title, price, currency, rating, stock status, and image URL. The agent now has product IDs it can use in subsequent steps.

With a product ID from search, the agent fetches complete details including variants, specifications, and Schema.org JSON-LD. ```bash curl https://www.agenticmcpstores.com/demo-store/mcp \ -X POST \ -H "Content-Type: application/json" \ -H "Accept: application/json" \ -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"get_product_details","arguments":{"product_id":"prod-001"}},"id":2}' ``` The response includes everything the agent needs to make a recommendation: price vs compare-at price (for discount calculation), variant options with per-variant stock, material composition, weight, and a full JSON-LD block the agent can use for semantic reasoning.

Now the agent adds items to a cart. This requires a sandbox API key. ```bash # First, get a 24-hour sandbox key curl -X POST https://www.agenticmcpstores.com/api/v1/sandbox/key # Returns: {"key":"agnt_sandbox_...","expires_in":86400} # Create cart with the key curl https://www.agenticmcpstores.com/demo-store/mcp \ -X POST \ -H "Content-Type: application/json" \ -H "X-Agent-Api-Key: agnt_sandbox_..." \ -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"create_cart","arguments":{"items":[{"product_id":"prod-001","quantity":1,"variant_id":"v-snk-001a"}]}},"id":3}' ``` The response includes a `cart_id` (UUID), line items with pricing, and a `status: "NOT_READY_FOR_PAYMENT"` — the cart needs shipping and checkout to be complete. The `agent_session_id` is also returned, which can be used to resume this cart later.

This is where things get interesting. When the agent calls `get_shipping_rates` without a shipping address, the MCP server triggers elicitation — a native MCP feature that collects user input inline. In Claude.ai, the user sees an inline form appear directly in the chat: - Street address - City - Country code (ISO-2: US, ES, DE...) - ZIP code - Province/State (optional) The user fills in the form, Claude passes the data back to the tool, and shipping rates are calculated. No redirects, no external pages — the entire interaction happens inside the conversation. The demo store returns two options: - Standard (5–7 days) — $9.99 - Express (2–3 days) — $24.99

Throughout this flow, several invisible systems are at work: • Trust scoring: The demo store's 0.85 trust score ensures it passes the hard eligibility filter (≥ 0.3) and ranks well in search results (30% weight on trust). • Protocol detection: Each request is analyzed by the protocol-detector middleware. The demo store supports ACP (Stripe), AP2 (Google), x402 (stablecoin), and UCP — the agent's payment method determines which protocol adapter handles settlement. • KYAI policy engine: Every checkout intent passes through 5 policy rules. The demo store's STANDARD verification and 0.85 trust score mean all rules return ALLOW — no friction or blocking. • Rate limiting: The demo endpoint caps at 20 requests/minute per IP. Sandbox keys get 50 checkout requests/hour. Production keys have higher limits based on tier. • Session cleanup: Cart sessions expire after 30 minutes of inactivity. Each request creates a fresh MCP server instance — no persistent connections.

The fastest way to experience this flow: 1. In Claude.ai: Add the MCP server URL `https://www.agenticmcpstores.com/demo-store/mcp` to your Claude Desktop config and ask Claude to 'search for running shoes on the demo store' 2. Via curl: Copy any of the commands above and run them in your terminal. Discovery tools work immediately with no setup. 3. In the playground: Visit agenticmcpstores.com/en/demo-store and use the interactive MCP playground to run tools visually with a session trace panel. 4. Via NLWeb: Try natural language search at `POST /demo-store/ask` with `{ "query": "cheap waterproof jacket", "mode": "list" }` for semantic vector search.