> 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 four places: your homepage, Streams, Visibility, and Noros. 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? | | Noros | The questions you ask about this spend in chat. | ## 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 bell icon, which opens alerts for that provider. * A gear icon, which opens that connection's settings. ## 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 by **Service** to see the provider's own units of spend. Most providers support more splits below that. The table in [What Each Provider Reports](/docs/features/cost-loops/viewing-cost-loop-data.md#what-each-provider-reports) lists them for each provider. For example, split an OpenAI model by **Usage Type** to see its cached input cost beside its uncached input cost. ## 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, OpenAI, and Datadog 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**. See [What Each Provider Reports](/docs/features/cost-loops/viewing-cost-loop-data.md#what-each-provider-reports) for what the services are for each provider. {% 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 %} {% hint style="info" %} **A note on Datadog hourly figures.** Some Datadog hourly figures in Visibility are estimates. Datadog bills some products on a P99 (99th percentile) basis, and those products have no hourly split. North spreads their cost evenly through the day. Daily and monthly totals do not change. When this applies, the Explore and Compare tabs show a **Datadog hourly is estimated** note. {% endhint %} ## Noros Noros answers questions about Cost Loop spend the same way it answers questions about your cloud spend. Open **Noros AI**. Ask Noros about a Cost Loop provider by name, for example "Show my Datadog cost." See [Noros AI](https://docs.noros.ai) for what else you can ask. ## What Each Provider Reports Each Cost Loop provider reports spend in its own units. In Streams and Visibility, those units appear as services. Most providers support more splits below the service. | Provider | Services | Other useful splits | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | OpenAI | Models, by version, for example `gpt-5.4-2026-03-05` | | | Anthropic (Claude Platform) | Models, by version, for example `claude-sonnet-4-6`. Tool charges appear under their own names, for example `web_search` and `code_execution`. | | | Anthropic (Enterprise) | Models, by version, for example `claude-opus-5`. Tool charges appear under their own names, for example `web_search` and `code_execution`. | | | Snowflake | Billing categories, for example Snowflake Compute and Snowflake Cloud Services | | | Datadog | Products, for example Infra Hosts and Indexed Logs (15 Day Retention) | | --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.north.cloud/docs/features/cost-loops/viewing-cost-loop-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.