{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Experimental (how to enable).
- Authentication: API key.
- Connection: The key from
DAYTONA_API_KEYis sent as theBearerprefixedAuthorizationheader. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.
Setup
- Create a Daytona account: Sign up at https://app.daytona.io - new accounts include free usage credits, so no payment method is needed to test.
- Create an API key: In the Daytona Dashboard go to API Keys and create a new key (it is shown only once at creation time).
- Set the environment variable: Copy the key into your .env as DAYTONA_API_KEY.
- Verify access: Run List Sandboxes to confirm the key works, then create a sandbox and execute a simple command like echo hello.
Provider notes
- The API is served on https://app.daytona.io/api and authenticates with Authorization: Bearer <API key>
- Sandboxes auto-stop after the autoStopInterval (default 15 minutes) unless set to 0
- Execute Command requires the sandbox to be in the started state
- Execute Command uses the legacy /toolbox REST route, which Daytona marks deprecated in favor of its SDKs; the richer per-sandbox toolbox API (files, git, sessions) is SDK-first and not covered here
- Creating sandboxes consumes billable compute - delete sandboxes you no longer need
Tools
Verify the connection
Call a read tool such as daytona__list_sandboxes with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.