Metadata-Version: 2.4
Name: vouch-protocol
Version: 1.6.0
Summary: The Identity & Reputation Standard for AI Agents
Author-email: Vouch Protocol Contributors <hello@vouch-protocol.com>
License: Apache License 2.0
        ==================
        
        Copyright 2025 Vouch Protocol Contributors
        
        Licensed under the Apache License, Version 2.0 (the "License");
        you may not use this file except in compliance with the License.
        You may obtain a copy of the License at
        
            http://www.apache.org/licenses/LICENSE-2.0
        
        Unless required by applicable law or agreed to in writing, software
        distributed under the License is distributed on an "AS IS" BASIS,
        WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
        See the License for the specific language governing permissions and
        limitations under the License.
        
        NOTE: The Vouch Protocol specification may be contributed to W3C
        Verifiable Credentials Working Group as a separate standards track.
        
        ================================================================================
        
                                         Apache License
                                   Version 2.0, January 2004
                                http://www.apache.org/licenses/
        
           TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
        
           1. Definitions.
        
              "License" shall mean the terms and conditions for use, reproduction,
              and distribution as defined by Sections 1 through 9 of this document.
        
              "Licensor" shall mean the copyright owner or entity authorized by
              the copyright owner that is granting the License.
        
              "Legal Entity" shall mean the union of the acting entity and all
              other entities that control, are controlled by, or are under common
              control with that entity. For the purposes of this definition,
              "control" means (i) the power, direct or indirect, to cause the
              direction or management of such entity, whether by contract or
              otherwise, or (ii) ownership of fifty percent (50%) or more of the
              outstanding shares, or (iii) beneficial ownership of such entity.
        
              "You" (or "Your") shall mean an individual or Legal Entity
              exercising permissions granted by this License.
        
              "Source" form shall mean the preferred form for making modifications,
              including but not limited to software source code, documentation
              source, and configuration files.
        
              "Object" form shall mean any form resulting from mechanical
              transformation or translation of a Source form, including but
              not limited to compiled object code, generated documentation,
              and conversions to other media types.
        
              "Work" shall mean the work of authorship, whether in Source or
              Object form, made available under the License, as indicated by a
              copyright notice that is included in or attached to the work
              (an example is provided in the Appendix below).
        
              "Derivative Works" shall mean any work, whether in Source or Object
              form, that is based on (or derived from) the Work and for which the
              editorial revisions, annotations, elaborations, or other modifications
              represent, as a whole, an original work of authorship. For the purposes
              of this License, Derivative Works shall not include works that remain
              separable from, or merely link (or bind by name) to the interfaces of,
              the Work and Derivative Works thereof.
        
              "Contribution" shall mean any work of authorship, including
              the original version of the Work and any modifications or additions
              to that Work or Derivative Works thereof, that is intentionally
              submitted to Licensor for inclusion in the Work by the copyright owner
              or by an individual or Legal Entity authorized to submit on behalf of
              the copyright owner. For the purposes of this definition, "submitted"
              means any form of electronic, verbal, or written communication sent
              to the Licensor or its representatives, including but not limited to
              communication on electronic mailing lists, source code control systems,
              and issue tracking systems that are managed by, or on behalf of, the
              Licensor for the purpose of discussing and improving the Work, but
              excluding communication that is conspicuously marked or otherwise
              designated in writing by the copyright owner as "Not a Contribution."
        
              "Contributor" shall mean Licensor and any individual or Legal Entity
              on behalf of whom a Contribution has been received by Licensor and
              subsequently incorporated within the Work.
        
           2. Grant of Copyright License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              copyright license to reproduce, prepare Derivative Works of,
              publicly display, publicly perform, sublicense, and distribute the
              Work and such Derivative Works in Source or Object form.
        
           3. Grant of Patent License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              (except as stated in this section) patent license to make, have made,
              use, offer to sell, sell, import, and otherwise transfer the Work,
              where such license applies only to those patent claims licensable
              by such Contributor that are necessarily infringed by their
              Contribution(s) alone or by combination of their Contribution(s)
              with the Work to which such Contribution(s) was submitted. If You
              institute patent litigation against any entity (including a
              cross-claim or counterclaim in a lawsuit) alleging that the Work
              or a Contribution incorporated within the Work constitutes direct
              or contributory patent infringement, then any patent licenses
              granted to You under this License for that Work shall terminate
              as of the date such litigation is filed.
        
           4. Redistribution. You may reproduce and distribute copies of the
              Work or Derivative Works thereof in any medium, with or without
              modifications, and in Source or Object form, provided that You
              meet the following conditions:
        
              (a) You must give any other recipients of the Work or
                  Derivative Works a copy of this License; and
        
              (b) You must cause any modified files to carry prominent notices
                  stating that You changed the files; and
        
              (c) You must retain, in the Source form of any Derivative Works
                  that You distribute, all copyright, patent, trademark, and
                  attribution notices from the Source form of the Work,
                  excluding those notices that do not pertain to any part of
                  the Derivative Works; and
        
              (d) If the Work includes a "NOTICE" text file as part of its
                  distribution, then any Derivative Works that You distribute must
                  include a readable copy of the attribution notices contained
                  within such NOTICE file, excluding those notices that do not
                  pertain to any part of the Derivative Works, in at least one
                  of the following places: within a NOTICE text file distributed
                  as part of the Derivative Works; within the Source form or
                  documentation, if provided along with the Derivative Works; or,
                  within a display generated by the Derivative Works, if and
                  wherever such third-party notices normally appear. The contents
                  of the NOTICE file are for informational purposes only and
                  do not modify the License. You may add Your own attribution
                  notices within Derivative Works that You distribute, alongside
                  or as an addendum to the NOTICE text from the Work, provided
                  that such additional attribution notices cannot be construed
                  as modifying the License.
        
              You may add Your own copyright statement to Your modifications and
              may provide additional or different license terms and conditions
              for use, reproduction, or distribution of Your modifications, or
              for any such Derivative Works as a whole, provided Your use,
              reproduction, and distribution of the Work otherwise complies with
              the conditions stated in this License.
        
           5. Submission of Contributions. Unless You explicitly state otherwise,
              any Contribution intentionally submitted for inclusion in the Work
              by You to the Licensor shall be under the terms and conditions of
              this License, without any additional terms or conditions.
              Notwithstanding the above, nothing herein shall supersede or modify
              the terms of any separate license agreement you may have executed
              with Licensor regarding such Contributions.
        
           6. Trademarks. This License does not grant permission to use the trade
              names, trademarks, service marks, or product names of the Licensor,
              except as required for reasonable and customary use in describing the
              origin of the Work and reproducing the content of the NOTICE file.
        
           7. Disclaimer of Warranty. Unless required by applicable law or
              agreed to in writing, Licensor provides the Work (and each
              Contributor provides its Contributions) on an "AS IS" BASIS,
              WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
              implied, including, without limitation, any warranties or conditions
              of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
              PARTICULAR PURPOSE. You are solely responsible for determining the
              appropriateness of using or redistributing the Work and assume any
              risks associated with Your exercise of permissions under this License.
        
           8. Limitation of Liability. In no event and under no legal theory,
              whether in tort (including negligence), contract, or otherwise,
              unless required by applicable law (such as deliberate and grossly
              negligent acts) or agreed to in writing, shall any Contributor be
              liable to You for damages, including any direct, indirect, special,
              incidental, or consequential damages of any character arising as a
              result of this License or out of the use or inability to use the
              Work (including but not limited to damages for loss of goodwill,
              work stoppage, computer failure or malfunction, or any and all
              other commercial damages or losses), even if such Contributor
              has been advised of the possibility of such damages.
        
           9. Accepting Warranty or Additional Liability. While redistributing
              the Work or Derivative Works thereof, You may choose to offer,
              and charge a fee for, acceptance of support, warranty, indemnity,
              or other liability obligations and/or rights consistent with this
              License. However, in accepting such obligations, You may act only
              on Your own behalf and on Your sole responsibility, not on behalf
              of any other Contributor, and only if You agree to indemnify,
              defend, and hold each Contributor harmless for any liability
              incurred by, or claims asserted against, such Contributor by reason
              of your accepting any such warranty or additional liability.
        
           END OF TERMS AND CONDITIONS
        
