> For the complete documentation index, see [llms.txt](https://moltad.gitbook.io/moltad-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moltad.gitbook.io/moltad-docs/documentation/ad-units-complete.md).

# Ad units complete

Source of truth in product code: MoltAd `src/pricing.ts` (floors, defaults, definitions) and tool contracts in `src/tools.ts` / remote MCP at `https://moltad.net/mcp`.

**Credit peg:** 100 credits = $1.00 USD.

## Families

### Agent-directed (prefer for AI chat / API agents)

These sell the **agent's context and decision path**, not a human eyeball.

| Code      | Label                             | What you pay for                           | Billing tool                             | Default\* | Floor\* |
| --------- | --------------------------------- | ------------------------------------------ | ---------------------------------------- | --------- | ------- |
| `cpr`     | CPR -- Cost Per Recommendation    | Offer appears in agent recommendation      | `report_conversion` \* `recommendation`  | 100       | 50      |
| `cpia`    | CPIA -- Cost Per Agent Impression | Offer injected into agent-visible context  | `report_impression`                      | 12+       | 6+      |
| `cppromo` | CPPromo -- agent coupon/promo     | Machine-readable promo applied             | `report_conversion` \* `coupon_redeemed` | 70        | 35      |
| `cpd`     | CPD -- Cost Per Decision          | Agent selects your option in a decide step | `report_conversion` \* `decision`        | 150       | 75      |

\* Credits. + CPIA uses **per 1,000** pricing semantics like CPM (see `creditsForEvent` / tool docs).

Chat and AI API apps commonly map:

| Chat surface                        | Typical unit        |
| ----------------------------------- | ------------------- |
| Sidebar / always-visible agent slot | `cpia` or `cppromo` |
| Inline recommendation in answer     | `cpr`               |
| Choose-between options step         | `cpd`               |
| Apply discount code in flow         | `cppromo`           |

Placement kinds: `agent_response`, `tool_result`, `marketplace_listing`, **`chat_sidebar`**, `sponsored_tool`, `general`.

### Legacy / human-adjacent

| Code  | Label                     | Billing                                            |
| ----- | ------------------------- | -------------------------------------------------- |
| `cpm` | CPM per 1,000 impressions | `report_impression`                                |
| `cpc` | Cost per click            | `report_click`                                     |
| `cpi` | Cost per install          | `report_conversion` \* `cpi` (usually after click) |
| `cpa` | Cost per action           | `report_conversion` \* `cpa`                       |
| `cpl` | Cost per lead             | `report_conversion` \* `cpl`                       |

Defaults (credits): cpm 20 / cpc 5 / cpa 80 / cpl 40 / cpi 60. Floors: 10 / 2 / 40 / 20 / 30.

## When to use which

1. **You control an LLM or agent loop** -> agent-directed first.
2. **You only have a web pixel** -> legacy CPM/CPC may fit, but product thesis favors agents.
3. **Platform affiliate demand** -> keep campaign `rateCredits` at or below the brand's public `maxRateCredits` (see [worked example](https://moltad.gitbook.io/moltad-docs/documentation/affiliate-demand-and-kimigpt)).
4. **Direct SaaS promo in chat** -> CPPromo + `create_coupon` + publisher `deliver_ad`.

## Event -> unit map

| `conversionType`      | Unit            |
| --------------------- | --------------- |
| `recommendation`      | `cpr`           |
| `decision`            | `cpd`           |
| `coupon_redeemed`     | `cppromo`       |
| `cpa` / `cpl` / `cpi` | matching legacy |

## Workflow sketch

```
Advertiser: create_campaign (escrow budgetCredits)
Publisher:  deliver_ad(campaignId)           # free pull
Publisher:  report_impression | report_click | report_conversion
Advertiser: get_advertiser_report* / get_attribution / postbacks
```

`deliver_ad` alone never spends campaign budget; reporting does.

## Tools that define creative surfaces

* **Advertiser:** `create_campaign`, `create_coupon`, `register_postback`, `get_advertiser_report*`, `get_attribution`
* **Publisher reporting:** `get_publisher_report*` (period rollups via MCP)
* **Publisher:** `list_placement`, `deliver_ad`, `report_impression`, `report_click`, `report_conversion`
* **Product SKUs (TikTok US Shop):** `search_tiktok_products`, `get_tiktok_product` -- see [Product ad units](https://moltad.gitbook.io/moltad-docs/documentation/product-ad-units) and [TikTok US Shop products](https://moltad.gitbook.io/moltad-docs/documentation/tiktok-us-shop-products)

## Pricing page

Human summary: <https://moltad.net/pricing>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://moltad.gitbook.io/moltad-docs/documentation/ad-units-complete.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.