ito-compute

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Itô 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.
使用标准Itô Compute CLI或MCP服务器。ECC不实现并行客户端、本地模拟、预留、工作负载运行器或推理服务器。ECC本身不执行任何浏览器自动化操作。

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:
sh
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:
text
/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.
ito-compute-cli
目前未发布。请从其标准仓库构建,不要使用
npx
npm exec
或未经验证的包:
sh
git clone https://github.com/Ito-Markets/ito-cloud-runtime.git
cd ito-cloud-runtime/cli/ito-compute-cli
npm ci
npm run check
ECC_ITO_CLI_EXECUTABLE
设置为构建后的绝对路径:
text
/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito.js
ECC不会通过
PATH
自动发现这个带有凭证的客户端。
ecc ito login
执行设备授权,且绝不会继承
ITO_API_KEY
。仅用于验证的
auth
命令,以及
find
status
命令,在配置后会直接传递
ITO_API_KEY
;无需设置
ITO_AUTH_MODE=legacy
。切勿在参数、跟踪文件、MCP结果、日志或聊天中放置密钥或令牌。

CLI workflow

CLI工作流

  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).
  2. Run
    ecc ito auth
    to validate existing credentials; it never starts login and rejects
    --no-browser
    .
  3. 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.
  4. Run the live RFQ command:
    sh
    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
  5. Run
    ecc ito status
    to inspect RFQs and procurement orders. After an ambiguous transport failure, check status before repeating
    find
    .
  6. 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.
  1. 在首次操作前运行
    ecc ito login
    。ECC会将此委托给标准CLI的设备授权,默认情况下会打开Itô验证页面,并在macOS钥匙串中持久化存储设备令牌。使用
    ecc ito login --no-browser
    可禁用页面跳转。ECC本身不执行任何浏览器自动化操作。如果发起操作的Agent无法完成浏览器登录步骤,请将确切命令交给用户;在完成授权后,返回原任务并继续执行
    ecc ito auth
    。 设备令牌默认使用macOS钥匙串。文件令牌作为备选方案,其所在目录和令牌文件必须仅对所有者开放(权限为0700和0600)。
  2. 运行
    ecc ito auth
    验证现有凭证;此命令不会启动登录流程,且不支持
    --no-browser
    参数。
  3. 在运行
    ecc ito find
    之前,需获得明确的买方授权以提交RFQ。
    • 必须指定
      gpu
      count
      、完整的
      days
      max-rate
      nodes
      gpus-per-node
      storage-tb
      start-window
      form-factor
      contract-type
      fabric
      region
      ,以及拆分填充决策。
    • 必须满足
      count == nodes * gpus-per-node
      ;切勿自行推导拓扑结构。
    • 仅当买方明确接受任意fabric或region时,才可使用
      any
    • 省略
      --allow-split
      参数表示false。
  4. 运行实时RFQ命令:
    sh
    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
  5. 运行
    ecc ito status
    查看RFQ和采购订单状态。在出现模糊的传输失败后,重复执行
    find
    前请先检查状态。
  6. 当用户明确要求撤销此设备权限时,运行
    ecc ito logout
    。如果远程撤销失败,标准CLI会保留本地凭证以便操作员重试;切勿手动删除令牌作为替代方案。
库存价格仅作参考。RFQ不代表预留算力。只有当标准结果包含非空的确定报价时,才可将费率视为固定。

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
    .
sh
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.
ecc ito evals
将标准CLI的窄幅实时适配器暴露给单独安装的
sixtytwo-cli==0.3.33
。它不会通过ECC暴露本地 fixture 执行。 在调用前必须满足以下所有条件:
  • 操作员有权联系指定节点;
  • 设置
    ITO_ENABLE_SIXTYTWO_LIVE=1
  • 指定
    --live-sixtytwo
    参数;
  • 明确的节点列表;
  • 包含
    sixtytwo.yaml
    的现有绝对配置目录。
sh
ecc ito evals \
  --cluster clu_prod_example \
  --live-sixtytwo \
  --nodes gpu-01,gpu-02 \
  --config-dir /absolute/path/to/qualification-config
标准适配器仅能对指定节点运行固定版本检查和
sixtytwo test --full
。它无法租用、启动、恢复、修复、重置、购买或订购资源。ECC不会将
ITO_API_KEY
或模型/云凭证传递到节点验证流程中。

MCP workflow

MCP工作流

Build the canonical package, then configure the stdio server with an absolute path:
json
{
  "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_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.
构建标准包,然后使用绝对路径配置标准输入输出服务器:
json
{
  "mcpServers": {
    "ito-compute": {
      "command": "node",
      "args": [
        "/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito-mcp.js"
      ]
    }
  }
}
服务器仅暴露以下接口:
  • ito_auth
  • ito_find
  • ito_status
ito_auth
验证现有凭证;它不会启动设备登录。使用
ito_auth
,收集明确的买方授权和所有硬约束,调用
ito_find
,然后在需要时通过
ito_status
轮询状态。

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.
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.
find
提交RFQ并可能返回确定报价,但它不会执行租用、购买、预留、配置或转账操作。
status
是只读导向的,不过提供商端点可能会协调现有采购订单。ECC帮助中的被动仪表板链接是一个独立的用户操作Web路由;请勿打开或操作它来替代缺失的CLI功能。

Unsupported operations

不支持的操作

The supported client surface cannot lock quotes, reserve capacity, execute workloads, or serve inference. 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.
支持的客户端功能无法锁定报价、预留算力、执行工作负载或提供推理服务。MCP服务器不暴露验证功能;请使用上述明确的CLI命令。请勿发明额外工具或购买路径。当本地CLI缺失或实时操作失败时,请勿用浏览器或fixture替代。请报告缺失的功能并停止操作。