> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/readme.md).

# Welcome to TradeAware User Guide

We're here to ensure your experience of complying with the EU Deforestation Regulation is simple and seamless. Whether you want to learn about our latest features or need help to resolve technical issues, we're here for you.

## Contact Support <a href="#how-to-get-support" id="how-to-get-support"></a>

If at any time you have challenges or questions when using TradeAware, you can email us directly at [**support@live-eo.com**](mailto:support-tradeaware@live-eo.com). Our team will respond directly to you and provide the necessary assistance.

## Contents <a href="#additional-resources" id="additional-resources"></a>

The TradeAware User Guide contains four high level sections:

* [**Getting Started**](/tradeaware/readme/getting-started.md) - How to create an account in the web app and access your API details.
* [**Using the TradeAware Web App**](/tradeaware/using-the-tradeaware-web-app/settings-guide.md) - Content on how to use the features of the TradeAware application.
* [**Using the TradeAware API**](/tradeaware/using-the-tradeaware-api/api-access-and-business-account-registration.md) - Information on how to use the features in TradeAware via API.
* [**Additional Resources**](/tradeaware/additional-resources/contact-support.md) **-** Additional content about the features and usage of TradeAware.


---

# 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.live-eo.com/tradeaware/readme.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 `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.