Pizza Meets Champagne: The Match-Moment in Action (and What We Learned)

This morning I asked an AI assistant how to make pizza. One question later we were on drink pairings. One more question later the agent searched Nexbid…

This morning I asked an AI assistant how to make pizza. One question later we were on drink pairings. One more question later the agent searched Nexbid and found an excellent champagne — BRUYEN Sélection Meunier Brut Nature from The Champagne Store, one of our active advertisers. I wanted a case, six bottles, CHF 216. And then the journey got stuck. What worked The agent did exactly what Nexbid promises: discovery through context, not through search. Nobody typed "champagne". The conversation was about pizza. The agent inferred from the context (Italian food, fatty cheese, acidic tomato) that the right pairing was Blanc de Noirs, Brut Nature — and found a matching, factually correct hit in our inventory. That is the match-moment: publisher content (in this case Betty Bossi's pizza recipe as the conversational anchor) × advertiser product (BRUYEN) × user intent (buy a case) → snippet → cart. Without the user having to know a shop, google a brand, or browse a product database. Where it broke The agent had two paths: prefill_link — a cart URL into the shop. Worked technically, but only deep-linked to the product page, not into the cart. Choosing six bottles was on me. wallet_pay — the actual agentic flow: I authorize once, the agent pays. The tool accepted the call, status: wallet_pending. And then silence. No link to authorize. No path to setup. The intent expired after one hour. This is not "the agent is too dumb". This is Nexbid having a feature that looked like it worked but wasn't wired through end-to-end. Five minutes with Claude.ai exposed it. The same test would have exposed it any day before. What we changed Within the next few hours: 1. Magic-link authorization When an agent now calls wallet_pay, it gets back an authorization_url — a single-use link the agent presents to the user. The user clicks it, signs in (Clerk), sees the intent (what's being bought, from whom, how much) and approves with one click. Valid for one hour, tamper-proof via single-use token. 2. Mandate setup that works Before today the wallet UI had an API contract bug (snake_case vs camelCase, missing fields). Nobody could even create a mandate. Fixed. On nexbid.dev/dashboard/wallet a user sets up a wallet in 30 seconds — budget, validity, scope (all shops or specific). Daily limit is auto-computed. 3. Cart prefill that covers more shops buildCartLink auto-detects Shopify, and can also …

Author

Holger von Ellerts

Published

2026-04-28

Topics

Agentic, Protocol Commerce, Agent Discovery