# Daytona Ephemeral Sandbox Provisioner

> Daytona Ephemeral Sandbox Provisioner is a paid API for AI agents from daytona.withzero.ai, paid per call via MPP, $0.05/call, status unknown (last checked 2026-09-15, last successful call 2026-08-05).

Provisions a short-lived Daytona development sandbox (1 CPU, 1 GB RAM) for 30 minutes, returning a sandbox ID for subsequent port-preview URL retrieval.

## Facts

- Endpoint: POST https://daytona.withzero.ai/v1/x402/sandboxes
- Price: $0.05/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-15
- Last successful call: 2026-08-05
- Success rate: 100% of calls made through Zero
- Rating: 3.3 / 5 from 1 review
- Activations on Zero: 2
- Provider: daytona.withzero.ai
- Website: https://daytona.withzero.ai
- Canonical page: https://www.zero.xyz/c/daytona-withzero-ai-sandboxes-886514bd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pWrda94YlHFU3U-HgmMiR

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability daytona-withzero-ai-sandboxes-886514bd -d '<json body>'
```

Example prompt: Spin up an ephemeral Daytona sandbox for me — 1 CPU and 1 GB RAM for the next 30 minutes — so I can run some code and preview it on a port.

## When to prefer this

Use this endpoint when you need a fresh, isolated development environment on demand without managing persistent infrastructure. Ideal for CI/CD pipelines, code execution sandboxes, short-lived demos, or any scenario requiring a clean 30-minute compute instance paid via x402 on Base. Prefer over persistent VM provisioning when you want zero cleanup overhead and cost-per-use billing at $0.05 USDC.

## Known failure modes

- Payment failure (insufficient USDC balance) — sandbox not created, payment error returned
- Resource exhaustion on provider — sandbox provisioning fails with a 503 or similar
- Invalid request body — 400 error if required fields are missing or malformed
- Sandbox quota exceeded for wallet — provisioning rejected
- Network timeout during provisioning — indeterminate state, may require status check

## How this service works

Provision an ephemeral Daytona sandbox (1 CPU, 1 GB RAM) for 30 minutes. Returns the sandbox id; fetch a port-preview URL on demand.

## Output

Returns a JSON object containing a sandbox ID for the newly provisioned Daytona environment. The sandbox ID can then be used with companion endpoints to fetch a port-preview URL, check sandbox status, or delete the sandbox before the 30-minute TTL expires.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {},
 "description": "No body parameters required. The endpoint provisions a fixed-spec sandbox (1 CPU, 1 GB RAM, 30 minutes) with no configuration needed.",
 "additionalProperties": false
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/daytona-withzero-ai-sandboxes-886514bd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from daytona.withzero.ai](https://www.zero.xyz/host/daytona.withzero.ai/llms.txt)