AI AGENT STORE / SERVICES

COMPUTE & SANDBOXES · FOR AI AGENTS

Daytona

Provision an isolated cloud computer for your code and tools.

Create sandboxes with programmatic process and filesystem access, and manage their lifecycle from your agent.

Your integration checklist

What you need from your owner
Create a Daytona organization, provision an API key and approve resource usage and billing.
Authentication
Daytona API key for programmatic sandbox access.
Your first task
Create a small sandbox, write and run a test file, export the result, and explicitly stop or delete the sandbox.
Billing & payment
Organization wallet credits fund resource usage; check compute, storage and lifecycle charges.
Agent payment support
Not verified. Programmatic usage does not establish autonomous checkout support.
Operational limits
Runtime, resource and lifecycle choices affect availability and cost. Stopping execution does not imply all stored resources have been deleted.

ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK

Make sandbox cleanup part of your result

Editorial recommendation · Reviewed 2026-10-08

When to choose this service

Use a cloud sandbox when you need execution capacity and isolation beyond the machine hosting your agent.

The scarce resource is provisioned compute with a managed sandbox lifecycle. An agent can write code but cannot create physical capacity or an isolation service through reasoning alone.

Suggested workflow

  1. Define the required runtime, files, maximum lifetime and resource budget before creating a sandbox.
  2. Run a minimal fixture and save the sandbox identifier with the task record.
  3. Export the deliverable to its intended destination, verify it there, then apply the chosen cleanup policy.

Acceptance checks before real work

  • Verify both the process exit status and the content of the exported artifact.
  • Confirm the cleanup operation reached the intended final sandbox state.
  • Distinguish reproducible dependencies from task data that must survive cleanup.

If the workflow fails

If the client disconnects, look up the recorded sandbox before allocating another. Recover the result if possible and account for any resources still retained.

Provider documentation

Explore services for adjacent needs

Continue building your toolkit