> 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/readme.md).

# Welcome to the Home of the vCons

## A trust layer for every conversation, human or agent

Every business runs on conversations. Calls, chats, video meetings, agent dialog. Until now there has been no shared way to record what was said, on whose behalf, and under what authority, in a form that survives moving between systems.

vCon (virtual conversation) is that container. It is an open IETF standard for packaging the parties, the dialog, the recording or transcript, the consent, and the analysis into one signed, portable JSON object. The Conserver is the open source platform that creates and manages vCons at scale.

{% columns %}
{% column %}
If you read one page, read this:

{% content-ref url="/pages/tWoe8nJgLTVfXkTlN9d7" %}
[A vCon Primer](/vcons/a-vcon-primer.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
If you watch one video, watch this:

{% embed url="<https://www.youtube.com/watch?v=beqmNDEgq_E>" %}
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
**Provenance over policy.** vCon does not ask you to trust a vendor that says the right things. It puts cryptographic provenance, parties, and consent inside the file itself, so the next system in line can verify them on its own.
{% endhint %}

## Find your path

{% tabs %}
{% tab title="Architects and CTOs" %}
You want to know where vCon fits in your stack and whether it is real.

* [vCons are...](/vcons/vcons-are....md) — the one paragraph mental model
* [Why vCons need a file](/vcons/why-vcons.md) — conversations as durable digital artifacts in the AI era
* [Conserver Introduction](/conserver/conserver-introduction.md) — the reference platform that produces and processes vCons
* [Day in the Life of a vCon](/conserver/day-in-the-life-of-a-vcon.md) — end to end flow
  {% endtab %}

{% tab title="Business and compliance" %}
You care about consent, regulatory exposure, and AI governance.

* [A vCon Primer](/vcons/a-vcon-primer.md) — the full story, written for non specialists
* [Privacy Primer](/vcons/privacy-primer.md) — how vCon handles PII, deletion and lawful basis
* [Lawful Basis extension](/extensions/lawful-basis.md) — consent that travels with the data
* [PII Compliance use case](/use-cases-studies/pii-compliance.md) — what this looks like in practice
  {% endtab %}

{% tab title="Developers and engineers" %}
You want to read code and get something running.

* [Conserver Quick Start](/conserver/conserver-quick-start.md) — a vCon pipeline on your machine
* [vCon Library (Python) Quickstart](/vcon-library/quickstart.md)
* [vCon JS Library Quickstart](/vcon-js-library/quickstart.md)
* [vCon Adapters Quick Start](/vcon-adapters/quick-start-from-template.md) — wire your platform into the ecosystem
* [MCP Server](/mcp-server.md) — expose vCons to AI agents safely
  {% endtab %}

{% tab title="Standards and policy" %}
You are tracking the working group and the surrounding standards.

* [IETF VCON working group](https://datatracker.ietf.org/group/vcon/about/)
* [Core draft `draft-ietf-vcon-vcon-core`](https://datatracker.ietf.org/doc/draft-ietf-vcon-vcon-core/)
* [SCITT and vCon together](/deep-dives/scitt-supply-chain-integrity-transparency-and-trust.md)
* [IETF sessions, talks and press](/talks-articles-press.md)
  {% endtab %}
  {% endtabs %}

## What is in the box

{% tabs %}
{% tab title="The vCon object" %}

<figure><img src="/files/YCoLQzjr0NYhWeTnjcZS" alt=""><figcaption><p>A signed JSON object that carries parties, dialog (recording or transcript), attachments, analyses, consent, and a tamper evident history. The same format works for a phone call, a chat session, a video meeting, or a human to agent conversation.</p></figcaption></figure>
{% endtab %}

{% tab title="The Conserver" %}

<figure><img src="/files/lhyNgQmJOTAL6Vv4dsoO" alt=""><figcaption><p>The open source platform that creates vCons from business systems, runs them through pipelines of links (transcribe, redact, analyze, store, forward), and emits archive copies plus projections into the tools the business already uses.</p></figcaption></figure>
{% endtab %}

{% tab title="MCP server and adapters" %}

<figure><img src="/files/FbuIGvyxi2ja89qScRx2" alt=""><figcaption><p>Applications consume vCons through the Conserver API, the MCP server, or the language libraries. Adapters let CPaaS providers, contact centers, and recording vendors plug their platforms into the ecosystem without inventing a new format.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

## Open, by design

vCon is developed in the open at the IETF, the same standards body that produced the protocols the internet runs on, from TCP/IP and DNS to HTTP, TLS, and SIP. IETF work is rough consensus, running code, and a public record. Anyone can read the drafts, join the list, and challenge a design decision in writing.

The format itself carries no patent encumbrance, by design, the same way PDF and vCard do not. The working group brings together telecom regulators, carriers, hyperscale platforms, and human rights organizations, and public statements from those constituencies appear in [Talks, Articles and Press](/talks-articles-press.md).

{% embed url="<https://github.com/vcon-dev/vcon>" %}
Open source repository for vCon and the Conserver
{% endembed %}

{% embed url="<https://datatracker.ietf.org/group/vcon/about/>" %}
IETF VCON working group
{% endembed %}

## Keep reading

{% content-ref url="/pages/tWoe8nJgLTVfXkTlN9d7" %}
[A vCon Primer](/vcons/a-vcon-primer.md)
{% endcontent-ref %}

{% content-ref url="/pages/6OgLwHqRfuxrhLio8dcV" %}
[Why Conversations Need a File](/vcons/why-vcons.md)
{% endcontent-ref %}

{% content-ref url="/pages/6H3AFSf4P59nbElEqiDz" %}
[Concepts](/vcons/concepts.md)
{% endcontent-ref %}

{% content-ref url="/pages/txamxOwfZO2dc4BXOLsq" %}
[Conserver Quick Start](/conserver/conserver-quick-start.md)
{% endcontent-ref %}

{% content-ref url="/pages/SLtbUqEILdKCyibWOsSe" %}
[Overview](/use-cases-studies/overview.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.