Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vantage.sh/llms.txt

Use this file to discover all available pages before exploring further.

The FinOps Agent is an AI assistant that helps you understand and act on your cloud costs in plain language. It is available in two places, and the same agent powers both:

Vantage console

A dedicated, full-screen agent page with threaded, persistent conversations. Available to all customers, including free trials.

Slack

Tag @Vantage in any channel where the agent has been invited. Required for cost recommendation approvals and automation.
You can use the agent in two ways:
  • Ask questions: Get answers about your cloud spend (via the Vantage MCP) and how to use Vantage (via the Vantage Docs MCP).
  • Take action: Have the agent create and update Vantage resources (Cost Reports, Dashboards, Budgets, Virtual Tags, etc.), investigate cost anomalies, and—through Slack—automatically remediate cost optimization opportunities with optional approval workflows.
When enabled for automation in Slack, the FinOps Agent operates in three stages:

1. Scans

Your cloud environment for issues like unused or underutilized resources.

2. Identifies

Optimization opportunities and waste found within your environments.

3. Acts

To remediate issues on your behalf, while keeping track of any actions taken.
Pick the surface that fits how you want to work with the agent. Start In the Console for chat, threads, and Vantage resource creation. Use In Slack for cost recommendation approvals, automated remediation, and team collaboration.
https://mintcdn.com/vantage-39/dQz82CvBD_D4tRVs/agent-icon.svg?fit=max&auto=format&n=dQz82CvBD_D4tRVs&q=85&s=6afc2c187a301d997a2491455d6410cf

FinOps AI Prompt Guide

For a complete view of what you can ask the agent, plus best practices and ready-to-copy prompts, see the dedicated FinOps AI Prompt Guide.

​
In the Console

The console agent is a dedicated, full-screen page in the Vantage console where you can have ongoing conversations with the FinOps Agent. It is available to all Vantage customers, including users on free trials, and requires no setup.
1

Open the Agent page

From the Vantage console, click the Agent tab in the top navigation, or go directly to console.vantage.sh/agent.
2

Start a conversation

Type a question or request in plain language, then press Enter. The agent automatically names the conversation based on your first message and saves it to your sidebar so you can return to it later.
3

Continue or start new threads

Use the conversation sidebar on the left to revisit previous conversations or start a new one at any time. Each conversation is private to your Vantage user and respects your RBAC permissions.
For comprehensive prompting examples, see the FinOps AI Prompt Guide.

​
Conversations and Threads

Each conversation is a self-contained thread that captures your back-and-forth with the agent.
  • Auto-named: The agent names each new conversation based on your first message. You can rename a conversation at any time by clicking the ellipsis (…) next to it in the sidebar.
  • Persistent: Conversations are saved per user and retained according to your account’s data retention period. Return to any prior conversation to continue where you left off.
  • Private: Console conversations are visible only to your authenticated user. They are not shared with teammates and do not appear in Slack.
  • Scoped to your permissions: All agent responses respect your RBAC role and only access data you are authorized to view.
  • Resource-aware: The agent recognizes Vantage console URLs and resource tokens (Cost Reports, Folders, Dashboards, Virtual Tags, Budgets, Cost Alerts, anomalies, and more). Paste a link or token directly into your prompt and the agent will use it as context. For example, you can add a Cost Report URL into your prompt to scope the question: 
    What was the biggest change in cost between September 2025 and October 2025 in https://console.vantage.sh/go/rprt_xyz789abc123def4? What resources contributed?
  • File-friendly: The agent currently accepts text-based file inputs, including CSVs. Support for additional file types is planned.
  • Audited: Any Cost Report, Dashboard, Virtual Tag, Budget, or other asset the agent creates or updates on your behalf is attributed to your user. Audit log entries reflect actions taken by the agent as if you performed them yourself. View these in the Vantage Audit Log.

​
In Slack

Slack is required if you want the agent to send recommendation notifications, run automated remediation, or collaborate with your team in shared channels. The console agent works without Slack.

​
Set Up the Slack Integration