Project-URL: Homepage, https://github.com/vouch-protocol/vouch
Project-URL: Bug Tracker, https://github.com/vouch-protocol/vouch/issues
Project-URL: Documentation, https://vouch-protocol.com
Keywords: ai,agents,identity,cryptography,did,verifiable-credentials
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Security :: Cryptography
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: jwcrypto>=1.5.0
Requires-Dist: python-dateutil
Requires-Dist: cryptography
Requires-Dist: pydantic>=2.0.0
Requires-Dist: httpx>=0.24.0
Requires-Dist: pqcrypto>=0.4.0
Provides-Extra: langchain
Requires-Dist: langchain>=0.1.0; extra == "langchain"
Provides-Extra: crewai
Requires-Dist: crewai>=0.1.0; extra == "crewai"
Provides-Extra: autogen
Requires-Dist: pyautogen>=0.2.0; extra == "autogen"
Provides-Extra: mcp
Requires-Dist: mcp>=0.1.0; extra == "mcp"
Provides-Extra: vertex
Requires-Dist: google-cloud-aiplatform>=1.0.0; extra == "vertex"
Provides-Extra: streamlit
Requires-Dist: streamlit>=1.0.0; extra == "streamlit"
Provides-Extra: server
Requires-Dist: fastapi>=0.100.0; extra == "server"
Requires-Dist: uvicorn>=0.23.0; extra == "server"
Provides-Extra: enterprise
Requires-Dist: redis>=5.0.0; extra == "enterprise"
Requires-Dist: prometheus-client>=0.17.0; extra == "enterprise"
Provides-Extra: aws
Requires-Dist: aioboto3>=12.0.0; extra == "aws"
Provides-Extra: gcp
Requires-Dist: google-cloud-kms>=2.0.0; extra == "gcp"
Provides-Extra: azure
Requires-Dist: azure-keyvault-keys>=4.0.0; extra == "azure"
Provides-Extra: pq
Provides-Extra: tracing
Requires-Dist: opentelemetry-api>=1.20.0; extra == "tracing"
Requires-Dist: opentelemetry-sdk>=1.20.0; extra == "tracing"
Requires-Dist: opentelemetry-instrumentation-httpx>=0.40b0; extra == "tracing"
Provides-Extra: media
Requires-Dist: Pillow>=10.0.0; extra == "media"
Requires-Dist: base58>=2.1.0; extra == "media"
Requires-Dist: qrcode>=7.4.0; extra == "media"
Requires-Dist: c2pa-python>=0.5.0; extra == "media"
Provides-Extra: dev
Requires-Dist: pytest>=7.0.0; extra == "dev"
Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
Requires-Dist: pytest-cov>=4.0.0; extra == "dev"
Requires-Dist: black>=23.0.0; extra == "dev"
Requires-Dist: mypy>=1.0.0; extra == "dev"
Requires-Dist: ruff>=0.1.0; extra == "dev"
Requires-Dist: Pillow>=10.0.0; extra == "dev"
Requires-Dist: base58>=2.1.0; extra == "dev"
Requires-Dist: qrcode>=7.4.0; extra == "dev"
Requires-Dist: c2pa-python>=0.5.0; extra == "dev"
Provides-Extra: all
Requires-Dist: vouch-protocol[autogen,crewai,dev,enterprise,langchain,mcp,server,streamlit,tracing,vertex]; extra == "all"
Dynamic: license-file

