↗ toolspin by InstaVM

THE TOOLSPIN API

Your agent.
A whole toolbox.

Find a tool, pass your inputs, get the result. Run catalog tools from a coding agent or script, using your existing InstaVM account.

ONE REQUEST TO START

Bring your key.
Pick your tool.

Use an InstaVM API key in your agent’s environment as INSTAVM_API_KEY. No browser login is needed.

This example benchmarks a command and returns timing.json. Use a new idempotency key for each intended run; keep the same key when retrying.

POST /api/v1/runs
curl https://toolspin.132-196-89-85.sslip.io/api/v1/runs \
  -H "Authorization: Bearer $INSTAVM_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: benchmark-001" \
  -d '{
    "tool": "sharkdp/hyperfine",
    "args": ["--runs", "1", "--export-json",
             "timing.json", "printf hello"],
    "outputs": ["timing.json"]
  }'

From discovery to result

  1. 01

    Find a tool

    GET /api/v1/tools?q=hyperfine searches the live catalog. Use the returned tool ID in your request.

  2. 02

    Start a run

    POST /api/v1/runs accepts arguments, stdin, input files, and environment variables. It returns 202 with a poll_url.

  3. 03

    Collect the result

    GET the poll_url with your key every two seconds. When completed, read result.stdout, stderr, exit_code, and base64 output files.

A completed run can have a nonzero exit code. Check failed and interrupted states too. Keep polling if billing.cleanup is pending.

YOUR EXISTING ACCOUNT

Same InstaVM billing.

Your API key selects the account that owns the VM and pays for its compute. Existing credits, plan limits, and usage billing apply. Toolspin adds no separate API charge.

Setup time and failed tool runs can incur compute usage. We request VM deletion after every run and report whether cleanup was confirmed. Each VM has a maximum requested lifetime of ten minutes.

GET /api/v1/account returns your existing credit balance, subscription, and VM usage. The UI’s free demo allowance is separate.

Built for bounded tool calls

Execution1–120 seconds per command; default 30 seconds. Setup happens first.
InputsArguments, 128 KiB of stdin, and up to 16 files totaling 512 KiB.
Outputs256 KiB each for stdout and stderr, plus 512 KiB of output files.
ConcurrencyTwo active API runs per account, subject to available capacity.
RetentionResults and retry records remain available for 24 hours. API keys are not saved.

Use command-line modes that can finish without keyboard interaction. For interactive TUIs, use the browser terminal. Uploaded files start in a fresh working directory.