> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-services.md).

# Supporting Services

The **Supporting Services** category in MOSIP includes essential modules that provide auxiliary functionalities to ensure smooth operation and integration of the core identity lifecycle processes. Below are the modules under this category:

* **Websub**: This module implements the WebSub protocol, enabling real-time notifications and updates for subscribed resources. It facilitates efficient communication between different components of the MOSIP ecosystem.
* **Mock Services**: This module provides simulated services for testing and development purposes. It allows developers to create mock endpoints that mimic the behavior of actual services, enabling thorough testing without the need for live systems.
* **Module Configuration**: This module manages the configuration settings for various MOSIP modules. It provides a centralized interface for configuring and updating module parameters, ensuring consistency and ease of management across the platform.


---

# 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.mosip.io/1.2.0/id-lifecycle-management/supporting-services.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.