Before starting, ensure you meet the following requirements for automation:
The Slack FinOps Agent is available to paying Vantage customers. The Agent is not available to the free tier.To learn more about Vantage plans, visit the Vantage pricing page.
1

Access the onboarding wizard

From the Vantage console, navigate to the Recommendations tab. A banner is displayed at the top. Click Get Started. (If you dismiss the prompt, click FinOps Agent.)
You can also access the FinOps Agent settings page to open the onboarding workflow.
2

Configure the Slack integration

The agent sends notifications directly to your Slack workspace.
  • If you’ve already installed the Vantage Slack integration for Cost Report notifications or alerts, you’ll be prompted to update your permissions to enable the agent.
  • If you haven’t installed the Slack integration yet, you’ll be prompted to log in to your workspace.
Follow the on-screen instructions to complete the Slack authorization. When prompted, select a channel where Vantage will post action approvals and recommendations.
If no channels appear in the selection list, you must first invite the @Vantage app to a Slack channel using the /invite @Vantage command in Slack. Once invited, the channel will appear in the list for selection.
3

Select recommendation types and approval workflows

For Automation Preference, select one of the following options:
  • Autonomous: The agent acts immediately.
  • Owner Approval: Your team approves each recommendation action sent via Slack.
Your selection applies to every enabled recommendation type. Select which recommendation types you’d like the agent to monitor (e.g., Compute Savings Plans, Database Savings Plans, Redshift Reserved Instances).For detailed information about how the approval workflow operates, see Approval Workflow.
4

Configure provider permissions

To enable the agent to take actions on your behalf, you may need to add additional provider permissions. If your AWS access credentials are already configured in Vantage, this step is automatically completed and you can proceed to the next step. If required, the onboarding wizard will display instructions for updating your AWS permissions using the AWS CLI, Terraform, or the IAM Console. After updating your permissions, click Complete Setup to continue.
You can navigate between onboarding steps using the stepper navigation on the left side of the screen to review or modify previous steps.
5

Complete onboarding

Once all steps are complete, a confirmation screen is displayed. The Slack-based FinOps Agent is now active and ready to use. An introductory message is sent to the channel you selected during onboarding.
6

Invite the agent to Slack channels

Invite the agent to additional channels at any time after onboarding using the /invite @Vantage command. Once invited, the FinOps Agent will introduce itself and explain its capabilities. You can invoke the agent by tagging @Vantage in any channel where it’s present, including in threads.

​
Update Slack Settings

After onboarding, you can change the connected Slack channel directly from the FinOps Agent settings page without needing to re-onboard. If the Slack integration needs re-authorization, a prompt is displayed on the settings page with instructions to reconnect.

​
Interact with the Agent

Tag @Vantage directly to interact with the agent in Slack. The agent only responds when explicitly mentioned. This applies to both new conversations and follow-up replies in threads.
For general help on using Slack, such as how to mention users or apps, create threads, or use commands, see the Slack Help Center.
In a Slack channel, tag the agent directly to start a conversation: 
@Vantage What was our AWS EC2 spend last month?
The FinOps Agent will reply in the thread: 
Last month's AWS EC2 spend was $3,240...
Whenever you ask follow-up questions, be sure to tag @Vantage in your reply so the agent is notified. If you do not tag @Vantage the agent will not reply: 
Reply in thread:

@Vantage Can you show me the top three regions by EC2 spend?
Keep in mind that if multiple people are conversing in the same channel or thread, anyone can prompt @Vantage, but the FinOps Agent will only respond with information relevant to the identity and permissions of the user issuing the prompt.
Slack threads and console conversations are independent. Messages and history do not cross over between the two surfaces.

​
Investigate Cost Anomalies

When Cost Anomaly Alerts are sent to Slack, the FinOps Agent can automatically investigate the root cause of a cost spike. If the FinOps Agent is enabled, anomaly alert notifications in Slack include an Investigate Anomaly button alongside the existing View Anomaly link.
AWS Costs - Cost Anomaly Alerts
1 New Anomaly
Amazon Elastic Compute Cloud - Compute - Compute Instance
Increased by 343.54
Detected On
Feb 26, 2026 UTC
Occurred On
Feb 25, 2026 UTC
Click Investigate Anomaly to start an investigation. The agent runs a multi-step analysis directly in the Slack thread:
1

