> For the complete documentation index, see [llms.txt](https://docs.tradecraft.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradecraft.fi/support/get-help.md). # Get Help We are available to help if you are having trouble with a transaction or have questions about how to use Tradecraft. **Support Availability Schedule** Our support team is online during the following times: * 9am - 5pm Monday through Friday, US Eastern time. * Excluding US holidays. Depending on the time your request was received it may take up to 72 hours to receive a response due to weekends and holidays. Email: ``` support@tradecraft.fi ``` {% hint style="info" %} **Our only support channel is our official support email address.** Accounts offering support on X, Telegram, or elsewhere are not us. Be wary of scams. We will never ask you to send us funds or to reveal your seed phrases. {% endhint %} --- # 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.tradecraft.fi/support/get-help.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 `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.