> 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/esignet-authentication/develop/integration.md).

# Integration Guides - eSignet

Explore seamless eSignet integration with guides on authentication, digital wallets, and more.

This section contains various guides and information that could benefit:

* Organizations, nations, and ID registries have an identity solution with authentication capabilities to enable Open ID connect-based authentication.
* Relying parties or service providers from countries where the eSignet solution is deployed.
* Digital wallets are those who want to integrate with eSignet and provide wallet-based authentication solutions or store verifiable credentials in their wallets.

For more information on how to get started with these integrations, read through:

<table data-column-title-hidden data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;">Explore how to implement and integrate the Authenticator plugin for user authentication with eSignet.</mark></td><td></td><td><a href="/home/esignet/esignet-authentication/develop/integration/authenticator.md">Authenticator Plugin</a></td></tr><tr><td><mark style="color:blue;">Explore how to bind an individual's ID with a public key to enable secure token-based authentication.</mark></td><td></td><td><a href="/home/esignet/esignet-authentication/develop/integration/key-binder.md">Key Binder Plugin</a></td></tr><tr><td><mark style="color:blue;">Explore how to bind user IDs with public keys for wallet authentication.</mark></td><td></td><td><a href="/home/esignet/esignet-authentication/develop/integration/audit.md">Audit Plugin</a></td></tr><tr><td><mark style="color:blue;">Explore how digital wallets</mark> <mark style="color:blue;">store credentials and enable authentication in eSignet.</mark></td><td></td><td><a href="/home/esignet/esignet-authentication/develop/integration/wallet.md">Digital Wallet</a></td></tr><tr><td><mark style="color:blue;">Explore setup steps, OIDC client registration, authentication flow, and integration best practices.</mark></td><td></td><td><a href="/home/esignet/esignet-authentication/develop/integration/relying-party.md">Relying Party</a></td></tr></tbody></table>


---

# 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/esignet-authentication/develop/integration.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.