Lookio Docs
Lookio websiteOpen Lookio
APIRate limits

Rate limits

The request limits of the Lookio API per credential and per address, the headers that report them and how to back off when you reach one.

Lookio limits requests to protect the service. The limits apply to the REST API and to the MCP server alike.

Limits

LimitValueApplies to
Sustained240 requests per minuteEach credential
Burst40 requests per 10 secondsEach credential
Address ceiling1,200 requests per minuteEach IP address, across all credentials
Failed authentication30 failures per minuteEach IP address

The credential limits shape normal use. The address ceiling exists so that unauthenticated traffic cannot overload the service, and it is far above the credential limit so that several credentials behind one network address never reach it. The failed-authentication limit stops key guessing, and a client with a working credential never touches it.

Two workspaces never share a budget.

When you hit a limit

The API answers 429 with the rate_limited code and a Retry-After header in seconds: 10 after the burst limit, 60 after the others.

HTTP
HTTP/1.1 429 Too Many Requests
Retry-After: 10

Wait for Retry-After, then retry. Add random jitter if many workers share a credential, so they do not retry together. The CLI does this for you.

Headers

Every JSON response carries the policy:

HTTP
RateLimit-Policy: 240;w=60, 40;w=10

It lists the limits and their windows in seconds. Lookio does not report a remaining count: its limiter cannot compute one, and a number it could not stand behind would mislead your throttle. Count your own requests against the policy.

Notes

  • Counters are kept per Cloudflare location and are approximate. A client spread across continents can exceed the nominal rate somewhat. The limiter is not an accounting system: credit spending is enforced separately, by the balance, so a burst cannot overspend your credits.
  • In Code Mode, each request() made inside a script counts against the credential’s limit, and a script can make at most 100 of them.
  • Registering an OAuth client is limited to 5 per minute per address.
  • Importing is not throttled by credits, but by these limits and by your plan’s word allowance.

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.