An analysis is the central data unit of Share Of Model. Everything you read in dashboards or fetch through the API is produced by an analysis: a scoped, configured run that gathers signals from LLMs and search engines and turns them into metrics, perception clusters, and source lists. Analyses come in two flavours, depending on the module:Documentation Index
Fetch the complete documentation index at: https://docs.shareofmodel.ai/llms.txt
Use this file to discover all available pages before exploring further.
- Brand analyses — answer “what does the model think about my brand?” and produce awareness, perception, and source signals.
- Search projects — answer “where does my brand or domain appear when users search?” and produce visibility, ranking, and citation signals.
Scope
When you create an analysis, you define what is being studied. The exact fields differ by module, but the shape is the same:- Brand analysis
- Search project
| Field | Required | Notes |
|---|---|---|
| Brand | Yes | The brand under analysis. |
| Category | Yes | The market in which the brand competes. |
| Competitors | Yes | Exactly 3 competitors, used as the comparative landscape. |
| Attributes | Yes | Exactly 6 attributes used for perception scoring. |
| LLM models | Yes | Models to query (OpenAI, Google AI, Meta AI and Anthropic by default). |
| Regions | Optional | Up to 8 regions per analysis. Country-prefixed prompts are added per region. |
| Personas | Optional | Up to 5 personas per analysis. Each persona narrows the prompt audience. |
Scope drives credit usage. For brand analyses, credits scale as
regions × personas; for search, each tracked query costs a known number of credits per run. See the Credit System for the full breakdown.Collects
A collect is the result of one execution of an analysis. Each time the platform runs an analysis, it produces a new collect that holds the metrics for that run.- Multiple collects can be aggregated to read average performance across a window.
- Collects can also be compared to a previous set, to read evolution over time.
- A collect carries a status — only
FINISHEDcollects are usable for reading metrics.
- single collect — pass one ID in
collect_ids. - aggregated metrics — pass several IDs in
collect_ids. - evolution — also pass IDs in
prev_collect_idsto compare against an earlier window.
Lifecycle
An analysis goes through three states from creation to insight:| Status | What it means |
|---|---|
| Launching | The analysis has just been created and is being prepared (typically the first 15–20 minutes). Data is not yet available. |
| Collecting | Data is being gathered. Trends may shift as more data arrives. Read early signals with care. |
| Live | Data has stabilised and is ready for insights. |
Archiving and reactivation
Analyses can be archived for later reference and reactivated when needed.- Archived analyses don’t consume credits.
- Reactivating an analysis re-consumes credits based on its original scope.
- The period during which an analysis was archived contains no data — data is not backfilled.
Reading the data
Every analysis exposes its data both in the platform UI and via the Core API. The same analysis, read through both surfaces, returns the same metrics.What’s next
Brand Catalog
How brands and competitors are modelled.
Visibility, Perception & Influence
The three pillars analyses produce.
Brand Analysis Starter Kit
Run your first analysis.
Search Visibility Overview
Run your first search project.