Lookio Docs
Lookio websiteOpen Lookio
SharePublic assistants
Share

Public assistants

Make an assistant public so any Lookio workspace can ask it with its own credits, earn 20% of what they spend, and ask the public assistants of others.

A public assistant is in the Public assistants directory. Any Lookio workspace can find it and ask it from its Chat, the API, the MCP server or the CLI, with its own credits.

The Public assistants directory with three cards: EU VAT for freelancers, Contract clause explainer and GDPR basics, with their publishers

The directory: each public assistant with its description and its publisher.
flowchart LR O["Another workspace<br/>asks your assistant"] -- "pays the mode's price" --> L["Lookio"] L -- "20% of those credits,<br/>early next month" --> Y["Your workspace"]
Who pays, who earns

Making one of yours public

Open the assistant, then the Public tab, or Make it public in its ⋯ menu. Write the description for the directory, 40 to 1,000 characters: what it answers, from which sources, for whom. Lookio reviews every request before it lists the assistant.

The Public tab of the Sales assistant, where you write the public description and send it for review

  • You earn 20% of the credits that other workspaces spend on it. Lookio adds them to your balance early the next month. Billing shows them as Public assistant earnings.
  • Its setup stays yours. Others see its name and description, never its context, guidelines or resources. Its answers cite passages but do not link your files.
  • Their questions stay theirs. Conversations stay in the workspace that asks. The Public tab shows numbers only: questions, workspaces, credits and your share. It never shows what they ask.
  • Its description stays as approved. To change it, unpublish the assistant, edit the description and send it again for review.
  • Unpublish removes it from the directory at once. Lookio refuses the next question from another workspace.

Only workspace admins make an assistant public.

Asking the assistants of others

Open Assistants, then Public assistants. Search the directory, open an assistant and choose Add to Chat. It joins the Chat’s assistant list, with a globe.

From the API, MCP or CLI, ask it by its id, like your own assistants: POST /v1/assistants/{id}/query, ask_assistant or lookio ask. Your conversations with it stay in your workspace, in your Logs and Usage. To browse the directory or publish, use lookio public and lookio assistants publish or the MCP tools.

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.