Sign in from a terminal, land in an interactive CLI, mint an account management key (slt_mgmt_…) for automation, create an inference API key (slt_…) for OpenAI-compatible SDKs, check credits, and manage a provider fleet. Optional MCP mode for AI coding agents.
Product: scalattice.com/cli · npm: scalattice-cli · Cloud docs: developers#cli · providers#fleet-api · Installer: scalattice.cloud/install/cli
# Paste-friendly
curl -fsSL https://scalattice.cloud/install/cli | sh
# Or with npm (Node 18+)
npm install -g scalattice-cliOr sign in on Cloud /auth and run the curl command shown there. That stores a session in ~/.config/scalattice/config.json, signs the browser tab in, installs this CLI if needed, and opens the prompt.
scalatticeYou get a scalattice> prompt. Type commands without the scalattice prefix:
scalattice> whoami
scalattice> login
scalattice> credits
scalattice> help
scalattice> exit
login stores a session only. For the OpenAI SDK, create a key and export it:
scalattice developers keys create
eval "$(scalattice init)" # after OPENAI_API_KEY is in the envOne-shot from any shell still works: scalattice login, scalattice whoami, and the rest.
Then use any OpenAI SDK:
from openai import OpenAI
client = OpenAI() # uses OPENAI_BASE_URL + OPENAI_API_KEY
print(client.models.list())| Prefix | Role |
|---|---|
slt_mgmt_… |
Account management: credits, inference-key CRUD, fleet |
slt_… |
Inference only (chat/completions via api.*) |
slt_provider_… |
Machine agent token (provider machines create / roll; goes on the GPU host) |
Create management keys on Account or account keys create if you need a long-lived secret for MCP. The CLI itself uses your session.
Inside the prompt, drop the scalattice prefix. From a normal terminal, keep it.
| Command | What it does |
|---|---|
scalattice |
Interactive prompt (login, whoami, …) |
login / logout |
Session only (what config.json stores) |
| `developers keys list | create |
| `account keys list | create |
init |
Print OpenAI env exports (needs OPENAI_API_KEY in the env) |
credits |
Wallet + model grants |
whoami |
Show session / account |
provider machines |
List fleet (id, status, token last four) |
provider machines create |
Add a machine (prints slt_provider_… once) |
provider machines roll |
New token for an existing machine (prints once) |
provider machines revoke |
Remove a never-connected machine |
provider earnings |
Fleet earnings |
provider pause / resume |
Pause or resume all machines |
provider schedule |
Patch one machine’s schedule |
mcp |
MCP stdio server (run as scalattice mcp, not inside the prompt) |
developer/developers, provider/providers, machine/machines, and key/keys are aliases.
Config: ~/.config/scalattice/config.json (mode 0600) — session + email only. Keys are never written there.
Env overrides: SCALATTICE_CLOUD_URL, SCALATTICE_API_URL, SCALATTICE_API_KEY, SCALATTICE_MGMT_KEY, SCALATTICE_SESSION_TOKEN.
scalattice login
scalattice provider machines create
scalattice provider machines
scalattice provider pause # or resumeSee Fleet API docs.
MCP is not a second install. After login, leave the prompt and run scalattice mcp. For a headless agent without a session, set SCALATTICE_MGMT_KEY in that environment.
{
"mcpServers": {
"scalattice": {
"command": "scalattice",
"args": ["mcp"]
}
}
}MIT
