> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet-2.0.0/local-deployment/local-setup/mock-id-system.md).

# Mock Identity System

### What It Is

The Mock Identity System is a mock implementation of an identity system, provided so developers can use it for local development and testing of eSignet. It exposes endpoints to:

* Create an individual
* Get an individual's data
* Authenticate an individual
* Send an OTP
* Share KYC data about the individual, post-authentication

It supports the same authentication factors a real identity system would: PIN-based authentication, OTP authentication, and biometric authentication.

### Why It's Used

eSignet is designed to connect to an identity system via an [Authn Provider](/home/esignet-2.0.0/develop/integration/authenticator.md) built specifically for that purpose, but a real government or enterprise identity system usually isn't something a developer has, or should have, access to in a local environment. The Mock Identity System stands in for that real system, so eSignet's full authentication flow can run end to end on a local machine, without any external dependency or access to production identity data.

It's brought up automatically as part of both Docker Compose files described under [Local Setup](/home/esignet-2.0.0/local-deployment/local-setup.md).

### Repository and Setup

{% hint style="info" icon="github" %}
**Codebase**: [esignet-mock-services](https://github.com/mosip/esignet-mock-services/tree/master)
{% endhint %}

{% hint style="info" icon="github" %}
**Setup guide (README)**: [mock-identity-system README ](https://github.com/mosip/esignet-mock-services/blob/master/README.md)
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.esignet.io/home/esignet-2.0.0/local-deployment/local-setup/mock-id-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.