For the complete documentation index, see llms.txt. This page is also available as Markdown.

πŸ‘‹Welcome to the Home of the vCons

vCon is the open container for conversations. Signed, consent aware, and portable, it lets organizations record what was said, by whom, and under what authority, in a way that machines and auditors ca

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.

If you read one page, read this:

πŸ’¬A vCon Primer

Why this matters now

AI agents are starting to talk to customers and to each other. There is no shared record of what an agent said, on whose behalf it spoke, or under what authority it acted. vCon is that record. It captures the dialog, the parties, and the consent in a single signed object that any downstream tool can verify.

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.

Find your path

You want to know where vCon fits in your stack and whether it is real.

What is in the box

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.

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.

Open source repository for vCon and the Conserver
IETF VCON working group

Keep reading

πŸ’¬A vCon PrimerπŸ—„οΈWhy Conversations Need a FileπŸ’‘Concepts🐰Conserver Quick StartOverview

Last updated

Was this helpful?