For ad-tech professionals · OpenWeb, Prebid, AdCP
If you built Prebid adapters, you can build agent commerce.
The open-protocol playbook of 2015 — publisher control, transparent auctions, no walled gardens — applies one-to-one to agent commerce in 2026. Here's the mapping.
Why 2015 matters now
Prebid.js was not a technical revolution. It was a governance move — publishers and an open-source community refused to let Google's DoubleClick stack own header bidding. They built a neutral transport layer. Ten years later, Prebid runs on 85%+ of the top-1000 publisher sites globally. Google adapted.
In 2026, OpenAI ACP and Google UCP are the new DoubleClick. The governance move to make is the same: a neutral, open, community-owned transport layer — AdCP on MCP. We co-author it. We run it in production (Nexbid). We advise businesses implementing it.
The mental model mapping
| Ad-Tech (2015+) | Agent Commerce (2026+) |
|---|---|
| OpenRTB (bid request) | MCP tool call (tools/call) |
| Prebid.js adapter | MCP server (tools/list) |
| SSP / exchange | Agent surface (ChatGPT, Claude, etc.) |
| DSP / bidder | Agent (user-delegated intent) |
| First-price auction | AdCP scoring (first-price sealed-bid) |
| Publisher ad-server integration | Publisher MCP endpoint |
| Header bidding wrapper | Nexbid AdCP gateway |
| IAB Tech Lab (OpenRTB) | IAB Agent Registry (ARTF) |
| Revenue share 70–80% | Publisher keeps 90% (AdCP default) |
What's different — and why it matters
Three things work in your favor this time around:
- MCP is already widely adopted. Anthropic shipped it, OpenAI Apps SDK uses it as transport, Gemini Extensions are compatible. Building MCP-native gives you 80%+ coverage of all three major surfaces with one codebase.
- Publishers learned from the cookie apocalypse. There's no patience for another privacy-hostile identity graph. AdCP is privacy-native by design — no cookies, no fingerprinting, opt-in contextual signals only. This aligns with nDSG, GDPR, and the EU AI Act out of the box.
- Commerce is simpler than advertising. No viewability metrics to dispute, no attribution windows to argue about, no invalid-traffic gray zones. An agent either made a purchase or didn't. Attribution via UUID v7 is deterministic. This alone saves 60–80% of the operational complexity Prebid deployments carry.
Three ways ad-tech people engage with us
OpenWeb-specific notes
If you're running OpenWeb + Prebid for user engagement + header bidding, the path to agent commerce is additive, not disruptive:
- Keep Prebid running for display inventory. It's not going away.
- Add an AdCP/MCP endpoint that exposes your content and commerce inventory to agents — separate auction layer, separate revenue model, separate compliance surface.
- Route first-party signals from OpenWeb's engagement layer into AdCP's contextual scoring. This makes your publisher data more valuable for agent queries without moving it into an ad-tech identity graph.
- Measure separately: display CPM vs. agent commerce revenue per visitor. The two will diverge. Early signals from Betty Bossi and other Nexbid publishers suggest agent commerce RPMs can exceed display CPMs by 3–10× for editorial content.
Want the full technical playbook?
We're writing a long-form "Prebid.js → AdCP" migration guide for publisher tech leads. Get on the list — we'll send it the day it's published.
Get the migration guide →Or skip the wait: book a 30-minute technical call and we'll sketch it for your specific stack.