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

# Get API support

First follow [Troubleshoot API requests](/troubleshooting-and-safety/diagnose-api-failures.md). If the problem remains, contact your existing Mochi implementation or account contact.

## Include this information

* the organization name;
* the UTC timestamp;
* HTTP method and path;
* response status;
* response `X-Request-ID`;
* the API key's name or non-secret prefix;
* whether this was the first attempt or a retry using the same `Idempotency-Key`; and
* a short description of the expected and observed behavior.

## Do not include private data

* the API key or `Authorization` header;
* message text or media;
* email addresses, phone numbers, usernames, or other contact values;
* provider credentials or webhook URLs;
* complete request or response bodies; or
* cursor values unless Mochi specifically requests one through an approved secure channel.

If a key may have been exposed, stop using it and request revocation immediately. Do not wait for the API problem to be diagnosed before revoking a possibly compromised key.


---

# 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.themochi.app/troubleshooting-and-safety/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.