> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/guides/installing/contact-support.md).

# Contact support

Where can I find support for Leather?

You can contact our support team by email at <support@leather.io>.

{% hint style="info" %}
**We will never initiate support by contacting you via direct message on any platform.** If someone messages you directly offering help or claiming to work for Leather, they are almost certainly a scammer.
{% endhint %}

{% hint style="warning" %}
**It is imperative that you never provide your Secret Key or any personally identifiable information to anyone when seeking wallet support.** This includes never giving this information to genuine Leather staff, either proactively or upon request since it will never be needed to resolve your problem. Keep this information confidential at all times.
{% endhint %}

You may see the following Leather team members within the community who can assist you:

* **Werner** ([@Drinknu](https://twitter.com/drinknu) on Twitter, werner.btc on Discord ID: 689879505644552245, @Werner3141 on Telegram, [@314159265359879](https://github.com/314159265359879) on GitHub, werner.btc on Stacks)<br>
* **DeeList.btc** (@DeeList7 on Twitter, DeeList.btc#0001 on Discord ID: 486818375561904128 and deelist.btc on Stacks)<br>

<br>


---

# 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://leather.gitbook.io/guides/installing/contact-support.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.