Ask anything
“How much waste did the team find this week?” “Which portfolio is most off pace?” Plain English in, account-grounded answers out — with the numbers to back them.
[07/07]Flume
/ the product tour
Ask your account anything.
Flume is the team’s Generalist — ask anything about your account, generate structured reports, or plug your own AI into ROASt over MCP. Same model class as ChatGPT; the difference is the 74 ROASt tools underneath — and the guardrail that it never makes budget decisions on its own.
[01]Ask Flume
/ the in-app chat
The whole team, one conversation.
Flume reads your campaign data, portfolio settings and engine outputs through the same tools the agent team uses — so its answers come from your account, not from vibes.
Structured reports
Pre-built prompts for a Performance Review, Pacing Review, Recommendations, or Account Health Check — saved to the Documents sidebar, exportable as HTML or PDF, ready to forward to a client.
Never near the money
Flume can read everything and propose actions — but all budget and target recommendations come from the deterministic engine. An LLM never decides where your spend goes.
Honest metering. Flume turns are metered per plan tier — you
can see your usage in Settings, and the quota resets monthly. No surprise bills,
no per-token mystery maths.
[02]MCP
/ bring your own AI
Your AI as the controller. ROASt as the safety net.
Hand the controls to your own Claude, ChatGPT or Gemini via ROASt’s Model Context Protocol endpoint — the same tools Flume uses, under the same guardrails, driven from wherever you already work.
74 tools, inherited
46 read tools — campaigns, portfolios, goals, audits, reconciliation, briefs, keyword + creative analytics — plus 28 write tools covering budgets, goals, events, automation and pause applies. Mint a token in Settings → API Access, paste it into your MCP config, done.
Nothing skips the safety net
Writes route through the same staging + audit pipeline as the in-app Optimiser. Destructive deletes require an explicit confirm flag — refused otherwise. Your AI proposes; ROASt enforces.
Scoped tokens
Every token is minted with a capability scope — read-only, write, or full — and can be revoked at any time. Give a reporting bot read access without ever exposing a write surface.
Your subscription, your bill. MCP usage doesn’t debit your
Flume turn quota — your own Claude or ChatGPT subscription does the thinking,
ROASt provides the data layer and the guardrails. That’s the point: the
agentic era needs a control tower, not another chatbot.