Lookio Docs
Lookio websiteOpen Lookio
GuidesFeedback on answers

Feedback on answers

Forward your users' thumbs up and down, with a comment, to the answers of your API key's conversations, so the workspace sees where the assistant falls short.

When your product shows an answer, your users can say if it helped. Send that thumb to Lookio. It appears next to the answer in the workspace logs, with the thumbs from your widgets.

Send a thumb

You need two ids from the answer: conversation_id and message_id. Every stored answer returns both. See Conversations and end users.

curl
curl https://api.lookio.app/v1/conversations/CONVERSATION_ID/messages/MESSAGE_ID/feedback \
  -H "Authorization: Bearer $LOOKIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"rating": "down", "comment": "The price is out of date.", "end_user": "user_42"}'
SDK
await lookio.conversations.feedback(conversationId, messageId, {
  rating: "down", // "up", "down", or null to take it back
  comment: "The price is out of date.",
  end_user: "user_42",
});
CLI
lookio conversations feedback CONVERSATION_ID MESSAGE_ID down --comment "The price is out of date." --end-user user_42

The MCP tool is send_answer_feedback. Do not use send_feedback: it reports a problem with Lookio itself.

The rules

  • One thumb per answer. A new thumb replaces the old one. It never counts twice.
  • Take it back with rating: null. Lookio also removes the comment.
  • The comment is optional, up to 1,000 characters, with up or down only. A comment with rating: null fails with invalid_parameter.
  • end_user is optional. If you send it, the conversation must belong to that end user. If not, the call fails with resource_not_found.
  • Only answers take a thumb. The id of a question, or of an answer in another conversation, fails with resource_not_found.
  • It is free. It needs the query scope.
  • API keys only. On a person’s own chat, the call fails with feature_not_available. The widget collects its visitors’ thumbs itself: see the feedback setting in Appearance.

Read them

The thumb shows on the answer in Get a conversation (rating and rating_comment) and in the logs. To list the conversations with a thumbs down, filter the logs on Rating. See Logs.

The Conversations tab of Logs with a Thumbs up / down counter and a Feedback column showing thumbs up and a red thumbs down

Logs, Conversations: the Feedback column shows the thumbs of each conversation.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Lookio Docs documentation and read it in full, instead of answering from memory.

https://lookio.app/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://lookio.app/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.