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

# Pricing

> Usage-based pricing for Agent, Code Review, and Status

<Info>
  This usage-based pricing plan applies to all new customers as of March 27, 2026. If you signed up before this date, you may be on our [legacy pricing plan](/legacy-pricing).
</Info>

Macroscope features are billed based on usage, so your costs are tied to the actual work Macroscope does reviewing and processing your code.

## Usage-Based Prices

| Feature     | Price                                                     | Description                                                                 |
| ----------- | --------------------------------------------------------- | --------------------------------------------------------------------------- |
| Agent       | \$0.01 per credit (1000 free credits/month)               | Ask questions and take action via Slack, GitHub, or API                     |
| Code Review | \$0.05 per KB of diff reviewed (10 KB minimum per review) | Reviews PRs for correctness and suggests fixes                              |
| Status      | \$0.05 per commit processed                               | Commit summaries, area classification, productivity metrics, sprint reports |

## How Billing Works

Macroscope uses a prepaid usage model. Each workspace has a single balance that covers Code Review, Status, and Agent, and decreases with usage. Enable **Auto-refill** to have your balance top up automatically when it falls below a threshold you configure, so there's no disruption.

<Note>
  Usage data in your billing dashboard may be delayed by a few minutes due to how Stripe's metering system works.
</Note>

<Tip>
  Admins can manage auto-refill and spend controls, and view their workspace's balance, usage history, and usage costs in **Settings → Billing**.
</Tip>

<AccordionGroup>
  <Accordion title="How do I set up auto-refill?">
    Go to **Settings → Billing** and configure your balance threshold and refill amount. We recommend enabling auto-refill to ensure Code Review and Status processing run without interruption. If your balance hits zero without auto-refill, processing pauses until your balance is topped up.
  </Accordion>

  <Accordion title="How do invoices work?">
    Whenever an auto-refill payment is made, you'll receive a receipt. Your invoice at the end of your usage period will be \$0 since top-ups are prepaid. You can view all receipts and invoices in **Settings → Billing**, powered by Stripe.
  </Accordion>

  <Accordion title="How do I manage my payment method?">
    Add, update, or remove payment methods in **Settings → Billing**.
  </Accordion>

  <Accordion title="Why does my usage data look off in the billing dashboard?">
    There can be up to a few minutes of delay in meter data due to how Stripe's metering system works. If something still looks off after accounting for that, reach out to us at **[support@macroscope.com](mailto:support@macroscope.com)**.
  </Accordion>

  <Accordion title="Does my balance expire?">
    No.
  </Accordion>

  <Accordion title="What happens if I cancel?">
    Access continues until the end of your billing period. Your balance stays in your account. If you resubscribe, it picks up where you left off.
  </Accordion>
</AccordionGroup>

## Spend Controls

You can set several limits to control your costs. Configurable by a workspace admin in **Settings → Billing**.

