> For the complete documentation index, see [llms.txt](https://docs.remede.camarm.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remede.camarm.fr/readme.md). # Welcome Welcome to the Remède Documentation Center ! Here you can understand what is Remède, how to use it, and how you can enhance it. {% hint style="info" %} This new documentation can contains broken links and errors. You can help us improving it on Github ! Thank you {% endhint %} The Remède Project is an open source project whose goal is to provide a free, privacy respectful dictionary experience for everyone, everywhere. We also distribute our own dictionaries, in an open format. ### Jump right in
User DocumentationLearn how to use Remède.DownloadSupportGroup 2101.pngFor the users
Developers documentationDevelop on Remède !APIGetting startedGroup 2099.pngFor the developers
DatabaseWe build our own dictionaries databases.Remède for your projectCreditsGroup 2098.pngDatabase
The Remède ProjectDiscover what is Remède.StoryContributingGroup 2100(1).pngProject
``` Remède by The Remède Project © 2023-now CECILL-2.1. Dictionary databases includes data from third-parties services governed by other free licenses. See https://docs.remede.camarm.fr/database/credits for further information. ``` --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.remede.camarm.fr/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.