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

# For AI agents

> How a coding agent reads this documentation: the skill file, llms.txt, Markdown versions of every page and the documentation MCP server.

This documentation is written for people and is equally available to coding agents — Claude Code,
Cursor, Copilot and others. An agent does not have to parse the HTML: every page also exists as
Markdown, and the whole set comes in forms meant to be loaded as context.

## What an agent can read

| Resource | Address | What it is |
| - | - | - |
| Skill file | [`/docs/skill.md`](https://veriqa.app/docs/skill.md) | Read this first: what Veriqa is, how to choose between the two mechanisms, recipes for typical tasks, configuration keys, common mistakes and a checklist before finishing |
| Page index | [`/docs/llms.txt`](https://veriqa.app/docs/llms.txt) | Every page with a one-line description, in navigation order |
| Full text | [`/docs/llms-full.txt`](https://veriqa.app/docs/llms-full.txt) | The whole documentation in one file |
| Any page as Markdown | add `.md` to the page address, e.g. [`/docs/quickstart/dotnet.md`](https://veriqa.app/docs/quickstart/dotnet.md) | The page without the site around it |
| Documentation search | `https://veriqa.app/docs/mcp` | An MCP server that searches this documentation |

The skill file, the index and the full text are in English. Russian pages are not in them, but each
one has its Markdown version too, under `/docs/ru/` — e.g. `/docs/ru/quickstart/dotnet.md`.

## Connect the documentation MCP server

With the MCP server, the agent searches the documentation itself while it works, instead of relying
on what it remembers.

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http veriqa-docs https://veriqa.app/docs/mcp
    ```

    Add `--scope project` to share the server with your team through `.mcp.json`.
  </Tab>

  <Tab title="Cursor and VS Code">
    Open the menu at the top of any page and choose Cursor or VS Code; the editor installs the
    server.
  </Tab>

  <Tab title="Other tools">
    Use the menu at the top of any page to copy the MCP server address, then paste it into the
    tool's MCP settings.
  </Tab>
</Tabs>

## Use one page as context

The same menu at the top of every page copies the page as Markdown, opens it as Markdown, or starts
a conversation in Claude or ChatGPT with the page attached. It is the quickest way to hand an agent
exactly the page the task is about.

## What to tell the agent

The agent works better when the task names the mechanism and the deployment mode. A few starting
points:

* *"Read [https://veriqa.app/docs/skill.md](https://veriqa.app/docs/skill.md), then add sign-in through Veriqa embedded in this
  ASP.NET Core application. Enable Telegram only."*
* *"Read [https://veriqa.app/docs/skill.md](https://veriqa.app/docs/skill.md). This application signs users in through a self-hosted
  Veriqa — wire it up as a plain OpenID Connect client; do not add any Veriqa package."*
* *"Using [https://veriqa.app/docs/reference/confirmation-api.md](https://veriqa.app/docs/reference/confirmation-api.md), ask the account owner to confirm
  before `DeleteProject` runs, and delete the project only if the owner has confirmed."*

<Note>
  An application that only signs users in needs no Veriqa package or SDK — it is an ordinary
  OpenID Connect relying party. Veriqa packages belong only where the application *is* the issuer
  or calls the confirmation API from its server. Agents often get this wrong; say it in the task
  if your application is a client.
</Note>

## See also

* [Samples](/docs/samples) — runnable projects an agent can copy from
* [Configuration reference](/docs/reference/configuration)
* [Known limitations](/docs/reference/limitations)


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