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

# Videntic

> Learn how to set up a Project, understand AI visibility, and act on evidence.

Videntic helps you understand when AI Platforms mention your Brand, cite your Website, and show tracked Competitors instead. Start with a Project, review the customer questions in its Prompt Library, and use the resulting evidence to decide what to improve.

New to Videntic? Follow the [Quickstart](/getting-started/quickstart) from Project setup through your first Analysis. Already have results? Use the paths below to answer a specific question.

## Start here

<CardGroup cols={2}>
  <Card title="Set up your first Project" icon="rocket" href="/getting-started/quickstart">
    Follow the current onboarding flow and review your first Analysis.
  </Card>

  <Card title="Choose a Plan" icon="wallet" href="/billing/plans">
    Understand Prompt, Competitor, and Technical Audit allowances.
  </Card>

  <Card title="Understand the metrics" icon="chart-line" href="/metrics/overview">
    Learn what AI Visibility, Share of Voice, and Citations measure.
  </Card>

  <Card title="Work with Sira" icon="sparkles" href="/features/sira-ai">
    Use Project context to investigate and plan supported work.
  </Card>
</CardGroup>

## Find the right guide

| What you want to do | Start here | What to check before acting |
| - | - | - |
| Build a useful baseline | [Build your Prompt Library](/how-to/manage-prompts) | Do the questions match your customers and Market? |
| Understand a change in the numbers | [Understand your results](/metrics/overview) | Did the Prompt, AI Platform, or Competitor set change? |
| Find out why a Competitor appears instead | [Review your first Analysis](/how-to/run-your-first-audit) | Read the responses and their source links before choosing a content task. |
| Check whether a Website fix took effect | [Review Technical Audit](/features/geo-audit) | Compare the Finding in a later Audit Run. |

## A useful first routine

1. Review the **Prompt Library**. Remove irrelevant questions and keep a stable core that represents your customers.
2. Check **Project Overview** and **Analytics** after an Analysis completes. Open the response evidence behind a surprising result.
3. Review **Technical Audit** findings separately. Confirm a finding still applies before making a Website change, then use a later Audit Run to check the result.
4. Revisit the same Prompts and Market over time. Record changes to your measurement scope when interpreting trends.

For definitions, see the [glossary](/concepts/glossary). For setup, continue with the [quickstart](/getting-started/quickstart).


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