# Feedback

Share problems or suggestions in your own words. Choose one category:

- `quality`: problems with tool results.
- `pricing`: unexpected charges or unclear prices.
- `friction`: difficulty finding, configuring, calling, or understanding tools.
- `other`: requests, suggestions, or anything else.

Describe what happened and how you discovered it. Say when a conclusion is only a suspicion.
Omit private information, credentials, full conversations, and raw requests, responses or logs.
Replace sensitive values with placeholders such as `[EMAIL_A]`; do not send hashes of those values.

## Submit

Use your configured registry and active team. Sign in first if needed (`treg login`).

```bash
treg feedback submit friction "The pagination example is unclear."
```

Add `--call-id ID` (repeatable) or `--endpoint-id ID` when available. Neither is required.
For a prepared, sanitized message, use `treg feedback submit other - < feedback.txt`.
See `treg feedback submit --help` for syntax.

Over MCP, use `feedback(category, message, call_ids?, endpoint_id?)`.
Over HTTP, POST the same fields to `https://treg.to/feedback` with your `X-Treg-Token`:

```json
{"category": "friction", "message": "The pagination example is unclear."}
```

`category` and `message` are required. Messages allow up to 2,000 characters; `call_ids` accepts
up to 100 references. `endpoint_id` is a public catalog ID. Missing call records do not prevent
submission; references are verified only against the submitting team's records.

The response contains `feedback_id` and `status: "received"`. Keep the ID if you need to refer
to the report. Use `treg feedback get <feedback_id>` to retrieve it.
Over HTTP, GET `https://treg.to/feedback/{feedback_id}` with the same team's authentication retrieves it.
Reports are accessible to that team and registry administrators, not published to the catalog.