Fetches anomaly details

The agent retrieves the anomaly’s metadata, including the provider, service, cost category, observed amount, prior-period amount, 7-day rolling average, and attributed resources.
2

Gathers supporting data

If specific resources are attributed to the anomaly, the agent retrieves details for each resource (instance type, region, account, per-category cost breakdown). It also loads the parent Cost Report’s title, filters, and groupings for context.
3

Queries costs around the anomaly

The agent pulls daily cost data for the affected provider and service, centered on the anomaly date (7 days before and after), to show exactly when the spike began and whether it has recovered.
4

Presents findings

The agent synthesizes everything into a structured summary:
  • What happened — The service, provider, cost change (with percentage), and detection date.
  • Cost trend — A day-by-day breakdown showing the spike and recovery pattern.
  • Attributed resources — Resources identified as contributors, with metadata like instance type and region.
  • Report context — The Cost Report name and any base filters, so you understand the monitoring scope.
  • Console links — Direct links to the anomaly and Cost Report in the Vantage console.
You can also trigger an investigation by tagging @Vantage in any Slack channel and asking about a cost anomaly or sharing an anomaly alert token. 
@Vantage Can you investigate the anomaly on my AWS EC2 report from yesterday?

​
Approval Workflow

The console agent can describe and explain recommendations but cannot take remediation actions at this time.
When the FinOps Agent finds a savings opportunity, it sends a message to your designated Slack channel, similar to the below example:
💰 Compute Plan Recommendations Available

Based on your recent usage, I found that your account could save by purchasing an AWS Compute Savings Plan. Here are savings options for a 1-year, no upfront payment savings plan:

1️⃣ Conservative: 0.31/hr coverage — Est. 112/mo savings
2️⃣ Moderate: 0.46/hr coverage — Est. 168/mo savings
3️⃣ Aggressive: 0.61/hr coverage — Est. 224/mo savings

The agent curates messages for each recommendation type it detects and provides multiple options for approval when appropriate. When the FinOps Agent proceeds to take an action (either after approval or autonomously), it follows these steps:
  1. The agent posts a message in the Slack channel where recommendations are directed, outlining its action plan. An explicit click is required to initiate the action.
  2. The agent executes the action in your cloud environment.
  3. An entry is logged to the Vantage Audit Log for full transparency and traceability.
  4. The agent reports back in the Slack thread with a summary of what was completed and the estimated savings achieved.

​
Frequently Asked Questions

Below are categorized answers to frequently asked questions.

​
Getting Started

Chatting with the agent is available to all Vantage customers, including users on free trials. Automated cost remediation through the Slack approval workflow is available to paying Vantage customers only.
Yes. You can use the FinOps Agent in the console and in Slack to ask questions about your costs and Vantage in natural language. Automated cost remediation is not available on free trials.
Slack is required if you want the agent to send cost recommendation notifications, run automated remediation, or have your team collaborate with the agent in shared channels. The console agent works without Slack.
Yes. The FinOps Agent is also available as a dedicated page in the Vantage console at console.vantage.sh/agent. Additional surfaces, such as Microsoft Teams, are planned for the future.
No. Console conversations are scoped to your authenticated user and are not visible in Slack. Slack threads—especially those across multiple users in shared channels—are not carried over into the console.
There are currently no usage limits on the in-console FinOps Agent.

​
Using the Agent

