Skip to main content
Scouts are in Beta and free during the Beta.
A Scout is an agent you assign to your reports and alerts. Each time one of them is delivered, the Scout reads it, works out what moved and why, and adds its answer to the delivery. It keeps a memory between runs, so each investigation starts from what the last one learned instead of starting cold. The Scout reads the same cost model you query through the Costory MCP: allocated cost, usage metrics, events and deploys. There’s nothing to wire up per Scout.

How a Scout works

Create a Scout

  • In the app: open Scouts in the left sidebar and click New scout. Costory asks a few questions, then writes the Scout’s instructions and assigns its reports or alerts.
Costory chat prefilled with a request to create a new Scout

New scout opens a chat with Costory, prefilled to define the Scout

Costory Scouts page showing the FinOps Advisor Scout with its instructions

The Scouts page, with a Scout's assigned reports, alerts and instructions

Assign a Scout to a report or an alert

  • From a report or an alert: in the report or alert editor, the right panel has a Scout field (“Scout reads your reports and enriches its delivery with follow-up answers”). Pick a Scout from the list. It then runs every time that report or alert is delivered.
Report editor with the Scout field open and a Scout selected from the list

The Scout field in the report editor

  • From Claude, Cursor or any MCP client: ask your assistant to create a Scout. The Costory MCP exposes create_scout, update_scout and list_scouts.
Example prompt:

Scout settings

Open a Scout from the Scouts page. Click Edit to change it.

Write good instructions

The instructions decide whether a Scout is useful or noisy. The ones that work best:
  1. Name the reader. For example: “engineering managers and the CTO” or “the Support AI team”.
  2. Give each finding a fixed structure. For example: What, Why it matters, Action, Owner, Estimated impact, Effort.
  3. Rank and cap. For example: rank by estimated monthly impact and keep at most 5 findings, then list what to watch.
  4. Say how to treat data artefacts. Spend moving between accounts with no net change, or a one-off commitment purchase, is a “check data” note, not a saving.
  5. Forbid invented numbers. Every amount has to come from the data.
  6. End with a question to ask next, in the Costory chat or in Claude with the Costory MCP.
Write your own, or start from a template. Templates are available in the app when you create a Scout. They’re starting points: nothing is created until you pick one.

Ask a Scout and steer it

  • In the thread: reply in Slack and mention @costory to ask a follow-up, add context it couldn’t know (“we shipped a new checkout on Tuesday”) or correct it.
  • In the chat or through the MCP: ask it to change its tone or what it shows you.
  • Reinstall the Slack app if @costory doesn’t respond.

Memory

A Scout remembers in two ways:
  • Events. When it finishes an investigation, it can record what it found as an event. Events show on the cost timeline next to deploys, in the Events page, and through list_events in the Costory MCP. Anyone looking at a chart later sees what the Scout found and when. See Events.
  • Its instructions. A correction like “don’t comment on staging, focus on production” can update the Scout’s instructions, so it applies to every later run.
The Scout’s memory is a dashboard (Open memory). You can edit it by hand, but it’s better to steer the Scout through the thread or its instructions and let it keep the dashboard itself.

What a Scout can and can’t change

  • It reads your cost data. It never gets write access to your cloud accounts or your code.
  • Inside Costory, it can create or update alerts, reports and dashboards, and it always asks you before it does.
  • It recommends. Your team, or your coding agent, applies the change.

Next step

Alerts

What a Scout reads: alerts that fire on a condition

Cost Reports

What a Scout reads: scheduled reports and digests

Costory MCP

Create and edit Scouts from Claude or Cursor
Last modified on November 19, 2026