Klariqo calls now emit signed vCons using the IETF vCon Working Group’s draft format — tamper-evident records of the conversation. Paste or drop one below and check its cryptographic signature right here in your browser. Nothing is uploaded; verification runs entirely on your machine.
Drop a .vcon.json here
or click to choose a file
or paste the vCon JSON
Klariqo’s published vCon signing key
The verifier confirms a vCon was signed by the holder of this key by matching its certificate fingerprint against the value below. Identity is self-asserted — it is not yet anchored to a third-party trust layer (such as SCITT). You can confirm the match yourself.
A vCon is a single, signable container for a conversation: its parties, transcript, outcome, and a cryptographic fingerprint of the recording. Signing makes the signed content tamper-evident — change the transcript, the metadata, or the recording fingerprint and the signature check fails.
Why it matters for voice AI: consent, disposition, and audit metadata can travel with the conversation, and the signed record cannot be edited after the fact without invalidating the signature. Because it’s an open format, a signed conversation record means the same thing across every vendor that adopts it.
Klariqo is adopting native vCon signing early for voice AI and pay-per-call workflows — every new call now emits a signed vCon.
vCon is an open conversation-record format being developed in the IETF vCon Working Group under draft draft-ietf-vcon-vcon-core. The specification is led by Thomas McCarthy-Howe, championed by Jeff Pulver, and stewarded by the vCon Foundation. The reference open-source tooling is the Conserver. Klariqo did not create vCon — we adopt it.