{/* 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
SPRITES_TOKENis sent as theBearerprefixedAuthorizationheader. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.
Setup
- Create a Sprites account: Sign up at https://sprites.dev by signing in with a Fly.io account (Sprites is made by Fly.io); new accounts can create sprites right away for testing.
- Generate an API token: Go to https://sprites.dev/account and generate an API token. Tokens have the format my-org/token-id/secret. (Alternatively, install the sprite CLI and run sprite org auth.)
- Set the environment variable: Copy the token into your .env as SPRITES_TOKEN.
- Verify access: Run List Sprites to confirm the token works, then create a sprite and execute a command in it.
Provider notes
- The API is served on https://api.sprites.dev/v1 and authenticates with Authorization: Bearer $SPRITES_TOKEN
- Sprites are stateful: the filesystem persists across suspends, and sprites wake automatically on use (status moves between cold, warm, and running)
- Destroying a sprite permanently deletes its persisted state
- Execute Command uses the HTTP POST exec endpoint for non-interactive commands; interactive TTY sessions, filesystem APIs, checkpoints, and services are WebSocket/SDK-first and not covered by these tools
Tools
Verify the connection
Call a read tool such as sprites__list_sprites with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.