Yes. Conversations in the console are stored and scoped per user. The agent automatically names each conversation based on your first message; you can rename it at any time by clicking the ellipsis (…) next to the conversation in the sidebar. Conversations are retained for the duration of your account’s data retention period.
Cost Reports, Dashboards, Virtual Tags, Budgets, and other resources the agent creates or updates are attributed to your user. Audit log entries reflect actions taken by the agent on your behalf, just as if you had created or updated the resource yourself. See the Vantage Audit Log for details.
During onboarding, you’ll select at least one Slack channel to invite the agent to. You can invite the agent to additional channels at any time using the /invite @Vantage command. Once invited, you can interact with the agent by tagging @Vantage.
Once integrated, you can add the FinOps Agent to as many channels as you like. Your cost recommendations will always be sent to the channel designated for approvals during onboarding.
At this time, the FinOps Agent can only be messaged in Slack channels. Support for direct messaging is planned. The console agent provides a private, per-user chat experience today.
The console agent can accept text-based file inputs, including CSVs. Support for additional file types is planned for the future. The agent responds in plain text and, in Slack, with Slack Blocks for richer formatting like tables.
Not at this time. The agent’s behavior is consistent across all customers. Vantage continuously refines the agent’s prompts and tooling based on customer feedback.
No. Vantage selects the model based on response accuracy and may update it at any time without notice.
Yes. Ask the agent—in the console or in Slack—for details about any recommendation. The agent will provide context about the usage patterns, historical data, and calculations that led to the recommendation. This transparency helps you make informed decisions about which optimizations to approve.
Yes. The FinOps Agent is fully aware of your existing Reserved Instances and Savings Plans commitments. All recommendations are calculated based on your uncovered usage after applying existing commitments, ensuring you don’t over-commit or duplicate coverage.
Yes. While the Vantage console UI is currently available in English only, the FinOps Agent can understand questions and provide responses in other languages when you interact with it both in Slack and on the Agent console page. You can ask questions about your costs in your preferred language.
The FinOps Agent uses Vantage’s MCP servers (Vantage MCP and Vantage Docs MCP) under the hood to access your cost data and documentation. However, the agent provides a pre-configured experience—available in both the Vantage console and Slack—that doesn’t require you to set up your own MCP client.Vantage MCP: Allows you to connect your own AI tools (like Claude, Cursor, or Goose) directly to Vantage’s APIs to query cost data and create reports using natural language. You have full control over which AI tool you use and how you interact with it.FinOps Agent: A ready-to-use AI assistant built into the Vantage console and Slack that uses the MCP servers on your behalf. The agent can answer questions, create reports, and—through Slack—take action on savings recommendations, all without requiring you to configure an MCP client. It’s designed for teams who want an immediate, integrated solution without the setup overhead.Both options respect your RBAC permissions and provide access to the same underlying Vantage data and APIs.

​
Permissions and Security

Only Vantage account Owners are allowed to approve cost remediation actions in Slack.
In the console, the agent uses your existing Vantage session—no additional authentication is required.In Slack, the agent looks up the email of the Slack user against the list of authenticated Vantage users. The email of your Slack user must match the email of your Vantage user in order for authentication to be successful. If this is not the case, please reach out to support@vantage.sh for assistance.
Yes, in order to use the FinOps Agent, you must be a registered user in Vantage.
Yes. The agent inherits the roles and permissions of your Vantage user and can only access or act on data you are authorized to view.
No, your data will not be used to train models. The agent only uses data fetched directly from your account via Vantage’s APIs. All enhancements to the model will be done as prompt engineering from Vantage engineering teams to address feedback from customers and provide more guided answers.
The Vantage Slack app will request the following permissions in order to perform its functions:
  • Content and info about channels & conversations
    • View messages and other content in direct and group direct messages that “Vantage” has been added to
    • View basic information about public channels in your workspace
    • View basic information about private channels that “Vantage” has been added to
  • Content and info about your workspace
    • View people in your workspace
    • View email addresses of people in your workspace
  • Perform actions in channels & conversations
    • View messages that directly mention @vantage in conversations that the app is in
    • Join public channels in your workspace
    • Send messages as @vantage
    • Start direct messages with people
  • Perform actions in your workspace
    • Allow “Vantage” to act as your App Agent
    • Add shortcuts and/or slash commands that people can use

​
Actions and Automation

When the FinOps Agent proceeds to take an action (either after approval or autonomously), it follows these steps:
  1. The agent posts a message in the Slack channel where recommendations are directed, outlining its action plan. An explicit click is required to initiate the action.
  2. The agent executes the action in your cloud environment.
  3. An entry is logged to the Vantage Audit Log for full transparency and traceability.
  4. The agent reports back in the Slack thread with a summary of what was completed and the estimated savings achieved.
