# Compute Connector

> More compute for your bot. When the machine your agent runs on is low on memory, Compute Connector warns it and sends the heavy job (builds, installs, test suites, headless browsers) to a cloud sandbox on your own provider account: Vercel Sandbox by default, or E2B, Daytona, Modal and Workers Sandbox. You bring the keys and pay the provider directly; we charge a flat connector fee and never resell compute.

## Connect
- MCP (streamable HTTP): https://compute.cloudforbots.com/mcp
- Claude Code: `claude mcp add --transport http compute-connector https://compute.cloudforbots.com/mcp`
- REST: `POST https://compute.cloudforbots.com/api/run/<tool>` with JSON args. OpenAPI: https://compute.cloudforbots.com/openapi.json
- Auth: optional `Authorization: Bearer <key>`. Free key: `POST https://compute.cloudforbots.com/api/key`

## Pricing
- Free: 500 calls/day (daily, not a trial). No signup.
- Pro: $9/month, 50000 calls/day: https://pay.instaloops.com/b/eVqdR91Tid799P94Kr83C3F
- Bring your own model. Works with Claude, Codex, ChatGPT, Grok Bot.

## Tools
### check_memory
Before a heavy job, send how much memory the machine your agent runs on has free (free -m, os.freemem()) and what you are about to run. Get a memory warning and a verdict: run_local, or offload with the provider to use. Free watch-only logs would_offload for the weekly report; nothing runs.
Inputs: `free_mb` (number, required), `total_mb` (number), `job` (string), `job_mb` (number), `floor_mb` (number), `host` (string)

### run_job
Pro: run a shell command in a fresh cloud sandbox on your own provider account (vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox)) and get the exit code and the last 16 KB of stdout and stderr back. Send small input files with it. The sandbox is created for the job and stopped right after, so nothing idles on your bill. Free watch-only logs would_offload and runs nothing.
Inputs: `cmd` (string, required), `provider` (string), `files` (array), `env` (object), `timeout_s` (integer), `runtime` (string), `template` (string), `free_mb` (number)

### save_provider_key
Pro, owner only: save one provider key, sealed with AES-256-GCM before it reaches the database. Providers: vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox). Vercel needs team_id and project_id; Modal and Workers Sandbox need bridge_url (see provider_setup). The key is checked with a read-only call first and is never returned or logged. Free stores nothing.
Inputs: `provider` (string, required), `token` (string, required), `name` (string), `team_id` (string), `project_id` (string), `api_url` (string), `bridge_url` (string), `make_default` (boolean), `skip_check` (boolean)

### list_providers
Every provider this connects to, how each one runs, and (with your key) the provider keys you saved: name, provider, fingerprint, default, last used. Never shows a key.
Inputs: none

### delete_provider_key
Pro, owner only: delete a saved provider key by name. Jobs on that key stop working at once.
Inputs: `name` (string, required)

### provider_setup
Step-by-step setup for one provider: where to get the key, what to pass to save_provider_key, links to its docs and price page, and for Modal or Workers Sandbox the bridge code to deploy on your own account.
Inputs: `provider` (string, required)

### weekly_report
Plain-English summary of the last 7 days: memory checks, low-memory warnings, jobs that would have been offloaded (free) or ran (Pro) by provider, minutes and failures. Read-only; sends nothing. Needs an API key.
Inputs: none

### usage_and_upgrade
Usage today + upgrade link (not metered).

## FAQ
### What problem does this solve?
Agents run heavy jobs (builds, installs, test suites, headless browsers) on whatever machine they live on. When that machine is low on memory, the job freezes it or gets killed. Compute Connector tells your agent before it happens and moves the job to a cloud sandbox on your own account.

### Do you sell compute?
No. You bring your own provider key and the provider bills you directly at its own price. We charge a flat $9/month connector fee and never mark up or resell compute (provider terms don't allow resale anyway).

### Which providers work?
Vercel Sandbox (the default), E2B and Daytona through their public APIs. Modal and Workers Sandbox through a small bridge you deploy on your own account; provider_setup gives you the code.

### How are my provider keys stored?
Sealed with AES-256-GCM before they reach the database, bound to your account and the key name. No tool ever returns a key, and keys, commands, environment values and output are never written to our logs.

### What do you keep about my jobs?
Only the first word of the command (like npm), the provider, how long it ran, the exit code and memory numbers, for your weekly report. Never the full command, files, env or output. 90-day retention.

### Will a sandbox keep billing me after the job?
No. Each run_job creates a fresh sandbox, runs your command and stops it right away. If your agent also opens its own long-lived sandboxes, Sandbox Timer flags the idle ones.

### What is watch-only mode?
The free plan warns when memory is low and logs every job that would have been offloaded, with a weekly report. Nothing runs and no key is stored. It is not a trial.

### How big can a job be?
Up to 240 seconds per run_job call, 50 input files and 500 KB sent with the job, and the last 16 KB of stdout and stderr back. Bigger inputs: clone or download them inside the job.

### Can it run on my own servers?
Not yet. Today it connects to the providers above. Bring your own key is the whole idea.

### What does it cost?
Free: watch-only, 500 calls a day. Pro is $9 a month, or $90 for a year, plus whatever your provider charges you. It is also included in the Cloud for Bots All Access bundle.

Publisher: Supa Humans (https://supahumans.ai). Marketplace: https://botrecipe.com/tools/