> For the complete documentation index, see [llms.txt](https://www.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.conserver.io/vcons.md).

# vCons

Says what a vCon is in three sentences and gives you the order to read the pages in this section.

A vCon (virtual conversation) is a JSON container for one conversation: who took part, what was said, what has been derived from it, and the files that explain it. It does for conversations what PDF did for documents and vCard did for contacts, so a call, chat or meeting can move between systems as one object. It is being standardized at the IETF as [`draft-ietf-vcon-vcon-core`](https://datatracker.ietf.org/doc/draft-ietf-vcon-vcon-core/), with optional signing and extensions such as lawful basis built on top.

## Reading path

1. [A vCon Primer](/vcons/a-vcon-primer.md): what a vCon is, why it exists, what is inside, and where the standard stands.
2. [Concepts](/vcons/concepts.md): the terms you meet in the spec, a sentence or two each.
3. [Field Reference](/vcons/field-reference.md): every field, extension token and current draft revision.
4. [Privacy Primer](/vcons/privacy-primer.md): lawful basis, personal data and data subject rights.
5. [The Journey of a vCon](/vcons/vcon-conveyor-infographic.md): one vCon moving through a Conserver pipeline.
6. [More Information](/vcons/more-information.md): drafts, talks, articles and outside commentary.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.conserver.io/vcons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.