# Vouch Protocol™

<p align="center">
 <img src="docs/assets/vouch-wordmark.png" alt="Vouch Protocol" width="400">
</p>

<p align="center"><strong>The open standard for the identity and accountability of AI agents.</strong></p>

<p align="center">
 <a href="https://c2pa.org"><img src="https://img.shields.io/badge/C2PA-Member-0891b2?style=for-the-badge" alt="C2PA Member"></a>
 <a href="https://contentauthenticity.org"><img src="https://img.shields.io/badge/CAI-Member-f97316?style=for-the-badge" alt="CAI Member"></a>
 <a href="https://identity.foundation"><img src="https://img.shields.io/badge/DIF-Member-6F2DA8?style=for-the-badge" alt="DIF Member"></a>
 <a href="https://lfaidata.foundation"><img src="https://img.shields.io/badge/Linux_Foundation-Member-333333?style=for-the-badge&logo=linux-foundation&logoColor=white" alt="Linux Foundation Member"></a>
</p>

<p align="center">
 <a href="https://www.bestpractices.dev/projects/11688"><img src="https://www.bestpractices.dev/projects/11688/badge" alt="OpenSSF Best Practices"></a>
 <a href="https://discord.gg/mMqx5cG9Y"><img src="https://img.shields.io/badge/Discord-Join_Community-7289da?logo=discord&logoColor=white" alt="Discord"></a>
 <a href="https://github.com/vouch-protocol/vouch/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="Apache 2.0 License"></a>
