mlx-optiq

Accounts and billing

How you sign in, how a machine gets a key, and what the dashboard does with it. For what Boost is and how to use it, see OptiQ Cloud overview.

Signing in

Sign-in is Google only, and asks for nothing beyond your name and email address. That is deliberate: any sensitive or restricted scope would drag the project into Google's manual data-access review, and OptiQ Cloud has no use for your Drive or your mail.

The consent screen is company-level and verified, so you see an ordinary Google sign-in rather than an unverified-app warning.

What we store Your email address, a dollar balance, what each call cost, and one row per machine you connect. No prompts, no code, no repository contents.

The dashboard

The top of the OptiQ Cloud dashboard: the dollar balance with a form to add credit in any amount, and what this month has cost.
cloud.mlx-optiq.com after signing in.

Your balance and a button to buy more, what you spent this month task by task, the models and their prices, your API keys with their limits, and auto top-up.

Connecting a machine

A terminal cannot receive a browser redirect, so OptiQ uses the device-code flow. Run this on the machine that runs optiq serve:

$ optiq cloud login

  Your code:  EH4Y-67C6
  Approve at: https://cloud.mlx-optiq.com/link

Waiting for approval...
Connected. Token saved to ~/.optiq/config.yaml
Signed in as you@example.com - balance $2.00.
Next: `optiq run claude --cloud glm-5.3-flash` runs Claude Code on an OptiQ Cloud model (also codex, opencode, vibe, hermes, openclaw); /boost in `optiq code` has the cloud lead a task with your local model as its helper. `optiq cloud models` lists the models and prices.

Open that URL, check the code matches what your terminal printed, and approve. The check is the point: approving is what grants a machine the right to spend your balance, so a page that granted one merely by being opened would turn a forwarded link into an attack.

How the key reaches your coding agent

optiq cloud login writes the key into your OptiQ config, on your machine. Only optiq serve reads it: when a client picks one of the cloud models (optiq-cloud/<id>), optiq serve sends the request to OptiQ Cloud with it. OptiQ Code with Boost, the Lab, Claude Code, Codex, OpenCode and the rest talk to optiq serve with whatever local key they already use, and never see the cloud key.

So a compromised agent config leaks a local key, not a cloud credential, and pointing a new agent at OptiQ needs no secret at all. To call the API from another machine or a server, create a separate key on the dashboard instead.

Where the token lives ~/.optiq/config.yaml, written 0600. It is never placed in a repository file, and never sent to a model.

Keys

optiq cloud login makes one key per machine, and you can create more on the dashboard, for example one per agent or per server. Only a hash is stored, so a key is shown once, when it is made, and never again.

A new key shown once on the dashboard, with a Copy button, above the list of keys.
A new key is shown once. Copy it before leaving the page.

Each key has its own limits: $100 a month of spending, 60 requests a minute and 10 calls at once unless you change them, plus the models it may call and an optional expiry. Edit changes them and Revoke stops the key at once. See Keys and limits for what happens at each one.

CommandWhat it does
optiq cloud statusAccount and balance.
optiq cloud logoutRevokes the token, then forgets it locally.
optiq cloud logout --keep-remoteForgets it locally only.

Logout revokes by default because forgetting a working credential is not logging out: a laptop lost afterwards could still spend your balance.

Auto top-up

Off unless you turn it on. When on, it adds the amount you choose (from $10) once your balance falls below a threshold you set, and it adds at most $1,000 in a month unless you change that limit. Leave the limit blank for none.

The cap is the part that matters. Automatic spending without one is how a runaway loop becomes a surprising invoice, so the cap is checked in the same statement that claims the top-up, and several calls arriving at once cannot each start their own purchase.

What you are charged for

  • The tokens each call used, at that model's per-token price, rounded up to the millionth of a dollar per call.
  • A call that failed before the model answered is not charged.
  • Nothing else: no subscription, no per-task fee, no charge for tasks on your local model.
  • Credit is bought $20 at a time and lasts 12 months from purchase. The $2 of credit at sign-up lasts 14 days.
  • Boosts left over from before per-token billing were converted at $0.10 each.

The dashboard lists every recent task with its tokens and cost, so you can check any charge against the price.