Skip to main content
Structured feedback lets agents label prior Lithtrix results as helpful, unhelpful, or wrong. Events are append-only; ref_id is not validated against your data (fast path). Avoid secrets and PII in note (≤500 characters). Discovery version 2.1.0 includes a feedback block in GET /v1/capabilities with tier limits and vocabulary.

​
POST /v1/feedback

curl -X POST https://lithtrix.ai/v1/feedback \
  -H "Authorization: Bearer ltx_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "ref_type": "search_id",
    "ref_id": "550e8400-e29b-41d4-a716-446655440000",
    "signal": "helpful",
    "note": "optional"
  }'

​
Body

FieldTypeRequiredDescription
ref_typestringYessearch_id, memory_key, blob_id, or parse_id
ref_idstringYesOpaque id (e.g. _lithtrix.search_id from search)
signalstringYeshelpful, unhelpful, or wrong
notestringNo≤500 characters

​
Success (201)

{
  "status": "success",
  "feedback_id": "uuid",
  "_lithtrix": {
    "served_by": "lithtrix.ai",
    "register_url": "https://lithtrix.ai/v1/register",
    "discover_url": "https://lithtrix.ai/.well-known/ai-agent.json",
    "guide_url": "https://lithtrix.ai/v1/guide"
  }
}

​
Errors

HTTPerror_codeWhen
422INVALID_REF_TYPEref_type not in allowed set
422INVALID_SIGNALsignal not in allowed set
422NOTE_TOO_LONGnote over 500 characters
422INVALID_REF_IDEmpty ref_id
429FEEDBACK_LIMITMonthly tier cap (UTC month); includes upgrade_url
See Errors for the common envelope shape.

​
GET /v1/feedback/stats

curl https://lithtrix.ai/v1/feedback/stats \
  -H "Authorization: Bearer ltx_your_key"
Returns rolling UTC aggregates for the authenticated agent: last_7d, last_30d, by_ref_type (counts per ref_type × signal), plus limit and remaining for the current UTC calendar month (same caps as POST).

​
MCP