> ## 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.

# Baseten

> Learn how to integrate Vantage with Baseten to track AI inference, training, and Model API costs.

Vantage integrates with your Baseten account using an API key to ingest cost and usage data through the Baseten [Billing Usage Summary API](https://docs.baseten.co/reference/management-api/billing/gets-billing-usage-summary-for-a-date-range). Vantage retrieves detailed cost and usage data broken down by product line (Dedicated Inference, Training, and Model APIs), model deployment, instance type, environment, and model. [Usage data](/usage_based_reporting) is available for Baseten, measured in hours for Dedicated Inference and Training, and in tokens for Model APIs.

## Baseten Permissions

Vantage connects to Baseten using an API key and validates access by reading billing usage summary data. Vantage cannot deploy models, trigger inference or training jobs, or perform any actions that incur costs in your Baseten account.

You must be a Team Admin (or organization Admin) to create a Team API key. See the [Baseten API keys](https://docs.baseten.co/organization/api-keys) and [Teams](https://docs.baseten.co/organization/teams) documentation for details. It's best practice to create a dedicated Team API key for Vantage and rotate it according to your organization's security policy.

To access the Baseten Billing Usage Summary API, the Team API key must be created with the **Manage and call all team models** permission level. This grants additional permissions beyond what Vantage uses; however, Vantage only reads data from the Billing Usage Summary API endpoint related to usage, and will never perform any other actions. Baseten does not currently support fine-grained permissions for Team API keys. We recommend submitting a feature request to Baseten for improved permission scoping, and Vantage will adopt fine-grained permissions if this becomes available.

## Connect Your Baseten Account

### Prerequisites

* You must have a Vantage **Organization Owner** or **Integration Owner** role to add or remove this integration. See the [Role-Based Access Control](/rbac) documentation for details.
* You must be a Team Admin (or organization Admin) in Baseten to create a Team API key.
* [Create a free Vantage account](https://console.vantage.sh/signup), then follow the steps below to integrate Baseten costs.

### Create the Connection

<Steps>
  <Step>
    Sign in to the [Baseten console](https://app.baseten.co) and click **API Keys** in the sidebar.
  </Step>

  <Step>
    Click **Create API key**.
  </Step>

  <Step>
    Give the key a descriptive name, select **Team** as the type, and click **Next**.
  </Step>

  <Step>
    Select **Manage and call all team models** as the permission level, then click **Create API key**.
  </Step>

  <Step>
    Copy the API key.

    <Warning>
      Baseten only shows the API key once. Save it securely before closing the dialog.
    </Warning>
  </Step>

  <Step>
    From the top navigation in Vantage, click **Settings**.
  </Step>

  <Step>
    On the left navigation, select **Integrations** > **Baseten**.
  </Step>

  <Step>
    The Baseten integrations page is displayed. Ensure you are on the **Connect** tab.
  </Step>

  <Step>
    Click **Add API Key** and complete the integration form:

    * **API Key**: Paste the Baseten Team API key.
    * **Description**: Enter a label to identify this Baseten account or workspace in Vantage. This value is used as the **Organization** dimension in Cost Report filters.
  </Step>

  <Step>
    Click **Connect Account**.
  </Step>
</Steps>

After clicking **Connect Account**, you will see the status of your integration change to **Importing** within the Vantage console. This status indicates that Vantage is actively importing your Baseten cost data. Vantage backfills up to six months of historical cost data upon initial connection. See the [Integration Status](/vantage_account#integration-status) documentation for details on integration statuses. You can connect multiple Baseten organizations, each with its own API key, as separate integrations in Vantage.

<Info>
  As soon as costs are processed, they will be available on your **All Resources** Cost Report. If you decide to remove your Baseten integration from Vantage, all costs associated with that Baseten API key will be removed from the Vantage console.
</Info>

### 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](/workspaces#manage-workspace-provider-integrations) documentation for information.

## Data Refresh

See the [provider data refresh documentation](/provider_data_refresh) for information on when data for each provider refreshes in Vantage. Baseten data refreshes once daily.

## Baseten Reporting Dimensions

On Baseten [Cost Reports](/cost_reports), you can filter and group across several dimensions:

* Organization (the description you enter when connecting the integration)
* Service (i.e., the Baseten product line, such as Dedicated Inference, Training, or Model APIs)
* Category (i.e., the model name)
* Subcategory (i.e., the instance type for Dedicated Inference and Training, such as `H100`; or the token type for Model APIs, such as Input Tokens, Cached Input Tokens, or Output Tokens)
* Resource (i.e., the deployment or job ID for Dedicated Inference and Training, or the model name for Model APIs)
* Charge Type (Usage or Credit)

In addition, Baseten costs include the following provider tags, which are automatically created by Vantage and available for filtering and grouping alongside any [Virtual Tags](/tagging) you create:

| Tag                           | Description                                                                     |
| ----------------------------- | ------------------------------------------------------------------------------- |
| `baseten:model_name`          | The model name associated with the usage                                        |
| `baseten:deployment`          | The deployment name for Dedicated Inference                                     |
| `baseten:instance_type`       | The instance type backing a dedicated deployment or training job (e.g., `H100`) |
| `baseten:environment`         | The Baseten environment name (e.g., `production`)                               |
| `baseten:resource_kind`       | The billable resource kind for Dedicated Inference (e.g., `MODEL_DEPLOYMENT`)   |
| `baseten:resource_id`         | The billable resource ID for Training jobs                                      |
| `baseten:kind`                | The resource kind for Training jobs                                             |
| `baseten:is_deleted`          | Whether the Training resource has been deleted                                  |
| `baseten:chain_id`            | The Chain ID when training is associated with a Chain                           |
| `baseten:chain_deployment_id` | The Chain deployment ID when present                                            |
| `baseten:chain_name`          | The Chain name when present                                                     |
| `baseten:model_family`        | The model family for Model APIs usage (e.g., `ZAI`)                             |

<Note>
  Historical cost attribution is preserved for deleted or torn-down deployments. The Baseten billing API continues to return deleted resources in the cost breakdown, so spend from a model deployment that has since been torn down still appears in your historical Baseten reports.
</Note>