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

# Support

Get help with deployments, integrations and compute operations.

Email <support@kinesis.network> for account, deployment and infrastructure questions. For community discussion, join the [Kinesis Discord](https://discord.gg/ur9g7EctPt).

## Help us reproduce the issue

Include the operation you attempted, the time and time zone, the app or project ID, and the behavior you expected. For API or MCP failures, add the error code and request ID if one was returned.

A short, redacted log excerpt or minimal request example helps. Remove API keys, access tokens, passwords, payment information and environment variable secrets before sharing it.

## Useful starting points

| Issue                                             | Guide                                                                                                                                                                                                                               |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| App will not start, or an endpoint is unavailable | [Monitor and troubleshoot](https://docs.kinesis.network/getting-started/running-llms-with-kinesis-network/monitoring-apps.md)                                                                                                       |
| API authentication or missing permissions         | [Authentication and scopes](https://docs.kinesis.network/api/authentication.md)                                                                                                                                                     |
| API error or failed asynchronous operation        | [Errors and recovery](https://docs.kinesis.network/api/errors.md)                                                                                                                                                                   |
| MCP client cannot connect or cannot see a tool    | [Connect an MCP client](https://docs.kinesis.network/mcp/connect.md)                                                                                                                                                                |
| Choosing or contributing infrastructure           | [Compute options](https://docs.kinesis.network/getting-started/running-llms-with-kinesis-network/understanding-compute-sources.md) · [Provider guide](https://docs.kinesis.network/getting-started/kinetization-of-idle-compute.md) |


---

# 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.kinesis.network/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.
