> ## 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.

# API Documentation Guide

> Programmatically access Share Of Model visibility and perception data — auth, modules and core concepts.

The Share Of Model API exposes the same AI visibility and perception data available in the platform, so you can integrate it into your tools, dashboards and workflows.

Rather than relying solely on the UI, the API lets you operationalise insights at scale, automate reporting, and connect AI signals to your internal analytics and activation systems.

## Modules currently exposed

<CardGroup cols={2}>
  <Card title="Search Visibility" icon="magnifying-glass" href="/platform/search/overview-what-how-purpose">
    AI-driven visibility signals across answer engines — how brands, products and categories surface in AI-generated answers, and which sources contribute to that visibility.
  </Card>

  <Card title="Brand Perception" icon="eye" href="/platform/models/brand-analysis-starter-kit">
    How AI models describe and interpret a brand — attributes, narratives and associations inferred by AI systems.
  </Card>
</CardGroup>

## Who the API is for

* **Product and data teams** building internal dashboards.
* **Marketing and brand teams** centralising AI signals in BI tools.
* **Technical teams** integrating Share Of Model into proprietary platforms.

## What you can do with the API

* Access visibility and citation data across AI answer engines.
* Retrieve brand-perception signals generated by AI models.
* Extract insights at product and category level for reporting or analysis.

All responses are structured for programmatic consumption.

## Prerequisites

Generate an API key with the appropriate access privileges before calling the API.

<Card title="Creating and Managing API Keys" icon="key" href="/platform/getting-started/creating-and-managing-api-keys">
  Step-by-step guide for user, workspace and organisation keys.
</Card>

<Warning>
  API keys are scoped to your workspace and must be treated as confidential credentials.
</Warning>

## Making your first call

The API documentation is split between two distinct APIs. Switch between them using the dropdown in the docs site header:

* **Brand Analysis Module**
* **Search Visibility Module**

### Authentication flow

<Steps>
  <Step title="Generate your API key">
    See [Creating and Managing API Keys](/platform/getting-started/creating-and-managing-api-keys).
  </Step>

  <Step title="Exchange the key for a JWT">
    Use the API key to request a **JWT token** through the authentication endpoints.
  </Step>

  <Step title="Authenticate every request">
    Pass the JWT as a **Bearer token** in the `Authorization` header on every subsequent request.
  </Step>
</Steps>

### First test call

A quick way to validate your setup is to call the endpoint that lists organisations you have access to. For other endpoints, follow the parameters described in the [API Reference](/api-reference/introduction).

## How the Search API works

The Search Visibility API is structured around **Projects** and **Collects**.

### Projects

Projects can only be created through the UI. During setup you define:

* a website,
* a brand,
* a locale (country and language),
* a list of thematics and sub-topics,
* a list of search queries (prompts) — each can include funnel stage, thematic, topic, persona and more,
* a collection frequency (once, weekly, or monthly),
* a list of LLM sources to monitor.

### Collects

A collect is automatically created and associated with a project each time the platform gathers metrics.

| Frequency | Behaviour              |
| --------- | ---------------------- |
| Once      | One collect total.     |
| Weekly    | One collect per week.  |
| Monthly   | One collect per month. |

When a collect's status is `FINISHED`, its ID can be used to retrieve metrics through the API.

### Aggregations and evolutions

Most endpoints support aggregation and comparison across multiple collects.

* **Single-collect metrics** — provide one ID in `collect_ids`.
* **Aggregated metrics** — provide multiple IDs in `collect_ids`.
* **Evolution / comparison** — provide one or more IDs in `prev_collect_ids` to compare against a previous set.

This structure supports performance snapshots, trends and evolutions over time.

## Support

<Tip>
  Our support team is available — reach out from the in-app chat for any API question.
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/api-reference/quickstart">
    From zero to your first authenticated call in minutes.
  </Card>

  <Card title="MCP Server Setup" icon="plug" href="/platform/getting-started/get-started-with-share-of-model-mcp">
    Connect AI assistants to your data.
  </Card>
</CardGroup>