Ito Compute
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately installed canonical CLI. Use when a user asks to find H100/H200 capacity, request a fixed compute rate, check Itô compute status, validate GPU nodes, revoke Itô access, or rent or purchase GPU compute and needs the supported boundary explained.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Ito Compute when an AI agent needs a reusable SKILL.md workflow for this job: Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately installed canonical CLI. Use when a user asks to find H100/H200 capacity, request a fixed compute rate, check Itô compute status, validate GPU nodes, revoke Itô access, or rent or purchase GPU compute and needs the supported boundary explained.
When not to use it
Skip Ito Compute when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/ito-compute # Save SKILL.md to ~/.claude/skills/ito-compute/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ito-compute/SKILL.md. For a shared project, commit the folder at .claude/skills/ito-compute/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Ito Compute skill for this task: Use Ito Compute when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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:
```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.
## 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). 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. When a quote is ready and the buyer explicitly approves, accept it:
```sh 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. 7. 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`.
```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.
## MCP workflow
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_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.
Intended uses
- Use Ito Compute when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.