Lookio Docs
Lookio websiteOpen Lookio
GuidesAPI keys

API keys

Create, limit, rotate and revoke the workspace API keys that authenticate the REST API, the CLI and MCP, and review personal connections.

An API key gives a script, an automation or a server access to your workspace. It belongs to the workspace, not to a person, so it keeps working when someone leaves.

Open Developer tools in the sidebar, then the API tab. Only admins can create, rotate and revoke keys. Members can only read the page.

Create a key

Choose Create key and name it. The default is Full access. Choose a smaller preset when the key needs less.

PresetScopes
Ask questionsaccount:read, assistants:read, query
Read onlyaccount:read, usage:read, resources:read, assistants:read
EditorThe read-only scopes, plus resources:write, assistants:write and query. It deletes no resource and no assistant.
Full accessEvery scope, including those that are not active yet.

Developer tools, API tab: the base URL, and the API keys table with two keys and their permissions, and the Create key button circled

Developer tools: the base URL and the workspace's API keys.

To pick scopes one by one, open Advanced. Authentication explains each scope.

For a key that only asks questions, use Ask questions and limit it to the assistants your product needs.

You can also:

  • Set an expiry: 30, 90 or 365 days, or none.
  • Limit the key to some assistants. Such a key uses only those assistants and cannot create assistants.

A key looks like sk_live_.... Lookio shows it once and then keeps only a hash. If you lose it, revoke it and create another. A workspace has at most 10 active keys.

Rotate and revoke

  • Rotate creates a new key and stops the old one at once. Copy the new key, then update what used the old one.
  • Revoke stops a key at once. You cannot undo it.
  • Rename changes the label only. The key does not change.

Personal connections

When someone signs in from the CLI or connects an AI client, Lookio creates a connection for that person. The Connections section lists each one: who approved it, what it may do and its last use. An admin can revoke any connection. A revoked connection stops at once. Its owner can connect again.

A connection has its owner’s permissions. See Members and permissions.

Developer tools, MCP and CLI tab: the MCP server URL, Standard and Code mode, and the Connections list

MCP and CLI: the server address, and the personal connections of the members.

A connection token is valid for 30 days. A refresh token, valid for 90 days, renews it. The CLI does this for you.

API keys or connections

UseFor
An API keyA job, an automation or a backend with no person behind it.
A connectionA person’s CLI or AI client. It has their identity and permissions, and keeps their own chats.

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.