Monetize an AI chatbot without breaking the conversation

Why display formats fail in a chat app

• No viewport, no scroll depth, no page boundary. Every signal a display network was designed around is missing from a message thread.
• The best signal is unusable. A user typing "family SUV under $50K, third row, mostly city driving" has stated budget, body style, feature, and use case. Cookie-based targeting sees an anonymous ID.
• Trust is the asset. Creative built for a scroll feed, jammed between two turns, damages the thing that made users come back.

That gap is what conversational advertising exists to close.

Which ad formats work inside a chatbot

Formats that answer a question outperform formats that interrupt one. Adgentek serves five, and you enable only the ones that fit your product.

Spark is the format that separates a conversational ad server from a text-link network. Rather than a static sponsored line, the brand supplies a structured knowledge base and the user runs their own Q&A against it, self-qualifying as they go. Spark units average 3.2 interactions per session, and the resulting intent data is what makes the inventory worth premium budget rather than remnant spend.

What your chatbot earns depends on the render path

Impression-priced demand requires a real browser context where the impression can be verified client-side. Any surface that cannot provide one is priced on outcomes instead. Most platforms in this category do not disclose this.

React, iOS, and Android SDKs are in development. Contact hello@adgentek.ai for early access. The current matrix is maintained at choosing your integration path.

This is not an Adgentek pricing preference, it is how impression verification works. An impression event fired from a Worker, a backend, or an agent runtime originates from datacenter IP space, and verification vendors classify it as general invalid traffic. Advertisers do not pay for it. Adgentek therefore fires impression pixels client-side only, never server-side, which is exactly why a headless surface cannot claim one. The billing notice is the sole legitimate server-side event.

The practical read: if you want programmatic CPM in your chat app, use the Web SDK, or render from the REST API and get the integration certified. If you are running a headless agent surface with nothing rendering in a browser, you can still monetize, on CPA and filtered CPC. Adgentek runs a four-tier hard waterfall of Direct, Programmatic, CPC, and CPA before house ads, with programmatic demand from leading partners sitting behind the direct tier. That depth is what keeps fill from depending on any single demand relationship.

Where the ad request sits in your response cycle

The ad request runs in parallel with your model call, so it never extends the time your user waits for a response. Decision latency is under 300ms at p95, which resolves well inside the window your completion takes to stream. You dispatch the decision request as soon as you have the user turn, your completion streams as normal, and the slot fills when the decision returns. If it does not return in time, the slot stays empty and nothing about the conversation changes.

This is the design constraint that matters most in a chat product and the one most likely to be tested during your evaluation. Build the integration so an ad server outage is invisible to your users, then verify it by pointing the SDK at a dead endpoint.

Integrating the Agentic Ad Server

The Web SDK is the fastest path to a live ad and carries full demand eligibility. AdsMCP reaches the same decisioning engine from a headless agent surface.

<!-- before the closing body tag -->
<script src="https://api.adgentek.ai/storage/v1/object/public/sdk/sdk.js"></script>
<script>
  AdgentekAds.init({
    apiKey: 'YOUR_FULL_API_KEY_HERE',
    slotId: 'YOUR_SLOT_ID'
  });
</script>

<!-- place exactly where the ad should render -->
<div id="adgentek-ad"></div>

AdgentekAds.requestAd([
  { role: 'user', content: userMessage },
  { role: 'assistant', content: aiResponse }
]);

The SDK renders into an element it finds by id, defaulting to adgentek-ad. It does not create the element and it does not auto-discover slots. Impression, engagement, and click tracking are automatic and fire client-side. Full reference, including showAd, getAd, and manual tracking for custom rendering, is at the Web SDK documentation.

Your API key is generated in the publisher dashboard under Settings, API Keys, and is prefixed adgt_. The slot ID is the placement ID from Inventory, Surfaces, and it drives targeting, floor pricing, and reporting. Placeholder credentials do not serve ads.

{
  "mcpServers": {
    "adsmcp": {
      "url": "https://mcp.adgentek.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PUBLISHER_TOKEN"
      }
    }
  }
}

Transport is MCP Streamable HTTP. The serve tool registers as ads.serve and MCP clients sanitize it to ads_serve, so that is the name your client calls. Treat the endpoint rather than any document as authoritative for tool names, and list tools on connect instead of hardcoding them. AdsMCP is listed in the official MCP Registry as io.github.Adgentek/adsmcp. See the AdsMCP documentation.

AdsMCP is an integration path into the Agentic Ad Server rather than a separate product. Further detail lives at adsmcp.ai.

Complete integration documentation is at docs.adgentek.ai. Coding agents should start from the Adgentek integration skill and use the docs index to discover current pages rather than working from a cached snippet.

Controls that protect the conversation

For the full policy layer, see brand safety in AI advertising.

Frequently asked questions

Nothing to start. There is no setup fee, no platform fee to install, no minimum spend, and no contract required to go live. You create an account, generate a slot ID, and paste the Web SDK snippet.

No. There is no floor on conversations per month and no approval queue for standard surfaces. Smaller apps typically start on CPA and filtered CPC demand and grow into programmatic CPM as volume builds.

No. Decision latency is under 300ms at p95 and the request is dispatched in parallel with your model call rather than in front of it. If the decision does not resolve before your response renders, the slot stays empty and the conversation continues unchanged.

No. Adgentek adds a surface rather than taking one over. Subscriptions, existing placements, and any other revenue you run are untouched, and there is no exclusivity clause.

Complete control. You choose which formats appear, where in the message flow a slot exists, which advertiser categories are eligible, which named brands are permanently blocked, frequency caps per session and per day, and a minimum quality floor. Sensitive topics are excluded automatically.

Remove the snippet. There is no term commitment, no exclusivity, and no wind-down period. Your data is not retained for targeting because no user profiles are built in the first place.

Who built this

Adgentek's two founders have been building programmatic infrastructure since 2007, on both sides of the transaction. Frank Sinton founded Beachfront in 2007 and ran it as a cross-screen video SSP for CTV and streaming publishers until Seedtag acquired it in 2024. Paul Harrison co-founded Simpli.fi and served as its Chief Technology Officer, building the programmatic DSP and the buy-side infrastructure underneath it.

That matters here for a specific reason. The hard part of an ad server is not the format. It is yield management, waterfall logic, floor pricing, discrepancy handling, and the demand relationships that make a fill rate real rather than aspirational. Those are the problems both founders spent most of two decades solving, one on the sell side and one on the buy side, before AI surfaces existed. Adgentek is that stack rebuilt for a conversational surface, not a first attempt at ad serving.

Related surfaces

Adgentek monetizes coding agents and AI IDEs, publisher article pages, and AI search. For the mechanics of the format itself, see how conversational ads work and the comparison against display advertising.

Ready to turn conversations into revenue?

Create an account, generate a slot ID, and copy your snippet. No sales call required.

Create your publisher account Talk to us

Free to start. No traffic minimum. Keep your existing ad stack. No exclusivity.

Founding Member, Ad Context Protocol Built by the founders of Beachfront and Simpli.fi