Nexbid Opens the Black Box: A Real Auction, Live
The public Match Moment demo now runs a real auction against real campaign budget - with an Ed25519-signed receipt anyone can verify themselves via curl.
Since April, Nexbid has said one sentence in practically every deck: the Match Moment — publisher content meets advertiser product meets user intent, producing an Enriched Snippet — is the actual event the entire marketplace runs on. Until now, you had to take Nexbid's word for it. As of today, you can look for yourself. The problem: a claim is not evidence Nexbid's positioning against OpenAI's ACP and Google's UCP rests on one sentence: open, community-governed, fully auditable — code, math, and operations. That is a strong claim for an open-source protocol with no central moderating authority. But a claim about auditability that a visitor cannot check themselves is worth exactly as much as any other marketing line. Until recently, that was exactly the state of the public demo page at /match-moment: it showed two fixed examples — champagne, Focuswater — with pre-scripted answers. No real visitor could ask their own question and watch a real auction run against real campaign budget. Behind that sat a second, deeper problem that only became visible once the page moved to real queries. The demo authenticated to /v1/discover only as Betty's publisher SDK (via HMAC) — never as an agent. The auction gate in the discovery endpoint checks a separate flag, agentVerified, set exclusively by a verified agent identity. Without that flag, a request would sail through full context detection and product search, but never reach the auction itself. The page showed "no winner in this run" regardless of match quality — not because nothing fit, but because the auction never started. The gate itself is not a bug; it is a deliberate safeguard. On May 26, 2026, a missing identity gate had let Betty's own GAM snippet calls — fired from end-user browsers, with no LLM agent involved at all — trigger 91 auctions and charge two advertiser budgets a combined CHF 95.20. Since then, agentVerified separates two structurally different products sharing one endpoint: publisher-SDK context targeting (free, no auction, 981,777 calls in the last seven days alone) and agent discovery with a real Match Moment (billable, verified agent identity required). The fix: a demo that is honest about what it is The correction is as unspectacular as an honest fix usually is: the demo endpoint now sends a real, registered agent identity ( nexbid-match-demo ) with its own API key, alongside — not instead of — Betty's publisher HMAC. Betty stays …
- Author
- Nexbid Engineering
- Published
- 2026-08-06
- Topics
- Agentic, Agent Discovery, Verification