Cowrie Research

vouch-primary-sources-2026-04-27

4 min read

Vouch primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Homepage / current framing

  • URL: https://www.getvouch.io/
  • Key takeaways:
    • The homepage frames Vouch around identity, employment, social, and other verification flows without document uploads.
    • It emphasizes “AI-resilient verification,” privacy, and direct verification from sources users already trust.
    • The site suggests a business-focused product aimed at replacing manual verification and screenshot/document-based processes.

2) Docs introduction / product scope

  • URL: https://docs.getvouch.io/introduction
  • Key takeaways:
    • The docs say Vouch enables businesses to verify user-owned data with cryptographic proofs rather than document uploads or narrow third-party APIs.
    • They organize the product into three main groups: Non-Doc KYC & KYB, Candidate Authenticity, and Social & Audience Verification.
    • The docs explicitly say the platform can work with data sources users can access online, which is an important clue that Vouch is broader than a single compliance or creator niche.

3) Getting started / integration model

  • URL: https://docs.getvouch.io/getting-started/first-steps
  • Key takeaways:
    • Vouch’s basic integration pattern is to use the SDK to create a secure verification URL, redirect the user, and optionally receive a webhook when the proof flow completes.
    • The docs expose core integration primitives such as customerId, apiKey, datasourceId, redirectBackUrl, webhookUrl, inputs, and metadata.
    • Sandbox and production are separated, and the docs explicitly note that sandbox proofs may be placeholder or example outputs and do not offer real cryptographic guarantees.
    • The page also shows Vouch is building agent/LLM-facing documentation surfaces (llms.txt and skills references), which is a useful operational clue for future cataloging.

4) Webhook verification / trust boundary

  • URL: https://docs.getvouch.io/getting-started/verifying-webproofs
  • Key takeaways:
    • Vouch says it cryptographically verifies proofs before sending webhook results, but customer applications must still authenticate the request origin and validate outputs before using them in business logic.
    • The webhook docs define a PSK-style Authorization header and provide example payload structure containing requestId, outputs, and webProofs.
    • The docs also distinguish required request verification and output validation from optional cryptographic presentation verification, which is a useful trust-boundary note.
    • Static webhook IPs are published for allowlisting, which is another operationally meaningful primary-source detail.

5) Non-doc KYC/KYB example

  • URL: https://docs.getvouch.io/examples/non_doc_kyc_kyb
  • Key takeaways:
    • The example shows address verification via a specific Revolut data source.
    • It demonstrates the user redirect flow, the webhook output shape, and the treatment of “Sensitive Data” sources.
    • For sensitive sources, the docs say webProofs are excluded and transcripts are redacted while only extracted outputs are retained.
    • This makes Vouch look like a privacy-preserving verification delivery platform, not just a proof generator.

6) Social & audience example

  • URL: https://docs.getvouch.io/examples/social_and_audience
  • Key takeaways:
    • The Instagram example shows Vouch handling account ownership, follower metrics, and audience demographics through authenticated user access.
    • The resulting payload can include both high-level outputs and underlying proof material when the data source is not marked sensitive.
    • This broadens the category beyond compliance into creator, reputation, and marketplace verification workflows.

Whitepaper / technical-doc status

  • No canonical standalone Vouch whitepaper or litepaper was found in this pass.
  • The strongest source of truth is the official site plus the docs set covering introduction, getting started, webhook verification, and concrete example implementations.
  • In practice, the docs are more informative than a missing whitepaper because they expose the actual integration flow, trust boundary, and privacy model.

Research notes

  • Best current category for the library: privacy-preserving user-data verification / non-doc KYC-KYB infrastructure / crypto-adjacent identity and proof-delivery platform.
  • Key categorization insight: Vouch should be treated as the productized application layer built on top of vlayer, not as the protocol itself.
  • Another useful note for future scouting: products with redirect flows, webhook delivery, and explicit sensitive-data retention rules can reveal the real business model and trust boundary much more clearly than a homepage slogan.

Graph View