> ## Documentation Index
> Fetch the complete documentation index at: https://docs.palagus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Six ready-made reports

> A report hands your assistant a finished checklist: which data to read, in which order, and how to write it up. You pick the project, the assistant does the rest — and you can ask follow-up questions afterwards.

## Two places, the same reports

<Columns cols={2}>
  <Card title={"In your assistant"}>
    You start a report as a command — in Claude Code, for example, type `/palagus` and press Tab to get `/mcp__palagus__weekly_pulse`. Your assistant then runs the checklist with Palagus’ tools.
  </Card>

  <Card title={"In the Palagus app"}>
    The same reports run with one click on the Reports page, on plans that include Reports. The topic heatmap is the one report that is not there — it takes too many calls for a report in the app.
  </Card>
</Columns>

In the MCP standard these are called `prompts`. We say reports, because in Palagus a prompt is one of your tracked questions. New reports reach your assistant when it reconnects; there is nothing to install.

<Info>
  **Rules every report follows** The assistant says which time window it used, reports the numbers from Palagus as they are, and marks any cause it offers as its own reading — never as a fact. If a part of the data is empty, it says so instead of filling the gap.
</Info>

## Where your assistant offers them

| Assistant | Where | Then |
| :- | :- | :- |
| Claude.ai | + → Connectors → Add from Palagus | The report lands in the message box as an attachment and is not sent yet — press Send yourself. Type the project's name exactly as it appears in Palagus. |
| Claude Code | Type /palagus and press Tab — it becomes /mcp\_\_palagus\_\_weekly\_pulse | Add the project; it runs right away. |
| ChatGPT | ChatGPT does not offer them | Ask in plain words instead — the tools are called all the same. |
| Codex CLI | Codex does not offer them (checked 2026-10-01) | Ask in plain words instead — the tools are called all the same. |

## The reports

<AccordionGroup>
  <Accordion title={"Weekly pulse"} id={"weekly_pulse"}>
    <Badge stroke>weekly\_pulse</Badge>

    A short status of one project: where visibility, share of voice and sentiment stand, the biggest movements, which competitors gained ground, and the answers whose sentiment stands out.

    **Use it when** you want a Monday-morning snapshot of what changed.

    <Columns cols={2}>
      <Column>
        `project` <sub>required</sub>
      </Column>

      <Column>
        The project's name, exactly as it appears in Palagus.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `range` <sub>optional</sub>
      </Column>

      <Column>
        The time window: last1h, last6h, last12h, last24h, last7d, lastMonth, lastQuarter, lastYear or all. Default last7d.
      </Column>
    </Columns>
  </Accordion>

  <Accordion title={"Drop diagnosis"} id={"drop_diagnosis"}>
    <Badge stroke>drop\_diagnosis</Badge>

    Why a number fell, step by step: the overview, then narrowed down by topic, persona and AI engine, then the sources the answers cite, then the answers themselves.

    **Use it when** visibility or sentiment went down and you want to know where it happened.

    <Columns cols={2}>
      <Column>
        `project` <sub>required</sub>
      </Column>

      <Column>
        The project's name, exactly as it appears in Palagus.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `range` <sub>optional</sub>
      </Column>

      <Column>
        The time window: last1h, last6h, last12h, last24h, last7d, lastMonth, lastQuarter, lastYear or all. Default last7d.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `topic` <sub>optional</sub>
      </Column>

      <Column>
        Narrow the diagnosis to one topic, by its name as it appears in Palagus.
      </Column>
    </Columns>
  </Accordion>

  <Accordion title={"Where you lose"} id={"where_you_lose"}>
    <Badge stroke>where\_you\_lose</Badge>

    Where the project trails its competitors — per AI engine and per topic — and to whom, with answers that name the competitor and not you as evidence. Every gap comes with its measurement margin, and a gap within it is called level.

    **Use it when** you want to know where competitors are ahead of you, and by how much it really is.

    <Columns cols={2}>
      <Column>
        `project` <sub>required</sub>
      </Column>

      <Column>
        The project's name, exactly as it appears in Palagus.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `range` <sub>optional</sub>
      </Column>

      <Column>
        The time window: last1h, last6h, last12h, last24h, last7d, lastMonth, lastQuarter, lastYear or all. Default last7d.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `competitor` <sub>optional</sub>
      </Column>

      <Column>
        Compare with this one competitor everywhere. Without it, each engine and topic names its own strongest competitor.
      </Column>
    </Columns>
  </Accordion>

  <Accordion title={"Topic heatmap"} id={"topic_heatmap"}>
    <Badge stroke>topic\_heatmap</Badge> <Badge color="orange">Beta</Badge> Assistant only — not in the app

    Visibility per topic and per AI engine, as a grid — strong and weak spots at a glance.

    Why it is a beta: Every cell is a separate call, so the grid is capped at 6 topics × 4 AI engines and can take a while.

    **Use it when** you want to see which topic is weak on which engine.

    <Columns cols={2}>
      <Column>
        `project` <sub>required</sub>
      </Column>

      <Column>
        The project's name, exactly as it appears in Palagus.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `range` <sub>optional</sub>
      </Column>

      <Column>
        The time window: last1h, last6h, last12h, last24h, last7d, lastMonth, lastQuarter, lastYear or all. Default last7d.
      </Column>
    </Columns>
  </Accordion>

  <Accordion title={"Source authority"} id={"source_authority"}>
    <Badge stroke>source\_authority</Badge> <Badge color="orange">Beta</Badge>

    The websites AI answers cite for the project — your own against competitors' against third parties — and which engines cite each.

    Why it is a beta: It works from citation counts only — there is no rate at which a source is fetched.

    **Use it when** you are working on content and want to know which sites the engines rely on.

    <Columns cols={2}>
      <Column>
        `project` <sub>required</sub>
      </Column>

      <Column>
        The project's name, exactly as it appears in Palagus.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `range` <sub>optional</sub>
      </Column>

      <Column>
        The time window: last1h, last6h, last12h, last24h, last7d, lastMonth, lastQuarter, lastYear or all. Default last7d.
      </Column>
    </Columns>
  </Accordion>

  <Accordion title={"Campaign tracker"} id={"campaign_tracker"}>
    <Badge stroke>campaign\_tracker</Badge>

    Did anything move after a date — a campaign, an article, a PR push? It compares an equal window before and after the date, reads the curve across both to tell a change that starts at the date from one already under way, and lists the prompts that moved most. It shows what changed, never that it changed because of the date.

    **Use it when** you launched something and want to see whether AI answers reacted.

    <Columns cols={2}>
      <Column>
        `project` <sub>required</sub>
      </Column>

      <Column>
        The project's name, exactly as it appears in Palagus.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `date` <sub>required</sub>
      </Column>

      <Column>
        The day it started, as YYYY-MM-DD. The two windows meet at midnight UTC of that day.
      </Column>
    </Columns>

    <Columns cols={2}>
      <Column>
        `days` <sub>optional</sub>
      </Column>

      <Column>
        Length of each window in days, 1 to 90. Default 7.
      </Column>
    </Columns>
  </Accordion>
</AccordionGroup>

## After a report

The assistant keeps every tool at hand, so you can drill into whatever stands out — one engine, one topic, or the answers behind a number. See the [use cases](/usecases) for questions that work well.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.