froog

Integrations

Use froog sandboxes as the code-execution tool for an agent framework: the model writes code, and it runs on a Linux VM of its own instead of on your server. Each guide is a complete example you can run.

Agent frameworks

The pattern

Every guide does the same four things with froog's single-file Python or TypeScript SDK (curl -fsSLO https://froog.tech/sdk/froog.py or froog.ts) and a FROOG_API_KEY:

  1. Open the conversation's sandbox: create it with POST /v1/sandboxes (or start it if it was stopped) and wait until it's running.
  2. Define three tools in the framework's own syntax, bound to that sandbox: run a command (POST /v1/sandboxes/{name}/exec), write a file (PUT /v1/sandboxes/{name}/files/content) and read a file (GET on the same path).
  3. Run the agent with those tools.
  4. Clean up: stop the sandbox (its disk is kept 14 days) or delete it. Its auto-stop timer (ttl_secs, an hour after each start by default) stops it on its own.

Any other framework

CrewAI, LlamaIndex, Pydantic AI, Google's ADK or your own loop: if it can call a function as a tool, the same three calls work. The HTTP API is plain JSON with a Bearer key:

POST https://api.froog.tech/v1/sandboxes/chat-42/exec
Authorization: Bearer $FROOG_API_KEY

{"command": "python3 primes.py", "timeout_secs": 300}

→ {"exit_code": 0, "stdout": "2 3 5 7 11 …", "stderr": "", "timed_out": false, "command_id": "…"}

Every endpoint is in the HTTP API reference and openapi.json. For a coding agent on your own computer (Claude Code, Codex, Cursor) that should start sandboxes itself, see Use froog from your coding agent.

Questions

Why run agent tools in a froog sandbox?

Code a model writes can do anything the machine allows. A froog sandbox is a separate KVM virtual machine with its own kernel and disk, sudo, Docker and internet, so the agent can install and run what it needs without touching your server, and its files survive between turns.

What does it cost?

Running time is billed per second while a sandbox runs: $0.0137 an hour for small (2 vCPU, 4 GB), $0.0274 for default (4 vCPU, 8 GB). A stopped sandbox costs no running time and keeps its disk for 14 days.

7 days free: 25 hours of running time, 2 sandboxes at once. Then from $0.0137 an hour, billed per second.