</p>

---

AI agents now make real decisions and real API calls. They read data, move money, and act on your behalf. Almost none of them can answer three basic questions: who is this agent, what was it authorized to do, and who is accountable when it goes wrong.

Vouch Protocol gives an AI agent a verifiable, cryptographic identity, the same idea SSL/TLS brought to websites. An agent signs what it intends to do, and anyone can verify who signed it, what they were allowed to do, and that nothing was changed. It is open source, free, and built on proven standards (Verifiable Credentials, Decentralized Identifiers, and Data Integrity proofs).

## Start in one command

```bash
pip install vouch-protocol

# Configure cryptographic commit signing for your repo. One command.
vouch git init

# Every commit from now on is signed and shows as verified.
git commit -m "Secure commit"
```

## See it for yourself

Run the sixty-second demo. It shows a real agent being accepted, an impersonator being rejected, and a tampered credential being rejected, all locally, no setup.

```bash
python examples/00_the_rogue_agent.py
```

Identity you cannot fake. Authority you cannot forge. Actions you cannot alter.

---

## What is in the box

Vouch is not one tool, it is a set of them. Here is the whole map.

### On the command line
- **`vouch init`** generate an agent identity (a DID and keypair).
- **`vouch sign` / `vouch verify`** sign a payload and verify it.
- **`vouch git`** sign every git commit cryptographically, set up in one command, with a verified badge for your README.
- **`vouch scan`** find leaked Vouch key material in your code before it ships (a private key in a file, a seed in an env var, a DID document that accidentally carries a private key).
- **`vouch media`** sign images, with C2PA support.

### For your agents
- **MCP server (`vouch-mcp`)** a standalone Model Context Protocol server so any MCP client (Claude Desktop, Cursor, any agent) can create an identity, sign and verify credentials, scan for leaked keys, and decode DIDs, out of the box.
- **Identity Sidecar** keeps signing keys out of the model's context, so a prompt injection cannot read them.
- **Vouch Shield** a runtime check that inspects every tool call against your rules, like a customs officer at the door.
- **Continuous trust** heartbeats and session vouchers, so trust is a live signal that has to be renewed, not a badge that is issued once and trusted forever.

### SDKs, in the language you use
Python, TypeScript, and Go are the full reference implementations. A Rust core with idiomatic Swift, JVM (Java and Kotlin), .NET, and C wrappers shares one codebase, so every language produces byte-identical output, verified against shared test vectors. A WebAssembly build is included for the browser and the edge. See the table further down for status per language.

### Inside your AI tools
- **Claude Skill**, **OpenAI Custom GPT**, and **Gemini Gem** packages that teach your AI assistant how to add Vouch to your code, running on your own AI subscription.

### Media and the web
- **C2PA Content Credentials** for images.
- **Vouch Sonic** an audio watermark that carries provenance through sound.
- **Browser extension** for Chrome and Edge that signs and verifies content on the page.

### For your repositories
- **Gatekeeper GitHub App** verifies commit signatures on every pull request and blocks leaked Vouch keys before they merge.

### For the ecosystem
- **Agent Trust Index** an open benchmark that scans agents in the wild and measures how many can actually prove who they are. (Spoiler: today, almost none.)

---

## How it works

```mermaid
flowchart LR
  P["Principal<br/>did:web:user.example.com"]
  A["AI Agent<br/>did:web:agent.example.com<br/>+ Identity Sidecar"]
  C["Vouch Credential<br/>VC + Data Integrity<br/>(eddsa-jcs-2022)"]
  API["API Endpoint"]
  V{"Verified"}

  P -->|"Delegation credential"| A
  A -->|"sign_credential(intent)"| C
  C -->|"HTTP body<br/>application/vc+vouch"| API
  API -->|"verify_credential()"| V
```

1. **Generate identity.** Create a keypair and a DID, and publish a DID Document with a verification method.
2. **Sign the action.** The agent issues a Verifiable Credential carrying `action`, `target`, and `resource`, secured by an `eddsa-jcs-2022` Data Integrity proof. The `resource` binding is what stops an agent from being tricked into acting on the wrong thing.
3. **Send it.** The credential travels as the HTTP request body.
4. **Verify.** The receiver resolves the issuer's DID, checks the proof, the timing, and the resource, and gets back a passport describing who acted and what they intended.

