Lookio Docs
Lookio websiteOpen Lookio
CLICLI overview

CLI overview

The lookio command-line interface lets you import resources, build assistants and ask questions from a terminal, a CI job or a coding agent.

The lookio command is a thin layer over the REST API. It runs on your machine or in your CI, holds no secret of Lookio’s, and prints JSON automatically whenever its output is not a terminal. It requires Node.js 20 or newer.

Install

The package is @lookio/cli on npm. It needs Node.js 20 or later. Setting Lookio up from an AI agent? See Connect an AI agent.

Terminal
npm install --global @lookio/cli
lookio --help

Or run it without installing:

Terminal
npx @lookio/cli account

The binary is called lookio. The lookio-cli package that is already on npm is the previous generation: it talks to the previous API and has different commands. Do not use it for these pages.

Sign in and check the connection

Terminal
lookio auth login        # opens your browser and stores a token in your OS keychain
lookio account           # the workspace, the plan, the credit balance and what this credential may do
lookio doctor            # connectivity, credential, CLI version and clock skew

For a CI job, use an API key instead of a browser: see Authentication.

Your first questions

Terminal
lookio resources add-url https://example.com/pricing --tags pricing
lookio resources get RESOURCE_ID          # repeat until status is ready or failed

lookio assistants create --name "Support" --follow-tags pricing
lookio ask ASSISTANT_ID "How much does the Pro plan cost?"

Imports do not wait

resources add-text, add-url, add-file, sites add and resources reindex return at once with a resource in queued. Lookio reads it in the background. Poll lookio resources get until status is ready or failed. Both are final.

Global flags

You can write these before or after the subcommand.

FlagEffect
--output json|table|ndjsonThe output format. JSON when stdout is not a terminal, a table in a terminal.
--jsonShort for --output json.
--profile <name>Which stored credential to use.
--no-retryDo not retry on 429 or 5xx.
--timeout <seconds>Give up on one request after this long. Default 60.

Where to go next

  • Authentication: browser, device and API key sign-in, profiles and where credentials are stored.
  • Commands: every command.
  • Automation: JSON output, polling, retries and CI.
  • Exit codes, including 7 for out of credits.

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.