> For the complete documentation index, see [llms.txt](https://docs.meeco.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meeco.me/latest/guides/presentations.md). # Presentations Presentation, short for [Verifiable Presentation](https://www.w3.org/TR/vc-data-model/#presentations), is a data model that allows a holder of [Verifiable Credentials](https://www.w3.org/TR/vc-data-model/#credentials) to present them in a way that that the Verifier can attest the authorship of the credentials included. The data format used for the presentation is [vp-jwt](https://www.w3.org/TR/vc-data-model/#json-web-token). Other formats are not supported at this time. ## Prerequisites * [DID](/latest/guides/dids/did-methods.md) * Credentials ## Who can use this? Presentations are generated by the holder and verified by an organisation or another user. ## Generate Verifiable Presentation Generate a verifiable presentation, ready for signing. **Endpoint** ```bash POST /presentation/generate ``` **Request** * DID * List of VCs **Responses** The presentation object that includes an unsigned JWT. The client calling this endpoint (e.g. holder wallet) is responsible for adding the signature. ## Verify Verifiable Presentation Verify a given verifiable presentation. The steps performed during this verification are * Validate the presentation structure * Resolve the presentation DID * Verify the presentation signature * For each credential in the presentation * Validate the credential structure * Resolve the issuer DID * Verify the credential signature **Endpoint** ```bash POST /presentation/verify ``` **Request** * Verifiable Presentation – supported format is vp-jwt **Responses** The result of the verification, either true or false. In case of false, all errors are provided, with an explanation. --- # 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.meeco.me/latest/guides/presentations.md?ask=&goal= ``` `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.