Lobstack documentation

Lobstack is a desktop app where agents do real work and ask before they change anything, and the API it runs on: 18 models from 4 providers behind one OpenAI-compatible endpoint.

The Lobstack app is free for Windows, macOS and Linux. Agents work in your files, repositories and connected tools. A step that only reads runs straight through; a step that changes something waits for your approval. The API, the Lobstack Gateway, is what the app runs on, and you can call it from your own code too.

The app in three steps

  1. Download it

    From lobstack.ai/download. It is a public beta, and the Windows and Mac builds are signed. The Mac app opens normally; Windows may ask once while the certificate builds reputation.

  2. Log In and pick an agent

    One sign-in through your browser, and the first one from the app adds $5 of credit for 30 days. A new workspace starts with three agents; make your own with New agent.

  3. Give it a job, and approve what changes something

    Searching and reading run. Writing a file, running a command or posting a document stops on a card that shows exactly what will happen, until you approve it. The whole walk-through is the app quickstart.

The app, the API and your account

Where to start

With the app

With the API

The API in one request

If you have used the OpenAI SDK, you already know the Gateway. Change the base URL and the key; everything else — the request shape, the response shape, streaming — stays as it is. What changes is what comes back with the answer: the model that served it, the tier it was scored into, and the price, on the response itself rather than in a dashboard you have to go and open. "auto" hands the choice to Nex, the router.

Your first requestbash
curl https://www.lobstack.ai/api/gateway/v1/chat/completions \
  -H "Authorization: Bearer $LOBSTACK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "auto",
    "messages": [{ "role": "user", "content": "Say hello." }]
  }'

The key comes from the Console; the API quickstart goes from a new account to this request and the headers it returns.

What we do not claim

Routing a simple request to a cheaper model is not a differentiator — OpenRouter, LiteLLM and Requesty all do it, and LiteLLM does it free and open source. We would rather you heard that here than found it out later.

What is unusual is the receipt, and specifically that it says what its own numbers mean. A dollar saving comes back with the model it was measured against and baseline_reason saying why that model: named when you asked for it, plan_ceiling when you sent "auto" and the comparison is against the best model your plan allows. Those are different claims and the response never presents them as the same one. Where there is nothing honest to compare against, the field is null rather than a number. The rules are on Metering & cost, and you can run the router on your own prompt without spending a token on the routing playground.