> For the complete documentation index, see [llms.txt](https://altme-documentation.gitbook.io/altmes-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://altme-documentation.gitbook.io/altmes-documentation/introduction/altme-solution-suite-is-made-up-of-3-components.md).

# Altme solution suite is made up of 3 components

Altme offers 3 components to implement SSI in Web3 applications. On the other hand, it is important to appreciate that the strength of the SSI model is interoperability and therefore all the components offered by Altme are available in open source and implement **protocols and standards recognized by the W3C and shared by the community**.

* **Altme Wallet** : The user friendly SSI mobile wallet for web3 applications
* **Altme Saas** : The next generation platform to build Issuers and Verifiers in minutes
* **Altme Web3 Issuer** : A trusted issuer of Web3 verifiable credentials

The open source repositorory is available there : <https://github.com/TalaoDAO> .


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://altme-documentation.gitbook.io/altmes-documentation/introduction/altme-solution-suite-is-made-up-of-3-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.