Lookio Docs
Lookio websiteOpen Lookio
LogsList the answer logs
logs

List the answer logs

Every answer Lookio produced, one line each, whatever asked: a member in the chat, Lookio AI, an API key (REST, CLI, SDK), the MCP server, a widget's visitor. Latest first, with the assistant, who asked, the query mode, what it cost, how long it took, and the conversation it belongs to when it was kept. No question or answer text: read the conversation with GET /v1/logs/conversations/{conversation_id}. Filter by channel, assistant_id, widget_id, api_key_id, member_id, mode and from/to, and paginate with cursor. Members' own chats are visible to admins only, as lines without content, and never to an API key. Costs nothing.

GET/v1/logs/answers

Requires usage:read.

One line per answer, whatever asked: a member in the app’s chat (chat), Lookio AI (lookio_ai), an API key through REST, the CLI or the SDK (api), the MCP server (mcp) or the visitor of a widget (widget). Results come latest first, and you page with cursor, an opaque string: pass next_cursor back unchanged. See Pagination.

A line holds metadata only: the assistant, who asked, the query mode, the model, the tokens, the credits it cost, how long it took, and whether the resources held an answer (answered is false for a free no-answer). It never holds the question or the answer. When the exchange was kept, conversation_id leads to it: read it with Retrieve a logged conversation, which needs assistants:write. An answer sent with store: false has no conversation, and shows as api.

Narrow the list with channel (comma-separated), assistant_id, widget_id, api_key_id, member_id, result (answered or no_answer), mode and from and to. result=no_answer finds the questions your resources could not answer.

A member’s own chats appear to admins only, as lines without content, and never to an API key. See Logs. The figures over the same filters are in Retrieve the figures of the answer logs.

Authorizations

Authorizationbearerin headerrequired

Query parameters

channelstringlength: ≥ 1 chars

Only the answers from these channels, comma-separated: chat (a member in the app's chat), lookio_ai (the in-app agent), api (an API key through REST, the CLI or the SDK), mcp (the MCP server), widget (a visitor of a widget). Default: all.

assistant_idstringpattern: ^ast_[abcdefghjkmnpqrstuvwxyz23456789]{12}$

Only the answers of this assistant.

widget_idstringpattern: ^wdg_[abcdefghjkmnpqrstuvwxyz23456789]{12}$

Only this widget's answers.

api_key_idstringlength: 1–64 chars

Only the answers asked with this API key.

member_idstringlength: 1–64 chars

Only this member's answers (admins).

modestringlength: 1–40 chars

Only this query mode (flash, fast, deep…).

fromstring

Only answers since this ISO 8601 date or timestamp.

tostring

Only answers until this ISO 8601 date or timestamp.

cursorstringlength: 1–200 chars

Pass next_cursor from the previous page, unchanged.

limitintegerrange: 1–100

Number of items to return. Values outside 1-100 are clamped, and the response reports the limit actually applied.

Response

application/json

List the answer logs

dataobject[]required
has_morebooleanrequired

True when another page follows: pass next_cursor back as cursor.

next_cursorstringnullrequired

Pass it back unchanged as cursor. Null on the last page.

limitintegerrequired

The page size actually applied.

request_idstringrequired

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.