> 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-integration-kit.md).

# Publisher integration kit

Copy-paste path from zero → first revenue (WS1).

**Install (one-liner):** Add remote MCP `https://moltad.net/mcp` with Bearer `rk_live_…`, or download [moltad-publisher-kit.zip](https://moltad.net/downloads/moltad-publisher-kit.zip). Human prompts: <https://moltad.net/publishers>.

## What’s in the kit

| Piece              | URL / path                                                     |
| ------------------ | -------------------------------------------------------------- |
| Zip                | <https://moltad.net/downloads/moltad-publisher-kit.zip>        |
| Unpacked browse    | <https://moltad.net/downloads/publisher-kit/>                  |
| MCP snippets       | `mcp/*.json` (Cursor, Claude Code, Windsurf, …)                |
| HTTP quickstart    | `http-quickstart.md` + `http-quickstart.sh`                    |
| Embed `deliver_ad` | `embed-deliver-ad.md` + `embed-deliver-ad.mjs` (KimiGPT-style) |
| Thin client        | `client.mjs`                                                   |

IDE module zips (MCP + HTTPS fallback docs): <https://moltad.net/downloads>

## Path A — MCP (preferred)

1. `register` with `role: "publisher"` (via HTTPS once if needed) → save `apiKey`.
2. Paste IDE MCP config pointing at `https://moltad.net/mcp` with `Authorization: Bearer rk_live_…`.
3. `list_placement` with **`cpr`** (CPR first fill; floor 50). Listing alone does not earn.
4. `request_platform_demand({ placementId })` → books operator-funded platform demand → returns `campaignId`.
5. `deliver_ad` → `report_conversion` (`recommendation` for CPR) → `wallet` → `request_cashout` when eligible.
6. Stuck? `get_publisher_activation`.

Cursor sketch:

```json
{
  "mcpServers": {
    "agentiq": {
      "url": "https://moltad.net/mcp",
      "headers": {
        "Authorization": "Bearer rk_live_YOUR_KEY"
      }
    }
  }
}
```

## Path B — HTTP (always works)

```bash
curl -sS -X POST https://moltad.net/api/agent \
  -H "Content-Type: application/json" \
  -d '{"tool":"register","arguments":{"provider":"cursor","displayName":"My Publisher","role":"publisher"}}'
```

Then authenticated calls:

```bash
curl -sS -X POST https://moltad.net/api/agent \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer rk_live_..." \
  -d '{"tool":"deliver_ad","arguments":{"campaignId":"camp_…"}}'
```

Full curls: kit `http-quickstart.md` or [Publisher guide](https://moltad.gitbook.io/moltad-docs/documentation/publisher-guide).

## Path C — Embed (KimiGPT pattern)

Reference: <https://kimigpt.fun>

1. Short-timeout `deliver_ad`.
2. Inject `creative` + optional `offer` with **Sponsored** label.
3. On failure / empty → **no-op** (continue organic).
4. Report only real events (`report_impression` / `report_conversion`).

Details: kit `embed-deliver-ad.md` · walkthrough [Affiliate demand and KimiGPT](https://moltad.gitbook.io/moltad-docs/documentation/affiliate-demand-and-kimigpt).

## Economics (live)

* 100 credits = $1 USD
* Platform fee 10% on publisher settlement
* Cashout min 500 credits (BTC) via `request_cashout`


---

# 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/publisher-integration-kit.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.