> ## Documentation Index
> Fetch the complete documentation index at: https://docs.videntic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Videntic?

> How Projects, Prompts, Analyses, and Technical Audit fit together.

Videntic measures how a Brand appears in answers from AI Platforms. It also helps you review the Website conditions and content opportunities that may affect discoverability. Measurement and Website diagnosis are related, but they are separate workflows.

## The pieces of a Project

* **Project and Market:** a Project measures one Brand in one country and language context, anchored to its primary Website.
* **Prompt Library:** the customer-style questions you want to measure repeatedly. Review these before treating a metric as representative of your customers.
* **Analysis:** one measurement cycle across the active Prompts and supported AI Platforms. It produces response evidence and metrics such as AI Visibility and Share of Voice.
* **Technical Audit:** a separate evaluation of Website pages and conditions. Its Audit Runs produce findings and an AI Readiness score.
* **Sira:** an AI agent that can help interpret Project context and carry out supported work, subject to your access and Plan.

## Mentions and Citations

A **Mention** is a reference to a Brand in the prose of an AI Response. A **Citation** is a source link in that response. An answer can mention your Brand without linking to your Website, or link to a page without mentioning your Brand in its prose. These signals should be read separately.

**AI Visibility** measures how often your Brand appears in the planned response opportunities. **Share of Voice** compares your Brand's Mentioning Responses with those of tracked Competitors. **Citation Share** compares attributed Citation Counts. See [Core metrics](/metrics/overview) for the detailed definitions.

## Use results well

Start by checking the Prompts, Market, and tracked Competitors behind a result. Then inspect response evidence and any relevant Technical Audit findings. Use a later Analysis or Audit Run to observe what changed after an action. The presence of a trend does not, by itself, prove which action caused it.

## Get started

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    Set up a Project from Website to Prompt review.
  </Card>

  <Card title="Add a Project website" icon="globe" href="/getting-started/add-a-website">
    Choose a Website and Market for measurement.
  </Card>

  <Card title="Set up multiple Markets" icon="map" href="/how-to/set-up-multiple-markets">
    Measure separate country and language contexts.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.