> For the complete documentation index, see [llms.txt](https://boundaryai.gitbook.io/boundaryai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boundaryai.gitbook.io/boundaryai-docs/bringing-in-your-feedback/ai-visibility.md).

# AI Visibility

People increasingly form opinions by asking an AI assistant, not by reading review pages. **AI Visibility** measures what those assistants actually say about you: it puts a set of prompts to the models you choose, brings the answers back into a Feedback Group, and scores how visible, and how well described, your brand is in them.

AI Visibility is its own source type, alongside surveys, uploads, connectors, and [Social Listening](/boundaryai-docs/bringing-in-your-feedback/social-listening.md) agents. It is created through the same agent wizard and runs on the same Web & Social Media Credits, but what it collects and the analytics built on top are distinct, so it appears as its own category across the app.

***

### Supported assistants

**Claude, ChatGPT, Gemini, Perplexity, Grok, DeepSeek, and Mistral.** One agent can query several at once, which is the point: the assistants often disagree, and you want to know which ones tell your story well and which ones don't.

***

### When to use it

* You want to know **what an assistant tells a prospect** who asks *"what's the best project-management tool?"* or *"is Brand X any good?"*
* You want your **share of voice** against competitors inside AI answers, not just in search results.
* You want to catch **wrong or outdated claims** that assistants repeat about your product, and see which web sources they lean on.
* You want a **trend**: re-run the same prompts on a schedule and watch your visibility move as your content and coverage change.

***

### Setting up an AI Visibility agent

Create an agent and pick one or more AI assistants in the Sources step; the wizard switches to a **brand-first flow**:

1. **Brand**: the name the prompts should ask about.
2. **Competitors** *(optional)*: naming them unlocks share-of-voice in the scorecard.
3. **Category**: what you compete in (say, *"project-management software"*). The wizard uses all three to write a realistic prompt set for you.

Power users can skip the generated prompts and supply **custom prompts** instead.

Everything else works like any other agent: choose **Run Once**, **Scheduled**, or **Ongoing**, and an intensity tier. For AI assistants the tiers are **12 / 25 / 50 answers per prompt** (Standard / High / Extra high). Runs deduct Web & Social Media Credits, and failed runs refund automatically.

***

### What comes back

Each answer is stored as a response, with metadata you can segment by:

* The assistant's **answer** as the response text.
* A **verbatim source snippet**: text pulled from the web page the assistant relied on, never the assistant's own paraphrase, so every claim is traceable.
* The **model**, the **prompt**, and the **cited domain**.

***

### The AI Visibility scorecard

The source's qualitative overview gains a scorecard: how often your brand appears in answers, the sentiment of those mentions, and, when you configured competitors, your **share of voice** against them. A per-model drill-down opens the underlying answers so you can read exactly what each assistant said, next to the source it cited.

***

### Where it fits in the rest of BAI Analytics

AI Visibility sources are listed under their own category in the feedback hub and on Feedback Group pages, separate from Web & Social sources. Beyond that they behave like any source: answers feed **Grouped Themes**, monitors with auto-coverage on watch them ([Custom Monitoring](/boundaryai-docs/analysing-your-feedback/custom-monitoring.md)), and they roll into **reports**. Put one in an evolution-tracked group and re-run it on a schedule to turn the scorecard into a period-over-period trend.

***

### Best practices

* **Name your real competitors.** Share of voice is the scorecard's most decision-ready number, and it only exists if the wizard knows who to compare you against.
* **Keep the prompt set stable when you want a trend.** Changing prompts between runs changes what's being measured; add new prompts as a second agent instead.
* **Start at Standard intensity.** 12 answers per prompt is usually enough to see the pattern; scale up when you need statistical comfort, not before.
* **Read the cited domains.** If assistants keep citing a stale comparison page or an old review thread, that page, not the assistant, is what needs fixing.