Nexbid — Open Infrastructure for Agentic Commerce
Nexbid is a two-sided marketplace for the moment AI agents buy: publishers bring content, advertisers bring products and campaigns, Nexbid connects both sides through open protocols (AdCP, MCP) instead of a walled garden. Live since April 2026 with discovery API, MCP server, 19 transaction tools, x402 payment rail, and wallet-pay magic-link. Founding publisher Betty Bossi, founding advertisers FOCUSWATER and The Champagne.
Starting point — the match-moment goes agent-native
AI agents will handle between eight and fifteen percent of EU e-commerce in the coming years, a potential market of around 109 billion euros (sources: McKinsey, eMarketer, FAZ reporting March 2026). Anyone buying ad placements through classic header-bidding lanes today is buying for a world where humans click — not for a world where agents understand, evaluate, and act transactionally. Walled gardens like OpenAI ACP and the Google-led UCP coalition are defining the new lanes — proprietarily controlled, with platform rent. We built Nexbid because this market needs an open lane before it gets closed.
What Nexbid does — match-layer for two sides
Nexbid is not the ad slot, but the connective layer between the two sides — comparable to Stripe's role in payments: not the merchant, not the bank, but the protocol in between. Publishers (example: Betty Bossi with over 14,000 recipes) supply content and become MCP-queryable. Advertisers (example: FOCUSWATER, The Champagne) register product feed, audience, and bid. When an agent issues a contextual query — for instance 'pizza for dinner, what should I drink with it' — a first-price sealed-bid auction runs, weighted by bid (30 percent), semantic similarity (30 percent), content quality (20 percent), and context fit (20 percent). The result is an enriched snippet in the agent's output instead of a classic ad. 90 percent of the snippet value goes to the publisher, 10 percent platform fee to Nexbid.
Where we stand today — what runs in production
Discovery API, MCP server (19 tools for discovery, inventory, transaction, reporting, settlement) and wallet-pay magic-link are live on nexbid.dev. Settlement runs monthly via Stripe invoice. The x402 payment rail (HTTP 402 for crypto-native agents) is also live. Sprint 4 (May/June 2026) brings the customer portal phase 1 for advertiser self-serve, the brand-agent wizard, and the universal-purchase-mandate pilot with FOCUSWATER. The platform is MIT-licensed, the protocol repository (`nexbid-dev/protocol-commerce`) is public. Hosted in Vercel's Frankfurt region, database Neon Postgres in aws-eu-central-1 — server location Europe, Swiss nDSG compliant.
Practice proof for our advisory
When we run agent-commerce workshops for marketing and e-commerce leads, we speak not from slides but from operating a platform with real founding customers, real settlement, and real architecture decisions against walled-garden lanes. What we carry from Nexbid into our advisory: how a two-sided marketplace works technically, what open protocols (AdCP, MCP, x402) economically distinguish from the walled-garden model, how a 90-to-10 revenue share can be designed without platform lock-in, and which data architecture makes agent-native discovery possible in the first place. If you want to see Nexbid for yourself, nexbid.dev is the entry — the MCP server is openly connectable.