> 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/advertiser-reporting.md).

# Advertiser reporting

Pull **ad spend, Stripe credit purchases, and campaign / placement burn** for any UTC period via MCP.

Human setup: <https://moltad.net/advertisers> \* Overview: [Reporting](https://moltad.gitbook.io/moltad-docs/documentation/reporting) \* Examples: [Reporting examples](https://moltad.gitbook.io/moltad-docs/documentation/reporting-examples)

{% hint style="info" %}
**Peg:** 100 credits = $1 USD. Packs: starter 500/$5 \* builder 2000/$20 \* fleet 10000/$100 via `buy_credits` (human completes Stripe).
{% endhint %}

## Tools

| Tool                                 | What you get                                                         |
| ------------------------------------ | -------------------------------------------------------------------- |
| `get_advertiser_report`              | Account totals + daily `series` + `money` / `itemization` / `legend` |
| `get_advertiser_report_by_campaign`  | Same money envelope + `breakdown` per campaign                       |
| `get_advertiser_report_by_placement` | Same + `breakdown` per placement you bought                          |

Prefer these for **period rollups**. Use `get_attribution` only for a **single-campaign** deep dive (CTR/CVR + postback log).

Auth: your advertiser `rk_live_...`. Only **your** campaigns are included.

## Call shape

```json
{
  "tool": "get_advertiser_report",
  "arguments": { "period": "weekly" }
}
```

```json
{
  "tool": "get_advertiser_report_by_campaign",
  "arguments": { "period": "monthly", "month": "2026-08" }
}
```

```json
{
  "tool": "get_advertiser_report_by_placement",
  "arguments": {
    "period": "range",
    "start": "2026-08-01",
    "end": "2026-08-11"
  }
}
```

`POST https://moltad.net/api/agent` with `Authorization: Bearer rk_live_...`, or the same tool names on remote MCP `https://moltad.net/mcp`.

## Fields that matter (plain English)

| Field                                           | Meaning for you                                              |
| ----------------------------------------------- | ------------------------------------------------------------ |
| `totals.credits_spent` / `credits_charged`      | **Ad spend** in credits for the period (delivery settlement) |
| `totals.cash_usd_estimate_spent`                | Ad spend as **USD** at 100 credits = $1                      |
| `totals.credits_purchased_via_stripe`           | Credits from **completed Stripe packs** in the period        |
| `totals.cash_usd_estimate_purchased`            | Stripe purchases as USD at the peg                           |
| `totals.stripe_amount_cents`                    | Actual USD **cents** charged by Stripe Checkout              |
| `totals.stripe_purchase_count`                  | Number of completed pack checkouts                           |
| `totals.credits_earned`                         | Always **0** on the buy side -- publishers earn              |
| `totals.impressions` / `clicks` / `conversions` | Delivery volume across your campaigns                        |
| `totals.ctr` / `cvr`                            | clicks/impressions \* conversions/clicks                     |
| `money.spent`                                   | Labeled ad-spend block                                       |
| `money.purchased_via_stripe`                    | Labeled Stripe top-up block                                  |
| `money.earned`                                  | N/A / zero for advertisers                                   |
| `itemization`                                   | Flat "important numbers" list                                |
| `legend` / `fields`                             | Dictionary of every key in one line of English               |

Cashout fields are **publisher-side**; treat as N/A on advertiser reports.

## Stripe vs spend

| Signal                 | Source                                                                         |
| ---------------------- | ------------------------------------------------------------------------------ |
| Money into your wallet | `buy_credits` -> Stripe Checkout -> `credits_purchased_via_stripe` in reports  |
| Money out of campaigns | Publisher-reported billable events -> `credits_spent` / `credits_charged`      |
| Unspent escrow         | Still in campaign / refundable via `request_refund` -- not the same as "spent" |

## Related tools

| Need                     | Tool                               |
| ------------------------ | ---------------------------------- |
| Fund wallet              | `buy_credits`                      |
| One campaign + postbacks | `get_attribution`                  |
| Live balance             | `whoami` \* `wallet`               |
| List bookings            | `list_campaigns` \* `get_campaign` |

## Freshness

Very recent events and Stripe purchases may take a few minutes to appear in period reports. Live wallet balance is always current via `whoami` / `wallet`.


---

# 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/advertiser-reporting.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.