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
# 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 '{}'# The E2B SDK, unmodified. Point it at rent.dev and use your rent.dev key.
export E2B_DOMAIN=rent.dev
export E2B_API_KEY=e2b_<the 64 hex characters of your rent.dev key>{
"mcpServers": {
"rent": {
"url": "https://mcp.rent.dev/mcp",
"headers": {
"Authorization": "Bearer rent_sk_…"
}
}
}
}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
- Agent quickstart
Create an account, fund it and run a sandbox over REST, with no person in the loop.
- MCP server
rent.dev's MCP server: two endpoints, their tools with scopes and hints, and how payments work inside a tool call.
- REST API
Every route of the rent.dev API with its parameters, body fields and status codes, generated from the OpenAPI document.
- E2B compatibility
Run the unmodified E2B SDK against rent.dev: setup, the compatibility matrix and the known gaps.
- Payments
How a rent.dev balance is funded: Checkout and pay links, auto-recharge, x402 USDC, wallet-first signup and the fees.
- Bring your own key
What runs on rent.dev's balance and what needs your own vendor key: GPU pods, and sandboxes at E2B Cloud or Vercel.
- Pricing
How a rent.dev sandbox is priced: provisioned memory plus active CPU, metered at no more than E2B's list price, a top-up fee of 5.5% (at least $0.80) by card or 5.5% over x402, and worked examples.
- Limits
The limits that apply to rent.dev sandboxes and GPU pods today: the current node's cap on running sandboxes and the vendor limits passed through.
- Errors
Every Problem code the rent.dev API answers, its HTTP status and what to do about it.