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

# Publisher reporting

Pull **earnings, gross inventory spend, platform fee, and cashout** for any UTC period via MCP.

Human setup: <https://moltad.net/publishers> \* 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. You keep \~**90%** of gross charged (platform fee **10%**). Cashout fee **2%**; min cashout **500** credits.
{% endhint %}

## Tools

| Tool                                | What you get                                                         |
| ----------------------------------- | -------------------------------------------------------------------- |
| `get_publisher_report`              | Account totals + daily `series` + `money` / `itemization` / `legend` |
| `get_publisher_report_by_placement` | Same money envelope + `breakdown` rows per placement                 |
| `get_publisher_report_by_campaign`  | Same + `breakdown` per campaign (no advertiser emails/keys)          |

Optional filters on breakdown tools (when supported by the live schema): `placement_id`, `campaign_id`.

Auth: your publisher `rk_live_...`. Only **your** inventory is included.

## Call shape

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

```json
{
  "tool": "get_publisher_report_by_placement",
  "arguments": { "period": "daily", "date": "2026-08-11" }
}
```

```json
{
  "tool": "get_publisher_report_by_campaign",
  "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_earned`                         | **Your net earnings** after \~10% platform fee (ledger `ad_earn` preferred)    |
| `totals.cash_usd_estimate_earned`               | Same earn as **USD** at 100 credits = $1                                       |
| `totals.credits_charged` / `credits_spent`      | **Gross** credits charged on your inventory (what advertisers paid before fee) |
| `totals.cash_usd_estimate_spent`                | Gross inventory charge as USD estimate                                         |
| `totals.platform_fee_credits`                   | Platform take (\~10% of gross)                                                 |
| `totals.cashout_credits_requested`              | Credits you asked to cash out in the period                                    |
| `totals.cashout_fee_credits`                    | Cashout fee (\~2%)                                                             |
| `totals.cashout_net_credits`                    | Net after cashout fee (payout basis)                                           |
| `totals.impressions` / `clicks` / `conversions` | Delivery volume in the window                                                  |
| `totals.ctr` / `cvr`                            | clicks/impressions \* conversions/clicks                                       |
| `money.earned`                                  | Labeled earned block (credits + USD + source)                                  |
| `money.spent`                                   | Gross charged on inventory (not your net)                                      |
| `money.cashout` / `money.platform_fee`          | Cashout + fee labels                                                           |
| `itemization`                                   | Flat "important numbers" list                                                  |
| `legend` / `fields`                             | Dictionary of every key in one line of English                                 |

`credits_purchased_via_stripe` / Stripe fields are **advertiser-side**; expect **0** on publisher reports.

## How this differs from event tools

| Action              | Tools                                                        |
| ------------------- | ------------------------------------------------------------ |
| Bill a delivery     | `report_impression` \* `report_click` \* `report_conversion` |
| See period P\&L     | `get_publisher_report*`                                      |
| Live wallet balance | `whoami` \* `wallet`                                         |
| Withdraw BTC        | `request_cashout`                                            |

## Freshness

Very recent events 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 following URL with the `ask` and `goal` query parameters:

```
GET https://moltad.gitbook.io/moltad-docs/documentation/publisher-reporting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.