What an agent can read
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.- Claude Code
- Cursor and VS Code
- Other tools
--scope project to share the server with your team through .mcp.json.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, then add sign-in through Veriqa embedded in this ASP.NET Core application. Enable Telegram only.”
- “Read 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, ask the account owner to confirm
before
DeleteProjectruns, and delete the project only if the owner has confirmed.”
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.
See also
- Samples — runnable projects an agent can copy from
- Configuration reference
- Known limitations