Skip to main content
Vantage integrates with a CoreWeave organization using an API access token. CoreWeave’s FOCUS billing export is in public preview and reports usage, not dollars, so Vantage prices each hour as billable usage times a rate. The default rate is CoreWeave’s on-demand list price for that SKU, and you can replace it with your own rate. The export currently covers CoreWeave Kubernetes Service (CKS): GPU and CPU instances, storage, and public IP addresses. Vantage picks up additional CoreWeave products as CoreWeave adds them to the export. Vantage imports that usage in the unit CoreWeave reports: Instance-Hours for GPU and CPU instances, GPU-Hours for single-GPU inference SKUs, vCPU-Hours, GiB-Hours for storage, and IP-Hours for public IP addresses. GPU instances are measured per instance, so one hour of an 8-GPU instance is one instance hour. See Usage-Based Reporting for how to chart usage.

​
CoreWeave Permissions

A CoreWeave API access token authenticates the user who creates it. The token does not have roles of its own. That user needs the Observability Viewer and Billing Viewer roles in an IAM access policy. Observability Viewer lets Vantage read CoreWeave billing metrics. Billing Viewer lets Vantage read the FOCUS billing export. The CoreWeave organization also needs the FOCUS billing export enabled. Vantage uses the token to check the connection and to import usage. Vantage cannot create, change, or delete clusters, workloads, or any other CoreWeave resources. If the connection fails with an authorization error after those roles are assigned, contact CoreWeave Support and ask them to enable FOCUS export for the organization.

​
Connect Your CoreWeave Account

​
Prerequisites

  • You must have a Vantage Organization Owner or Integration Owner role to add or remove this integration or change its rates. See the Role-Based Access Control documentation for details.
  • The CoreWeave user who creates the token needs Access Token User to create it, and Observability Viewer and Billing Viewer so Vantage can read metrics and the FOCUS export. An organization administrator assigns those roles in an IAM access policy. The token uses that user’s roles. See CoreWeave’s IAM roles and access policies documentation.
  • FOCUS billing export must be enabled for the CoreWeave organization. If the connection fails with an authorization error after Billing Viewer is assigned, contact CoreWeave Support and ask them to enable it. CoreWeave’s FOCUS documentation describes this prerequisite.
  • Create a free Vantage account, then follow the steps below to integrate CoreWeave costs.
If your organization restricts access to the provider by IP address, add the following Vantage IP addresses to your provider’s allowlist:
  • 54.87.66.45
  • 3.95.43.133
  • 54.162.3.72
  • 44.199.143.63
  • 3.218.103.23

​
Create the Connection

1
In CoreWeave, grant Observability Viewer and Billing Viewer to the user who will create the token. Follow CoreWeave’s access policies documentation. Role descriptions are in CoreWeave’s IAM roles documentation. That user also needs Access Token User to create a token. The token uses that user’s roles.
2
Confirm FOCUS billing export is enabled for the organization. If you get an authorization error after those roles are assigned, contact CoreWeave Support and ask them to enable it.
3
Create an API access token and copy the Token Secret, following CoreWeave’s API access tokens documentation.
CoreWeave shows the token secret only once. Save it before you close the dialog.
4
From the top navigation in Vantage, click Settings.
5
On the left navigation, select Integrations and then CoreWeave.
6
Click Add Account. If you already have a CoreWeave connection, open the Connect tab and click Add Another Account.
7
Complete the form:
  • API Key: Paste the CoreWeave token secret.
  • Description: Enter a name to identify the CoreWeave account or workspace these credentials belong to.
8
Click Connect Account.
Vantage checks that the token can read CoreWeave billing data before it starts importing. After you click Connect Account, the integration status changes to Importing. On initial connection, Vantage imports usage back to January 2026, the earliest month CoreWeave’s FOCUS export provides, within your account’s retention period. See the Integration Status documentation for details. Each API access token belongs to one CoreWeave organization. Connect each organization with its own token and description. Rates are set separately for each connection.
As soon as costs are processed, they are available on your All Resources Cost Report. If you remove the CoreWeave integration, all costs associated with that connection are removed from the Vantage console. Removing the integration leaves the API access token in CoreWeave. Delete the token in the CoreWeave Cloud Console when you no longer need it.

​
Next Steps - Manage Workspace Access

Once the import is complete and the integration status changes to Stable, you can select which workspaces this integration is associated with. See the Workspaces documentation for information.

​
Update the API Key

On the connection’s Manage Connection page, Update API Key replaces the stored token. Create the replacement the same way: the user who creates it needs Observability Viewer and Billing Viewer. The next daily import uses the new token.

​
CoreWeave Rates

Each amount in Vantage is billable usage times the rate for that SKU. Open Rates from the connection:
1
From the top navigation, click Settings.
2
On the left navigation, select Integrations and then CoreWeave.
3
On the Manage tab, click the account description for the connection you want to price. The Manage Connection page opens.
4
On that page, go to the Rates section.
  • Leave a rate blank to use CoreWeave’s on-demand list price. The page shows the date of the price list in use, and links to CoreWeave’s pricing page.
  • A rate you enter prices all of that SKU’s usage, including past months. Enter 0 to mark a SKU as free.
  • Storage and public IP rates are entered per month, the way CoreWeave prices them. Vantage converts those rates to hourly rates using 730 hours per month.
  • SKUs in your usage are listed first, marked In your usage. The rest of the price list is behind Show … SKUs from CoreWeave’s price map.
  • Click Save. Reports refresh shortly after you save. If a refresh cannot be queued, the page asks you to save again.
SKUs marked Contact sales or Not listed have no list price, so they show usage with no cost until you enter a rate. Each SKU has one rate, including reserved, spot, and flex usage. Vantage dates each hour in UTC, and CoreWeave’s billing month ends at 5:00 PM ET, so a total at a month boundary can differ from the invoice.

​
Data Refresh

See the provider data refresh documentation for information on when data for each provider refreshes in Vantage. CoreWeave data refreshes once daily. During the first five days of each month, Vantage also refreshes the previous month. CoreWeave’s export runs a few hours behind, and its most recent hours can change slightly until they settle.

​
CoreWeave Reporting Dimensions

On CoreWeave Cost Reports, you can filter and group across several dimensions:
  • Organization (the CoreWeave organization ID)
  • Cluster (the CoreWeave cluster ID)
  • Service (the FOCUS service name, such as GPU Compute or Object Storage)
  • SKU (the CoreWeave SKU, such as gd-8xh100ib-i128)
  • Product Family (GPU Compute, CPU Compute, Storage, Network, or Other)
  • Region (the CoreWeave region, such as us-east-04)
  • Charge Type (Usage)
  • Tag (coreweave:cluster_name, when the export includes a cluster name)
In the Group By menu, Organization, Cluster, SKU, and Product Family are labeled Billing Account, Account, Category, and Subcategory. CoreWeave costs include the following provider tag, which Vantage creates from the export. It is available for filtering and grouping alongside any Virtual Tags you create:

​
Kubernetes Agent

Pod-level costs from the Vantage Kubernetes agent appear under the Kubernetes provider. When that agent is running on the same CoreWeave clusters, with GPU rate annotations, those costs cover the same nodes this integration imports. Keep the CoreWeave and Kubernetes providers in separate Cost Reports for those clusters: use Kubernetes for namespace, pod, and label allocation, and CoreWeave for total CoreWeave spend. See Avoid Double Counting Costs in Cost Reports.