Lookio Docs
Lookio websiteOpen Lookio
AssistantsPublish an assistant
assistants

Publish an assistant

Asks Lookio to list the assistant in the directory of public assistants, with this description (what it answers, from what, for whom). Lookio reviews every request; once approved, any Lookio workspace may ask it and pays its own credits, and you earn 20% of what others spend on it, as credits, each month. Its context, guidelines and resources stay private. While it waits for review, sending again changes the description. A public assistant keeps the description Lookio approved: to change it, unpublish it and ask again (conflict otherwise). Admins only.

PUT/v1/assistants/{assistant_id}/publication

Authorizations

Authorizationbearerin headerrequired

Path parameters

assistant_idstringrequiredpattern: ^ast_[abcdefghjkmnpqrstuvwxyz23456789]{12}$

Body

application/jsonrequired
descriptionstringrequiredlength: 40–1000 chars

What the directory shows: what it answers, from what kind of sources, for whom. 40 to 1,000 characters. Its context, guidelines and resources stay private.

Response

application/json

Publish an assistant

dataobjectrequired
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.