ito-compute

Itô Compute

Use the canonical Itô compute CLI or MCP server. ECC does not implement a parallel client, local simulation, reservation, workload runner, or inference server. ECC itself does no browser automation.

Install the canonical local package

ito-compute-cli is currently unpublished. Build it from its canonical repository instead of using npx, npm exec, or an unverified package:

git clone https://github.com/Ito-Markets/ito-cloud-runtime.git
cd ito-cloud-runtime/cli/ito-compute-cli
npm ci
npm run check

Set ECC_ITO_CLI_EXECUTABLE to the explicit absolute built entry:

/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito.js

ECC never discovers this credential-bearing client through PATH. ecc ito login performs device authorization and never inherits ITO_API_KEY. The validation-only auth, plus find and status, forward ITO_API_KEY directly when configured; ITO_AUTH_MODE=legacy is not required. Never put a key or token in arguments, tracked files, MCP results, logs, or chat.

CLI workflow

1. Run ecc ito login before the first operation. ECC delegates this to the

canonical CLI's device authorization, which opens the Itô verification page by default and persists a device token in macOS Keychain. Use ecc ito login --no-browser to suppress the page handoff. ECC itself does no browser automation. If the originating agent cannot complete the signed-in browser step, hand the exact command to the user; after approval finishes, return to the originating task and continue with ecc ito auth. Device tokens use macOS Keychain by default. File-token fallback is explicit and its directory and token file must remain owner-only (0700 and 0600).

1. Run ecc ito auth to validate existing credentials; it never starts login

and rejects --no-browser.

1. Before ecc ito find, obtain explicit buyer authority to submit an RFQ.

• Require gpu, count, whole days, max-rate, nodes,

gpus-per-node, storage-tb, start-window, form-factor, contract-type, fabric, region, and the split-fill decision.

• Require count == nodes * gpus-per-node; never derive topology.
• Use any only when the buyer explicitly accepts any fabric or region.
• Omitted --allow-split means false.

1. Run the live RFQ command:

   ecc ito find \
     --gpu h200 \
     --count 8 \
     --nodes 1 \
     --gpus-per-node 8 \
     --days 30 \
     --storage-tb 1 \
     --start-window 2099-08-15 \
     --max-rate 3.00 \
     --form-factor bare_metal \
     --contract-type reservation \
     --fabric infiniband \
     --region us-east-1

1. Run ecc ito status to inspect RFQs and procurement orders.

After an ambiguous transport failure, check status before repeating find.

1. When a quote is ready and the buyer explicitly approves, accept it:

   ecc ito accept rfq_<ticket-id>

This routes the ticket to the desk for human review. It does not move funds or reserve capacity. Do not accept without explicit buyer authority.

1. Run ecc ito logout when the user explicitly asks to revoke this device.

The canonical CLI keeps the local credential when remote revocation fails so the operator can retry; never delete the token manually as a substitute.

Inventory prices are indicative. An RFQ is not reserved capacity. Treat a rate as fixed only when the canonical result contains a non-null firm quote.

Live node qualification

ecc ito evals exposes the canonical CLI's narrow live adapter to a separately installed sixtytwo-cli==0.3.33. It does not expose local fixture execution through ECC. Require all of the following before invoking it:

• operator authorization to contact the named nodes;
• ITO_ENABLE_SIXTYTWO_LIVE=1;
• --live-sixtytwo;
• an explicit node list; and
• an existing absolute config directory containing sixtytwo.yaml.

ecc ito evals \
  --cluster clu_prod_example \
  --live-sixtytwo \
  --nodes gpu-01,gpu-02 \
  --config-dir /absolute/path/to/qualification-config

The canonical adapter can run only the pinned version check and sixtytwo test --full against the explicit nodes. It cannot rent, launch, recover, repair, reset, purchase, or order resources. ECC does not forward ITO_API_KEY or model/cloud credentials into node qualification.

MCP workflow

Build the canonical package, then configure the stdio server with an absolute path:

{
  "mcpServers": {
    "ito-compute": {
      "command": "node",
      "args": [
        "/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito-mcp.js"
      ]
    }
  }
}

The server exposes only:

• ito_auth
• ito_find
• ito_status
• ito_accept

ito_auth validates existing credentials; it does not start device login. Use ito_auth, gather explicit buyer authority and every hard constraint, call ito_find, then poll with ito_status when needed. When a quote is ready and the buyer explicitly approves, call ito_accept with the ticket id. Desk quotes are usually indicative and nonbinding until the desk confirms; the result carries quote_class.

Rent or purchase semantics

find submits an RFQ and may return a firm quote, but it does not rent, purchase, reserve, provision, or move funds. accept routes a quote to the desk for human review; it does not move funds or reserve capacity. status is read-oriented, though the provider endpoint may reconcile an existing procurement order. The passive dashboard link in ECC help is a separate user-operated web route; do not open or operate it as a substitute for a missing CLI capability.

Unsupported operations

The supported client surface cannot lock quotes, reserve capacity, execute workloads, or serve inference. accept is a desk handoff, not a purchase. The MCP server does not expose qualification; use the explicit CLI command above. Do not invent additional tools or a purchase path. Do not substitute a browser or fixture when the local CLI is missing or a live operation fails. Report the missing capability and stop.