> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/learning-docs/decentralized-id/credentials/what-is-a-vp.md).

# What is a Verifiable Presentation?

A Verifiable Presentation is a combination of [Verifiable Credentials](/product/learning-docs/decentralized-id/credentials/what-is-a-vc.md), bundled together into a format to present to a third party.

Like VCs, Verifiable Presentations contain proofs (i.e. they can be signed with cryptographic keys). In this regard, a major difference between VCs and Verifiable Presentations is that Verifiable Presentations **are signed with cryptographic keys of the holder** to prove, for example, that the actor who is sharing the Verifiable Presentation is also the credential subject of the underlying VCs.

With some credential formats like AnonCreds, holders can freely choose which information (from underlying VCs) they include in a Verifiable Presentation and thus, share with a relying party. It is even possible for holders to prove to a relying party that they possess a certain attribute or fulfil certain conditions without disclosing details (e.g. the proof that one is older than 18 without revealing the real age) via so-called 'Zero Knowledge Proofs'.

There are multiple standards used for Verifiable Presentations, that will be listed below:

### Aries Present Proof

{% embed url="<https://github.com/hyperledger/aries-rfcs/blob/main/features/0454-present-proof-v2/README.md>" %}

### Presentation Exchange 2.0.0

{% embed url="<https://identity.foundation/presentation-exchange>" %}


---

# 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://docs.cheqd.io/product/learning-docs/decentralized-id/credentials/what-is-a-vp.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.
