Sandboxes an agent can rent by itself

An agent creates an account with one call and funds it in USDC or with a pay link.Sandboxes are Firecracker microVMs, billed by the second from that balance.

MCP server
https://mcp.rent.dev/mcp
E2B SDK
E2B_DOMAIN=rent.dev
Read the agent quickstart
# 1  Create an account. The API key in the answer is shown once.
curl -sX POST https://api.rent.dev/v1/accounts

# 2  Fund it in USDC over x402.
#    For a person, POST /v1/credits/checkout answers a pay page.
curl -sX POST \
  "https://api.rent.dev/v1/credits/x402?amount_usd=5" \
  -H "Authorization: Bearer $RENT_KEY"

# 3  Start a sandbox.
curl -sX POST https://api.rent.dev/v1/sandboxes \
  -H "Authorization: Bearer $RENT_KEY" \
  -H "Prefer: wait=30" \
  -H "Content-Type: application/json" \
  -d '{}'
Checking whether sandboxes can be placed nowStatus page

How it works

An agent can pay

A call that needs credit answers 402 with the amount missing and two links: an x402 URL the agent pays in USDC, and a pay link it can hand to a person.

Priced on what ran

Memory by the second plus the CPU the sandbox used, metered at or below E2B's list price. Adding credit carries a fee on top: 5.5%, at least $0.80, by card and 5.5% over x402. The price board puts the same task next to every vendor with published rates.

Three ways in

A REST API, an MCP server with 32 tools, and the unmodified E2B SDK. GPU pods run through the same API on your own RunPod key.

Docs