Skip to content

AdKit — your first ad in 5 minutes

AdKit is the fastest way to monetize an LLM-based conversation. Whether your bot is an agent with tools, a system prompt around a model API, or a Node service, AdKit gets you from zero to a served, clickable, revenue-earning ad in minutes — no channel documentation required.

AdKit is three pieces that work together (use any of them alone):

  • The MCP server — @advertising-chat/mcp. Gives any MCP-capable agent two tools: fetch_ad and record_event.
  • The Ad Skill — an instruction pack that teaches your assistant when to place ads (natural pause points, never sensitive moments), how to pass conversation context, and how to disclose sponsorship.
  • The SDK — @advertising-chat/sdk, a typed, zero-dependency Node client for the ads API, with webchat and WhatsApp render helpers.

Before you start: get a fetch key

Every path starts the same way. Advertising.chat is in private beta — request access at advertising.chat if you don't have an account yet. Then:

  1. Sign in to the Advertising.chat Console.
  2. Copy your fetch key — new accounts get one automatically, shown on the Get Started page (also under API Keys, /admin).

That is the only credential you need; keep it out of client-side code. Your first fetch returns a real ad — there is nothing else to set up.

Choose your path

  • My bot is an agent (MCP)

    Claude, OpenAI Agents, LangGraph, n8n — anything that speaks MCP. Add one server, paste one skill. The recommended path.

    MCP quickstart

  • My bot is a system prompt

    You call a model API with your own tool loop. Wire two small tools and paste the skill into your prompt.

    System-prompt quickstart

  • My bot is Node code

    Fetch, render, and track ads with the typed SDK — you decide exactly where ads appear.

    Node SDK quickstart

The rules of the road

However you integrate, three duties come with serving ads:

  1. Disclose. Every ad is clearly labeled — "Sponsored" (or its translation). The MCP tools and render helpers carry the label for you.
  2. Respect the moment. Fetch at natural pause points; never during sensitive conversations. The Ad Skill encodes this; the network also applies its own appropriateness rules.
  3. Report honestly. Click URLs are tracked automatically; record conversions when they truly happen, never otherwise.

Conversation context you send with a fetch is used to select that ad — it is not a tracking profile. No cookies, no identity graph.

Manage your account from an agent, too

The pieces above are for serving ads. There is also a management MCP server — @advertising-chat/mcp-manage — that lets you operate your account (ad units, line items, creatives, campaigns, performance queries) from Claude Desktop/Code with your own sign-in. See Operate Advertising.chat from Claude.