# Page Not Found

The URL `modules/partner-management-services/device-provider-partner` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Device Provider](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/pms-existing/device-provider-partner.md)
- [Device Provider](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/functional-overview/device-provider.md)
- [Auth Partner](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/pms-existing/auth-credential-partner.md)
- [Foundational Trust Provider](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/pms-existing/ftm-partner.md)
- [Module Configurations](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-services/module-configuration.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/pms-existing/device-provider-partner.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.mosip.io/1.2.0/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.mosip.io/1.2.0/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/1.2.0/id-lifecycle-management/support-systems/partner-management-services/pms-existing/device-provider-partner.md`).

You may also use `Accept: text/markdown` header for content negotiation.