> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/getting-started/tutorial/overview.md). # Overview This tutorial guides you through creating a working environment that issues and verifies Verifiable Credentials within the Empeiria ecosystem. **What You Will Learn:** * How to create and configure an Issuer and Verifier using the One-Click Deployment platform. * How to securely store `clientSecret` values to interact with Issuer and Verifier services. * How to run a simple Express-based backend that integrates with the Issuer and Verifier. * How to create a credential schema and issue credentials. * How to implement verification logic that ensures only holders of valid credentials can access certain resources. * How to set up a simple frontend that displays QR codes for issuance and verification flows. * How to test the full flow using a reference mobile wallet application (iOS/Android). **Prerequisites:** * Access to the [One-Click Deployment platform](https://oneclick.empe.io/). * Node.js, npm, and Express installed. * Basic knowledge of JavaScript/TypeScript and Node.js. * A reference Empe DID Wallet: * Android: * IOS: By the end of this tutorial, you\`ll have a demo that issues a "KYC Verifiable Credential" and verifies it to grant access to a protected dashboard. --- # 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.empe.io/getting-started/tutorial/overview.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.