Customers can opt to disable automated actions at any time. Many optimizations (like rightsizing or Savings Plans) will be reversible within specified periods, while some purchases (i.e., RIs) are permanent. Audit logs provide traceability for governance.Certain meaningful actions will also be queued for later in the day vs instantaneously to allow a human to potentially intervene. For example, if you are making a commitment for a Savings Plan for hundreds of thousands or millions of dollars, it will put into place an arbitrary delay in case you decide to reverse it.All actions are logged in the Vantage Audit Log for full transparency and traceability, allowing you to review what was changed and when.
Currently, the FinOps Agent only supports automated remediation actions for AWS. Future provider support is planned for Azure, GCP, Datadog, and more.
You can view all actions taken by the FinOps Agent in AWS CloudTrail by filtering for events initiated by the IAM role that the FinOps Agent assumed. This allows you to see exactly what changes were made, when they occurred, and which role was used to execute them.
Within the Vantage Audit Logs, you will be able to see the following:
  • Time the recommendation was provided
  • Time the recommendation was approved
  • Vantage User that approved the remediation
  • What Resources were altered as a part of the recommendation remediation
  • Time the action was taken in the cloud provider

​
Configuration and Management

Yes, once the FinOps Agent is configured, you will have access to an agent settings page where you can opt in and out of all offered recommendations.
You can pause the FinOps Agent’s automated actions and recommendation notifications at any time through the Vantage console by turning off a particular recommendation or all recommendations at once. This might be useful during periods of significant infrastructure changes, migrations, or organizational transitions. You can resume the agent whenever you’re ready.
Yes, you can change the connected Slack channel at any time from the FinOps Agent settings page without needing to re-onboard. See Update Slack Settings for details.
If the designated Slack channel is deleted, the FinOps Agent will no longer be able to send notifications about new recommendations or completed actions. If you have the Vantage Slack application added to other channels, you will be notified that a new channel needs to be set. You will also see your Slack integration in an Error state within the Vantage console. You’ll need to reconfigure the FinOps Agent’s Slack integration and designate a new channel through the Vantage console to resume receiving notifications.
If you have multiple integrations of the same provider, the FinOps Agent will provide additional context about which integration it is acting on.
You can provide feedback in two ways:
  • Quick feedback in Slack: Add a thumbs up or thumbs down emoji reaction to any agent message in Slack.
  • Detailed feedback (console or Slack): Tell the agent you have feedback to share. The agent will use the submit-user-feedback tool from the Vantage MCP, and your message will be sent directly to the Vantage team for review.
This depends on your organization’s Slack settings. As the application is currently under Marketplace review from Slack, this may require elevated permissions, such as Workspace Owner, in order to install. Check with your Slack Admin if you encounter any permission errors installing the Vantage app.
Vantage is currently in contact with Slack to have the application approved for downloading through the Slack Marketplace.
Yes, the OAuth URL for installing the app is created through the Vantage console, so any user that is looking to install the Vantage Slack App will need to do this through the Vantage Console until it is approved in the Slack Marketplace.
Autopilot will continue to function as normal. If you are currently set to “requires approval” and you integrate the agent into your Slack, you will begin to get notifications via Slack as well.The configuration settings for Autopilot have moved to the agent section of the settings page, and the graphs for AWS Compute and the additional RI services will remain unchanged. Autopilot can be accessed from Financial Planning > Autopilot in the navigation menu.
The Vantage FinOps Agent is scoped to the account your Vantage user has direct access to. In an MSP setup, this means you can use the agent within your MSP Management account, but not across child Managed accounts by default. For automated remediation through Slack, the same scoping applies—only resources in your Management account are remediated.To use the agent within a specific Managed account, masquerade into that account and access the agent there. Any questions you ask while masquerading are scoped to your user and are not visible to the Managed account.

​
Technical Details

The FinOps Agent is powered by OpenAI and Cloudflare, providing the AI capabilities and infrastructure needed for natural language processing and cloud cost optimization.