> 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/quickstart.md).

# Try the Live Demo

{% hint style="success" %}

### Run it yourself → [**demo.empe.io**](https://demo.empe.io/)

About five minutes. No account, no code, nothing to set up — the demo even installs the wallet app for you if you don't have it yet.
{% endhint %}

The fastest way to understand verifiable credentials is to hold one.

The demo leads you by the hand from start to finish. It plays both institutions for you: first the **issuer** that signs a document and hands it to you, then the **verifier** that asks you to prove it. You hold the wallet. A progress bar across the top — **Choose → Claim → Verify → Done** — tells you where you are, each screen tells you exactly what to tap, and the page reacts live as your phone scans.

At the end the verifier confirms your document is genuine without ever contacting the issuer: no database lookup, no phone call, no waiting. That is the whole idea, and five minutes of clicking explains it better than any page of documentation can.

***

## One Platform, Every Industry

The demo is not a single canned flow. It ships eleven scenarios drawn from different sectors, and every one of them runs on the same infrastructure — the same issuing, the same wallet, the same verification. Nothing is rebuilt per industry.

| Industry            | Credential            | Issued by                                  | Checked by                                 |
| ------------------- | --------------------- | ------------------------------------------ | ------------------------------------------ |
| Workplace access    | Employee Badge        | An employer                                | The same employer — at the office door     |
| Proof of employment | Employment Credential | An employer                                | A bank or a landlord — a different company |
| Know Your Customer  | Identity (KYC)        | A bank, after its KYC check                | Another service — an exchange or a telco   |
| Compliance          | AML Screening         | A compliance provider, after AML screening | A bank or a fintech, at onboarding         |
| Education           | University Diploma    | A university                               | An employer, during recruitment            |
| Government ID       | Driver's License      | A licensing authority                      | A car rental company                       |
| Access & entry      | Event Ticket          | The event organizer                        | The same organizer — at the gate           |
| Loyalty & tiers     | Membership Card       | A loyalty program                          | A store, at checkout                       |
| Health              | Vaccination Record    | A clinic                                   | An airline or a venue                      |
| Supply chain        | Product Passport      | The manufacturer                           | A distributor or customs                   |
| Civil registry      | Birth Certificate     | The civil registry office                  | Another office or a bank                   |

Two patterns run through that list, and both matter commercially:

* **One company on both sides.** The employer checks its own badge at the door; the organizer checks its own ticket at the gate. Credentials replace a proprietary access system, and the check keeps working with no connection to a backend.
* **Two different companies.** A bank relies on a compliance provider's AML screening; a recruiter accepts a university's diploma; a landlord accepts an employer's confirmation. The expensive work is done **once** and reused by everyone downstream, instead of every institution repeating the same check.

That second pattern is where the cost disappears: one KYC check, one AML screening, one diploma verification — issued once, accepted anywhere, with no integration built between the issuer and the verifier. On our platform a company can take either role, or both.


---

# 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/quickstart.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.