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

# Support

| Channel                | Best for                           | Where                                                                                                |
| ---------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Status page**        | "Is Brain up?"                     | [status.brain.fi](https://status.brain.fi)                                                           |
| **Documentation**      | Reference and guides               | [docs.brain.fi](https://docs.brain.fi)                                                               |
| **GitHub Discussions** | Public questions, integration help | [github.com/braindotfi/brain-core/discussions](https://github.com/braindotfi/brain-core/discussions) |
| **Discord**            | Real-time community help           | [discord.brain.fi](https://discord.brain.fi)                                                         |
| **Email**              | Specific failed requests           | <support@brain.fi>                                                                                   |
| **Security**           | Vulnerabilities only               | <security@brain.fi>                                                                                  |

### When Opening a Ticket

The single most useful thing you can include is a **request ID** (the `request_id` field on every error envelope; `err.requestId` in the SDK). Every API and MCP response carries one. Pasting a request ID lets the support team pull the exact request, the policy version that evaluated it, and the audit event that recorded it.

```typescript
try {
  await brain.pay("acme", { invoiceId: "inv_8231" });
} catch (err) {
  console.log(err.requestId); // include this in the ticket
}
```

### SLAs

| Plan           | First response   | Channels                                 |
| -------------- | ---------------- | ---------------------------------------- |
| **Sandbox**    | Best effort      | Discord, GitHub                          |
| **Developer**  | 1 business day   | Email, Discord                           |
| **Production** | 4 business hours | Email, Discord, dedicated Slack          |
| **Enterprise** | 1 hour, 24/7     | All of the above plus on-call escalation |

### Reporting a Security Issue

Please email <security@brain.fi> directly. Do not file public issues for security vulnerabilities. Brain runs a public bug bounty; details are on the security page.


---

# 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.brain.fi/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.