Report wrong fact
POST/v1/reports
Name one of your responses, the item in it, and what is wrong; people review it, and the outcome is yours by report ID. Needs the write_requests or the account scope.
- scope
- write_requests
- auth
- Bearer key
- operationId
- ReportWrongFact
- MCP tool
- report_wrong_fact
Request body
application/json · ReportCreate · no other fields
| Field | Type | Required | Limits | Holds |
|---|---|---|---|---|
| response_id | ResponseID | yes | A response's ID. It replays and compares that exact response. | |
| fact_version_id | VersionID | yes | ||
| claim | string | yes | 1 to 2000 characters | What is wrong with the item, in words. |
Response
200 · ReportResponse. The report, received.
| Field | Type |
|---|---|
| report | Report |
Problems
RFC 9457 application/problem+json. An abstention is not one of these: it is a 200.
| HTTP | Code | When |
|---|---|---|
| 400 | INVALID_REQUEST | Malformed JSON, unknown fields, bad filter, limit exceeded |
| 401 | UNAUTHENTICATED | Missing, malformed, or revoked key |
| 403 | FORBIDDEN_SCOPE | The key lacks the required scope |
| 413 | PAYLOAD_TOO_LARGE | Body or upload over the limit |
| 422 | UNPROCESSABLE | Well-formed but semantically invalid |
| 429 | RATE_LIMITED | Rate limit or per-tenant model cap |
| 500 | INTERNAL, POLICY_ASSERT_FAILED, RESPONSE_UNREPLAYABLE | Server fault. The last two also alert |
| 503 | STORE_UNAVAILABLE, LLM_UNAVAILABLE, LOG_UNAVAILABLE | A dependency is down or a budget tripped |
| 504 | TIMEOUT | A deadline was exceeded |