Lookio Docs
Lookio websiteOpen Lookio
DevelopersOverview

Developers

Pick your way into Lookio, the REST API, the TypeScript SDK, the MCP server or the CLI, with how they compare, how they authenticate, and where to start.

Your code can do everything the app does, through the REST API, the TypeScript SDK, the MCP server or the CLI. All four use the same objects, permissions and prices.

flowchart LR P["Your product"] --> API["REST API<br/>api.lookio.app/v1"] P --> SDK["TypeScript SDK<br/>@lookio/sdk"] AG["AI agent"] --> MCP["MCP server<br/>mcp.lookio.app/mcp"] AG --> CLI["CLI<br/>@lookio/cli"] SDK --> API CLI --> API API --> S["Lookio service layer<br/>permissions, credits, logs"] MCP --> S
Four ways in, one service layer

Choose your way in

You want to…UseStart with
Call an assistant from your backend, in any languageREST APIREST API
Do the same from TypeScript or JavaScript, with types and streamingSDKTypeScript SDK
Let Claude, ChatGPT or Cursor read and manage your workspaceMCP serverMCP server
Script Lookio, run it in CI, or let a coding agent drive itCLICLI
Plug Lookio into n8n, Make or ZapierREST API from the automation toolIntegrations
Ask assistants someone shared with youAccess addressCall an access

Two kinds of address

Your workspace

https://api.lookio.app/v1 and https://mcp.lookio.app/mcp.

Use an API key or a personal connection. Manage resources and assistants, ask questions, read logs.

An access

https://api.lookio.app/a/{access_id} and its /mcp.

Open to anyone with the address, or protected by an access key (ak_live_…) for each client. Callers can only ask the assistants it shares. See Call an access.

Authenticate

CredentialLooks likeForGet it
API keysk_live_…Your product, servers, automationsDeveloper tools, then Create key. See API keys.
Personal connectionOAuth, in the browserYou, through the CLI or an MCP clientlookio auth login, or add the MCP server. See Authentication.
Access keyak_live_…People outside your workspaceThe owner of an access.

For a backend, use an API key. It does not depend on a person. Each key has scopes, such as resources:write or query, and can be limited to some assistants. See Authentication and scopes.

Developer tools in the app: the API tab with the base URL https://api.lookio.app/v1 and two API keys

Developer tools: the base URL and the API keys of the workspace.

Your first call

Terminal
curl https://api.lookio.app/v1/assistants/ASSISTANT_ID/query \
  -H "Authorization: Bearer $LOOKIO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"question": "How do I issue a credit note?"}'

The API button on each assistant’s sheet gives this call, in curl, the CLI and JavaScript. For all the steps, see the Quickstart.

Rules that apply everywhere

Machine-readable

  • OpenAPI document: every endpoint, parameter and error code.
  • llms.txt and llms-full.txt: the whole documentation, for an AI agent.
  • Every page is also served as Markdown: add .md to its address.

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.