Support

Channel	Best for	Where
Status page	"Is Brain up?"	status.brain.fi
Documentation	Reference and guides	docs.brain.fi
GitHub Discussions	Public questions, integration help	github.com/braindotfi/brain-core/discussions
Discord	Real-time community help	discord.brain.fi
Email	Specific failed requests	[e-mail]
Security	Vulnerabilities only	[e-mail]

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.

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 [e-mail] directly. Do not file public issues for security vulnerabilities. Brain runs a public bug bounty; details are on the security page.