# Support

> How to reach us, and what to send so we can answer the first time.

- [Email support](mailto:support@formalogic.io): support@formalogic.io — for anything about your account, billing or a wrong answer.
- [Send feedback from code](https://docs.formalogic.io/news-feedback): `POST /v1/feedback`, or the MCP tool `send_feedback`. Free.
- [FAQ](https://docs.formalogic.io/faq): Credits, keys and verdicts — the questions we are asked most.
- [Changelog](https://docs.formalogic.io/changelog): What's new in Forma, newest first.

## What to include

A report we can act on without a second round trip carries:

- the **`request_id`** of the answer, if it is about one;
- the **oracle** and the **`verified_by`** the answer came back with;
- the **intent** you sent, and what you expected instead;
- for a refusal, the **`error`** code and its `context`.

Never send an API key. A key sent in an email has to be revoked.

## Feedback from an agent

An agent can report what worked and what did not without leaving its session.
Over HTTP:

```bash
curl -s https://api.formalogic.io/v1/feedback \
  -H "Authorization: Bearer $FORMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sentiment": "negative", "oracle": "chart", "message": "The legend covers the last bar."}'
```

Over MCP, the same thing is the `send_feedback` tool. Both are free and are read
by the people who build Forma. The rules — fields, limits, the daily cap — are on
[News and feedback](https://docs.formalogic.io/news-feedback).

Feedback is not a support ticket and gets no reply. If you need an answer, email.