The credential stays human-readable JSON. The proof attaches as a sibling object. No opaque base64 blob.

---

## Sign and verify

Sign an action:

```python
from vouch import Signer
import os

signer = Signer(private_key=os.environ["VOUCH_PRIVATE_KEY"], did=os.environ["VOUCH_DID"])

credential = signer.sign_credential(intent={
    "action": "read_database",
    "target": "users_table",
    "resource": "https://api.example.com/v1/users",
})
```

Verify it:

```python
from vouch import Verifier

is_valid, passport = Verifier.verify_credential(credential, public_key=public_key)
if is_valid:
    print(passport.sub, passport.intent)
```

`verify_credential` returns a plain `(is_valid, passport)` pair. A few lines to sign, a few to verify.

---

## Languages and interop

The crypto is written once and shared, so the output is identical across every language and is checked against the same test vectors.

| Language | Package | Status |
|---|---|---|
| Python | `vouch-protocol` (PyPI) | Stable, full reference implementation |
| TypeScript | `@vouch-protocol-official/sdk` (npm) | Stable |
| Go | `go-sidecar` | Stable signing sidecar |
| Rust | `vouch-core` (crates.io) | Ready |
| Java / Kotlin | `com.vouchprotocol:vouch-core-jvm` (Maven Central) | Ready |
| .NET | `VouchProtocol.Core` (NuGet) | Preview, needs a platform build |
| Swift | `VouchCore` (Swift Package Manager) | Preview, needs a macOS build |
| C | header shipped with the Rust core | Preview |
| WebAssembly | `core/wasm` | For browser and edge |

Every implementation does identity, signing with `eddsa-jcs-2022`, verification, the hybrid post-quantum profile, status-list revocation, and delegation, and they all verify each other's output.

---

## Post-quantum, when you need it

A credential can carry two independent proofs over the same bytes: a classical Ed25519 proof and a post-quantum ML-DSA-44 proof. A verifier can require either or both. This guards credentials signed today against a future quantum break, and lines up with the NIST CNSA 2.0 and NSM-10 migration timelines.

```python
credential = signer.sign_credential_hybrid(intent={
    "action": "submit_clinical_finding",
    "target": "trial:NCT00000001",
    "resource": "https://submissions.example.com/api/findings",
})
```

---

## Built on, and contributing to, open standards

Vouch is built on Verifiable Credentials, Decentralized Identifiers, Data Integrity proofs, and Multikey, and uses RFC 8785 JCS for deterministic, parser-independent canonical form. The project is a member of C2PA, the Content Authenticity Initiative, the Decentralized Identity Foundation, and the Linux Foundation, and the implementation is being proposed to the Linux Foundation's AI and Data community.

---

## Prior art

To keep this space free from patent capture, the project publishes **60 defensive prior-art disclosures** under CC0, covering cryptographic identity, media provenance, voice biometrics, AI safety, post-quantum cryptography, and AI coding governance. See [docs/disclosures](docs/disclosures/README.md).

---

## Use cases

- **Financial services.** A signed, accountable record of every trade or transfer an agent makes.
- **Healthcare.** An auditable trail for every access to patient data.
- **Customer service.** Proof of which agent touched which customer record, and on whose authority.
- **Agent to agent.** When one organization's agent calls another's, each can verify the other before acting.

---

## Documentation

- [Developer guide](docs/vouch_guide.md)
- [Specification](https://vouch-protocol.com/specs/)
- [Hybrid post-quantum guide](docs/hybrid-pq-implementation-guide.md)
- [Threat model](docs/THREAT_MODEL.md)
- [Integrations](vouch/integrations)
- [Examples](examples)

## Community

- Discord: [join](https://discord.gg/mMqx5cG9Y)
- GitHub Discussions: [start one](https://github.com/vouch-protocol/vouch/discussions)
- X: [@Vouch_Protocol](https://x.com/Vouch_Protocol)

## License

Apache 2.0. Free for commercial and open-source use. The 60 prior-art disclosures are CC0.

Built by [Ramprasad Gaddam](https://www.linkedin.com/in/rampy).

## Contributing

Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md). The most useful help right now: more framework integrations, more interop test vectors, tutorials for regulated sectors, and independent security review.
