Skip to main content
Tinker on Compute gives the official tinker SDK a dedicated training URL backed by one GPU. Your local script controls the training loop. Compute provisions the machine, meters it, and tears it down.
Tinker is in private alpha. The CLI and operator path are shipped, but public product quotes remain closed until the H100 and MI300X canaries pass. A normal public account currently receives sku_unavailable when it tries to create a session.

​
Why use it

Use fine-tuning when a capable base model still misses the behavior your application needs. Supervised fine-tuning teaches from prompt and ideal-response pairs. Reinforcement learning is useful when you can score an answer more easily than you can write the ideal one. The first Compute preset runs LoRA training on Qwen/Qwen3-4B-Instruct-2507. It supports cross-entropy for supervised work and importance sampling for RL-shaped loops.

​
Run a cookbook recipe

Install the current CLI, sign in, and add prepaid credit first:
Approved alpha accounts can run the upstream cookbook without exporting a second credential:
compute tinker run does five things:
  1. Quotes and provisions a Tinker session.
  2. Waits for its public training URL to become healthy.
  3. Injects TINKER_API_KEY, TINKER_BASE_URL, and TINKER_MODEL into the child process.
  4. Runs the command and forwards its exit status and terminal signals.
  5. Stops the CLI-owned session and waits for checkpoint harvest.
The SDK key is not printed or added to your outer shell.

​
Run your own script

Your script can build the official client from the injected environment:
Then run it through the same lifecycle:
tinker.ServiceClient() with no arguments also reads the two official environment variables. Do not hard-code the hosted Tinker URL; each Compute session has its own https://tinker-<id>.api.compute.cx base URL.

​
What you get

The training script receives the normal Tinker futures and results. When the session stops, Compute harvests saved weights to object storage. List the available files with:
Download a harvested checkpoint from the session page in the dashboard. The CLI currently lists checkpoints but does not download them.

CLI lifecycle

Choose between one-shot runs, interactive shells, and warm user-owned sessions.

SDK compatibility

Check the supported model and API boundaries, including the SDK environment and losses.