> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rainbrand.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Report a problem

> Send observations about Rainbrand through the API or MCP and continue your task.

Report bugs, confusing behavior, missing capabilities, misleading documentation, or disappointing results. You do not need to establish the root cause to report an observation about Rainbrand.

Reports go to the Rainbrand team for internal review. They do not open a support conversation or promise a reply.

## Submit a report

Use your existing [API credentials](/api/authentication) or authenticated [MCP connection](/mcp/connect).

Describe what happened, what you expected, and the effect on the task. Leave out credentials, personal or customer data, transcripts, source files, private prompts, and unrelated task content.

**API**

```bash theme={"dark"}
curl https://www.rainbrand.com/api/v1/feedback \
  -H "Authorization: Bearer $RAINBRAND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "The brand response omitted the font files listed in its guidance.",
    "category": "docs_mismatch"
  }'
```

A received report returns:

```json theme={"dark"}
{ "data": { "status": "received" } }
```

See [Submit feedback](/api-reference/feedback/submit-feedback) for the request fields and error contract.

**MCP**

Call `submit_feedback` with a short `message` and, if useful, a `category`, `tool_name`, or `related_id`. Use your connected client's schema for the accepted values. The tool acknowledges receipt and tells you to continue the original task.

Category is optional. Omit it if none fits, rather than inventing a value. Include a Rainbrand-generated resource or operation ID in `related_id` when available; do not paste the resource's contents.

## Continue your task

Report each distinct issue once. Exact duplicate reports from the same account are suppressed for 24 hours across API and MCP, with the same acknowledgement. Both interfaces share a limit of 100 new reports per user per hour. [API-key request limits](/api/usage-limits#api-key-requests) apply separately.

If validation rejects the report, use the accepted values in the error or omit the optional category. If submission is rate-limited or unavailable, continue the original task without repeatedly retrying the report. Do not wait for a reply or poll for feedback status.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.