> For the complete documentation index, see [llms.txt](https://docs.everesteer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.everesteer.ai/resources/support.md).

# Support

How to reach us.

{% columns %}
{% column %}
{% hint style="info" %}
**Email.** <support@everesteer.ai>
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="success" %}
**Discord.** [Join the server](https://discord.gg/GXue2tZaz)
{% endhint %}
{% endcolumn %}
{% endcolumns %}

## What to include in a report

A report with these four items is usually answered in one round:

1. **Key fingerprint.** From the MCP `whoami` tool. It identifies your key without ever sending us the key itself.
2. **The id of the failing call.** An `upload_id` for an event upload, or a `submission_id` for a tournament submission.
3. **Timestamp in UTC.** To the minute, so logs can be matched to your call.
4. **The exact error text** you received, including any status code.

{% hint style="danger" %}
Never send your API key, not even to support. The fingerprint from `whoami` is enough to find your account.
{% endhint %}

For scoring questions, include the `exped` and the `model_id` involved. For staking questions, include the wallet address and the round.


---

# 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://docs.everesteer.ai/resources/support.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.