> For the complete documentation index, see [llms.txt](https://docs.toolkit.equs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolkit.equs.ai/standards/about-the-system/components.md).

# Components

The building blocks of EQUS DTK: the Control, Integration and Protocol APIs, the Mobile and Web Wallets, and Embedded UI for issuance, presentation and wallets.

This page gives a high-level view of the main platform components and where each one fits in your credential journey.

{% hint style="info" %}
Authentication and access management are documented separately in [Authentication](/standards/api/authentication.md).
{% endhint %}

<figure><picture><source srcset="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FfTbrQnWQR7U868b3hbK1%2FEQUS_Wallets_and_APIs_dark.svg?alt=media&amp;token=056d48a8-8df3-481f-8b54-68ff1a456790" media="(prefers-color-scheme: dark)"><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2Ft3sBiqB44z0ff20kQ5hy%2FEQUS_Wallets_and_APIs_light.svg?alt=media&amp;token=eebff6c7-b632-4ea1-a3f3-d86fcef161dd" alt=""></picture><figcaption></figcaption></figure>

### Platform APIs ⚙️ <a href="#id-2.4.1-apis" id="id-2.4.1-apis"></a>

These APIs are your side of the platform: they let you act as Issuer and Verifier.

<table><thead><tr><th width="200">Component</th><th>Description</th></tr></thead><tbody><tr><td><a href="/api/control-api.md"><strong>Control API</strong></a></td><td>Administrative API for configuration, platform operations, and flow setup for Issuance, Presentation, and revocation.</td></tr><tr><td><a href="/api/integration-api.md"><strong>Integration API</strong></a></td><td>Primary integration API for your back-end services to start and manage Issuance and Presentation flows.</td></tr><tr><td><a href="/api/control-api.md"><strong>Protocol API</strong></a></td><td>Handles low-level protocol operations and metadata, such as did:web documents. Wallets and the platform call it; you won't need to.</td></tr></tbody></table>

### Wallets :hand\_splayed: <a href="#id-2.4.2-uis" id="id-2.4.2-uis"></a>

These components support the user side of the platform and related custodial wallet integrations. In Decentralized Identity terms, the wallets serve the **Holder** role, while the API can also be reused by machine agents and other server-side applications.

| Component                                                                                    | Description                                                                                                                                                                                          |
| -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p></p><p><a href="/standards/wallets/equs-wallet.md"><strong>Mobile Wallet</strong></a></p> | Non-custodial mobile wallet for users who would like to keep control of their own keys and credential storage.                                                                                       |
| [**Web Wallet**](/standards/wallets/web-wallet.md)                                           | Custodial web wallet for users. Use it standalone, or embed it in your web app.                                                                                                                      |
| [**Web Wallet API**](/api/web-wallet-api.md)                                                 | API for the Web Wallet and other custodial wallet operations. It serves two main consumers: user-facing Web Wallet experiences and machine agents that reuse the same custodial wallet capabilities. |

{% hint style="info" %}
The **Web Wallet** is disabled by default and is only available on request.
{% endhint %}

### Embedded UI 🖼️ <a href="#id-2.4.2-uis" id="id-2.4.2-uis"></a>

These web-only components let you embed user-facing Decentralized Identity journeys into your sites and applications. They support **Holder** interactions for flows initiated by your **Issuer** and **Verifier** systems. They are rendered through `iframe`-based integrations.

| Component                                                                                                                                   | Description                                                                                                              |
| ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| [**Embedded UI for Issuance**](/standards/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery/method-2-api-+-embed-ui.md) | Embeddable UI that guides users through the credential Issuance flow inside your site or application.                    |
| [**Embedded UI for Presentation**](/standards/presentation/flows-1-and-2/embed-ui-and-api.md)                                               | Embeddable UI that guides users through the credential Presentation flow inside your site or application.                |
| [**Embedded UI for Wallet**](/standards/embedded-ui/embedding-web-wallet.md)                                                                | Embeddable components for integrating the Web Wallet directly into your site. Requires Web Wallet, available on request. |


---

# 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.toolkit.equs.ai/standards/about-the-system/components.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.