> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/ai.md).

# AI

See what your organization spends on AI tools, and where that cost belongs.

The AI area puts your AI spend next to your Microsoft license cost. Bsure collects cost and seats from your AI vendors every night and matches each vendor account to a person in Entra ID. Then it breaks the cost down by the org properties you already use, such as department or cost center.

It is designed to answer simple but important questions:

* What do we spend on AI tools each month, and on which vendor?
* Which departments and people does that cost belong to?
* Which vendor accounts can't be tied to a person?

***

## Overview

The AI area has four pages.

### Cost Overview

Your AI cost for the month per vendor, org property and person, with a trend over time. See [Cost Overview](https://docs.bsure.io/user-guides/ai/cost-overview.md).

### Cost Allocation

A Power BI report that shows where your AI cost belongs, broken down by department or any other org property. See [Cost Allocation](https://docs.bsure.io/user-guides/ai/cost-allocation.md).

### Agents

The Agents report, which moves here from **Power BI → Security** once the AI area is turned on. See [Agents](https://docs.bsure.io/user-guides/ai/agents.md).

### Sources

The vendor accounts Bsure collects AI cost from. A Super Admin connects them here and checks that Bsure can still read them. See [Sources](https://docs.bsure.io/user-guides/ai/sources.md).

{% hint style="info" %}
**Why you might not see the AI area.** AI Cost is an add-on, and Bsure turns it on per organization.

* Without the add-on, Cost Overview, Cost Allocation and Sources show **The AI add-on is not active**. To add it, contact your Bsure account manager, or book a meeting with Bsure support. Agents still opens.
* To open the AI area, a user needs the **AI** permission in [Users Management](https://docs.bsure.io/user-guides/settings/configuration/users-management.md). Super Admins always have it.
  {% endhint %}

## Supported vendors

You can connect **GitHub Copilot**, one source per GitHub enterprise or standalone organization. All amounts are in USD, excluding tax, the currency the vendors report in.

## Where to go next

* **Connect your first vendor** → [Sources](https://docs.bsure.io/user-guides/ai/sources.md)
* **Read this month's AI cost** → [Cost Overview](https://docs.bsure.io/user-guides/ai/cost-overview.md)
* **Compare with your Microsoft license cost** → [Cost Dashboard](https://docs.bsure.io/user-guides/power-bi/microsoft-licenses/cost-dashboard.md)
* **Give a colleague access** → [Users Management](https://docs.bsure.io/user-guides/settings/configuration/users-management.md)

Use AI. Know what it costs. Bsure.


---

# 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.bsure.io/user-guides/ai.md?ask=<question>&goal=<user_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.
