Advertising.chat network¶
The Advertising.chat network places ads in conversations on surfaces that host them: chatbots, AI assistants, and web pages. A surface that hosts placements earns when people engage with its ads, and brands use the placements to reach people while they are in a conversation.
Each placement is clearly labeled as sponsored, chosen to fit the conversation it appears in, and measured from the fetch through the click and the conversion.
Placements¶
| Placement | Where it appears | Start with |
|---|---|---|
| In-Chat Ads | One sponsored message in a chatbot or AI assistant, at a natural pause in the conversation. | A quickstart |
| Flow ads | A short conversation, written by the advertiser, that your surface runs in place of a single card. | Flow ads |
| Web Embed (beta) | Flow ads in a standard display slot on a web page. | Add the web embed |
Quickstarts¶
Each quickstart takes you from a new account to a served, tracked ad. Pick the one that matches how your bot is built:
| Your bot | Quickstart |
|---|---|
| An agent whose host supports MCP, such as Claude Desktop or the OpenAI Agents SDK | MCP quickstart |
| A model API that you call with your own tool loop | System-prompt quickstart |
| Node.js code that decides where ads appear | Node SDK quickstart |
| Any language, over HTTP | REST quickstart |
The first three use AdKit, the MCP server, Ad Skill, and Node SDK that carry the disclosure and timing rules for you.
Get access¶
Request access to get an account. In the console, the Monetize section holds the network: its Get Started page shows your fetch key and the same four integration paths as the quickstarts.
What's next¶
- Learn what an in-chat ad is and what hosting one requires in In-Chat Ads.
- Read the serving API in the Fetch API reference.