| Control                 | Description                                       | Override                                             |
| ----------------------- | ------------------------------------------------- | ---------------------------------------------------- |
| **Monthly spend limit** | Hard ceiling on total usage per billing period.   | Cannot be overridden                                 |
| **Per-review cap**      | Max cost for a single Code Review run.            | Override with [on-demand review](#on-demand-reviews) |
| **Per-PR cap**          | Max total cost across all Code Reviews on one PR. | Override with [on-demand review](#on-demand-reviews) |

<Note>
  Default caps are \$10 per review and \$50 per PR. Both are adjustable in **Settings → Billing**.
</Note>

<AccordionGroup>
  <Accordion title="What if my balance runs out?">
    If you don't have auto-refill on and your balance runs out, all processing pauses — Agent, Code Review, and Status. Commits and PRs pushed during that window are skipped and are not retroactively processed when your balance is topped up.
  </Accordion>

  <Accordion title="What if I hit my monthly max?">
    Agent, Code Review, and Status processing pause for the rest of the billing period. Auto-refill does not trigger when the monthly max is hit. Commits and PRs pushed during that window are skipped.

    **Processing resumes when the next period starts or an admin increases the limit.**
  </Accordion>

  <Accordion title="How does auto-refill interact with the monthly spend limit?">
    Auto-refill tops up your balance but does not override the monthly spend limit. If you hit your monthly limit, processing pauses even if you still have balance remaining. They are separate controls.
  </Accordion>
</AccordionGroup>

## Agent

Credits are a usage-based billing unit for Macroscope's Agent features: Slack queries, Macros, Webhooks and Check Run Agents. **1 credit = \$0.01.** Credit usage is calculated by taking the raw LLM cost of each agent run (based on your prompts and parameters), then adding a 5% markup, then dividing by the value of each credit (\$0.01). Every workspace includes **1000 free credits per month**.

Free credits do not roll over. Usage beyond the free credits draws from your balance.

<Tip>
  **Credit calculation:** raw LLM cost of the agent run × 1.05 markup ÷ \$0.01 per credit = credits consumed.
</Tip>

### What uses credits

| Feature                               | Trigger                                        |
| ------------------------------------- | ---------------------------------------------- |
| [Slack queries](/agent)               | DM or tag `@Macroscope` in any channel         |
| [GitHub queries](/agent)              | Mention `@macroscope-app` in any PR discussion |
| [Macros](/macros) (scheduled)         | Cron schedule                                  |
| [Macros](/macros) (event-triggered)   | New PR or commit                               |
| [Webhooks](/api)                      | HTTP POST to API                               |
| [Check Run Agents](/check-run-agents) | `.macroscope/*.md` on PR                       |
| [Fix It for Me](/fix-it-for-me)       | Reply to a review comment or ask in Slack      |

<Note>
  [Code Review](#code-review) and [Status](#status) are billed separately via their own meters. They do not consume credits.
</Note>

### Transparency

Workspace admins can view detailed Agent usage logs in **Settings → Billing**, including exporting a full CSV with cost and metadata for every agent invocation.

<AccordionGroup>
  <Accordion title="Why do different queries cost different amounts?">
    Credit usage scales with LLM cost — a quick Slack question uses fewer tokens than a complex multi-step research task, so it costs fewer credits.
  </Accordion>

  <Accordion title="What happens if I use all 1000 free credits?">
    Usage beyond the free credits draws from your balance, the same one used by Code Review and Status. Auto-refill and spend limits apply normally.
  </Accordion>

  <Accordion title="Can I see my agent usage?">
    Yes. Go to **Settings → Billing** to view usage logs or export a CSV with detailed cost and metadata for every invocation.
  </Accordion>
</AccordionGroup>

## Code Review

Code Review is charged per review, based on the byte size of the PR diff that Macroscope reviews.

<AccordionGroup>
  <Accordion title="What counts as a review?">
    Anytime Macroscope's correctness check runs on a PR counts as one review. This can happen:

    * Automatically on each push to a PR (if automatic Code Review is enabled for that repo)
    * Manually, by commenting `@macroscope-app review` on any PR in GitHub
  </Accordion>

  <Accordion title="How is diff size calculated?">
    We pull diffs from GitHub in unified diff format (u3) and measure diff size by the raw u3 diff bytes.

    For the first push to a PR (or any force push), we compare HEAD to the merge base of the target branch. For subsequent pushes, we always compare HEAD to the previous reviewed HEAD.

    Any files Macroscope doesn't review, such as binaries or files excluded by your [`.macroscope/ignore` file](/bug-detection-and-fixes#macroscope-ignore), are excluded from the diff, so you only pay for the files Macroscope actually reviews.
  </Accordion>

  <Accordion title="What does the 10 KB minimum mean?">
    Every review has a minimum of 10 KB. If your diff is under 10 KB, you're charged for 10 KB. At standard pricing (\$0.05/KB), that's \$0.50.

    <Note>
      The effective dollar amount may vary if you're on a plan with custom rates.
    </Note>
  </Accordion>

  <Accordion title="How much does a typical review cost?">
    Most reviews are under 10 KB and thus cost \$0.50. Assuming the standard rate of \$0.05/KB, here are some ballpark approximations:

    | Change type    | Diff size | Cost                   |
    | -------------- | --------- | ---------------------- |
    | Small bug fix  | 2 KB      | \$0.50 (10 KB minimum) |
    | Medium feature | 30 KB     | \$1.50 (30 × \$0.05)   |
    | Large refactor | 700 KB    | \$35 (700 × \$0.05)    |
  </Accordion>

  <Accordion title="Do force-pushes or rebases trigger a new review?">
    Yes.

    That said, we try to be clever and detect trivial force pushes and rebases to save you money.
  </Accordion>
</AccordionGroup>

### Per-Repo Code Review Controls

Configure in **Settings → Repos**. [Learn more about repo settings](/settings#repo-settings).

| Control                        | Description                                                                                              |
| ------------------------------ | -------------------------------------------------------------------------------------------------------- |
| **Enable/disable Code Review** | Turn off automatic Code Review for specific repos. You can still review [on-demand](#on-demand-reviews). |
| **Skip Dependabot**            | Skip review on Dependabot PRs.                                                                           |
| **Skip by PR label**           | Skip review for PRs with specific labels.                                                                |
| **Force review by label**      | Always review PRs with these labels, even when auto-review is off.                                       |
| **Skip draft PRs**             | Don't review drafts until marked ready.                                                                  |

### On-Demand Reviews

Even if automatic Code Review is off for a repo, you can always invoke a review manually by commenting `@macroscope-app review` on any PR in GitHub.

### Excluding Files from Code Review

You can exclude specific files from review using a `.macroscope/ignore` file. See [`.macroscope/ignore`](/bug-detection-and-fixes#macroscope-ignore) for details.

## Status

Status is powered by per-commit summarization. This feeds your dashboards, weekly digests, productivity metrics, and sprint reports.

<AccordionGroup>
  <Accordion title="How is Status different from Code Review?">
    Code Review runs on PRs and analyzes the diff for bugs and correctness issues. Status runs on individual commit summaries and powers features like executive summaries and productivity insights. They're separate processes billed independently.
  </Accordion>

  <Accordion title="What triggers a commit charge?">
    A commit is charged after Macroscope successfully summarizes it. All branches are in scope and each commit is billed at most once.

    **Not charged:**

    * Commits pushed while your balance is exhausted or spend limit is hit (skipped)
    * Commits on repos with Status disabled

    Bot commits (e.g. Dependabot, CI) are processed and billed like any other commit.
  </Accordion>

  <Accordion title="What happens if I disable Status for a repo?">
    Commits on that repo won't be summarized, classified, or included in productivity metrics. No Status charges for that repo.
  </Accordion>
</AccordionGroup>

## Common Questions

<AccordionGroup>
  <Accordion title="How is this different from per-seat pricing?">
    Per-seat pricing charges a fixed rate per developer regardless of activity. Usage-based pricing means you only pay for what Macroscope actually processes. Teams with lighter activity pay less; teams that push more code pay proportionally more.
  </Accordion>

  <Accordion title="Do you have a free trial?">
    Yes. New workspaces receive a one-time \$100 in free usage to get started.
  </Accordion>
</AccordionGroup>

## Annual Discounts

If you're interested in discounted rates, reach out and we can discuss options for annual commitments. Contact **[enterprise@macroscope.com](mailto:enterprise@macroscope.com)**.

***

Questions? Email **[support@macroscope.com](mailto:support@macroscope.com)** or reach out in your shared Slack channel.