> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/features/cost-loops/viewing-cost-loop-data.md).

# Viewing Cost Loop Data

Learn where your Cost Loop spend appears in North, and how much detail each provider gives you.

Cost Loop spend appears in three places: your homepage, Streams, and Visibility. Each one answers a different question.

| Surface    | What it answers                                                          |
| ---------- | ------------------------------------------------------------------------ |
| Homepage   | What am I spending this month, per provider?                             |
| Streams    | How does this spend allocate across my business, and what is it made of? |
| Visibility | How does this spend compare and trend across time periods?               |

## Homepage

Each connected Cost Loop gets its own card, below the alert tiles. The card carries the connection name you chose during setup.

Every card shows:

* **MTD Spend**, month-to-date spend for that provider.
* A sparkline comparing the previous month against this month, split by a marker between the two.
* A gear icon, which opens that connection's settings.
* A bell icon, which opens alerts for that provider.

## Streams

Streams is where Cost Loop spend is allocated and broken apart. A Streams view groups your cloud streams and business units into a single allocation model, and a Cost Loop can be part of that model.

### Adding Cost Loops to a View

When you create a view, a **Cost loops** control lists every connected loop, grouped by provider. Select the loops you want in this view. A view can carry your cloud account and any number of Cost Loops together.

### Splitting Cost Loop Spend

To see provider-specific spend, split your root by **Provider**. Once a loop is in a view, split its node to break the spend apart. Two splits matter most.

**Split by service** gives you the provider's own units of spend:

* **OpenAI** splits into models, at model-version granularity. For example `gpt-5.4-2026-03-05` and `gpt-5.6-luna` appear as separate nodes with their own cost.
* **Anthropic** splits into models the same way.
* **Snowflake** splits into its billing categories, such as Snowflake Compute, Snowflake Cloud Services, and Snowflake Serverless Task.

**Split by usage type** takes an AI model one level deeper, into the token classes you are billed for:

* **Cached input**
* **Input**
* **Output**

This is how you see what a cached read is actually saving you. Split a model by usage type and the cached input cost sits beside the uncached input cost for the same model.

## Visibility

Visibility puts Cost Loop spend beside your cloud spend on the same chart and in the same table.

### Selecting Cost Loops

A **Cost loops** control sits at the top right of the Explore, Compare, and Forecast tabs. It lists every connected loop, grouped by provider, and it is additive: whatever you select is added to the data presented on the page.

### Splitting and Filtering by Provider

Use the **Provider** dimension to separate Cost Loop spend from cloud spend, and one Cost Loop from another. Group by provider to see AWS, Snowflake, Anthropic, and OpenAI as their own series. Filter by provider to narrow the whole page to one of them.

### What You See

Cost Loop spend appears at service granularity, with both **Amortized cost** and **Unblended cost**.

* **OpenAI and Anthropic** models appear as services, named by model version.
* **Snowflake** appears as its billing categories.

{% hint style="info" %}
**A note on Claude models.** If you run Claude through Amazon Bedrock as well as through the Anthropic API, both appear in your service list, and they are separate lines. Bedrock usage is labelled with the Bedrock edition, for example `Claude Sonnet 4.5 (Amazon Bedrock Edition)`, and is part of your AWS spend. Anthropic Cost Loop usage carries the raw model name, for example `claude-sonnet-4-6`. Adding them together would not double count, but they are billed by two different providers and reach North by two different routes.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.north.cloud/docs/features/cost-loops/viewing-cost-loop-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.