Lookio Docs
Lookio websiteOpen Lookio
Platform 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 is a credential for your workspace, for a script, an automation or a server. It belongs to the workspace rather than 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 see the page read-only.

Create a key

Choose Create key and name it. Full access is selected by default, including scopes for capabilities that are not active yet. Choose a narrower preset or adjust the scopes before creating the key.

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.

Open Advanced to tick scopes one by one. The meaning of each scope is on the Authentication page.

For an SDK key that only asks assistants 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. A key limited this way can only use those, and cannot create new ones.

A key looks like sk_live_.... Lookio shows it once, then stores only a hash. If you lose it, revoke it and create another. A workspace can hold up to 10 active keys.

Rotate and revoke

  • Rotate creates a new key and stops the old one right away. Copy the new key, then update whatever used the old one.
  • Revoke stops a key at once. It cannot be undone.
  • 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 tied to that person. The Connections section lists each one with who approved it, what it may do and when it was last used. An admin can revoke any connection. A revoked connection loses access immediately, and its owner can connect again.

A connection acts with its owner’s permissions. See Members and permissions.

Connection tokens are valid for 30 days and renew with a refresh token that lasts 90 days, which the CLI handles 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 carries 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.