--- title: "The Sprites ecosystem — set up your coding agent" description: "Wire Sprites into Claude Code, Codex, Cursor, Antigravity, Grok, Cortex, DeepSeek, Pi, Hermes Agent, VS Code, or any MCP client. Pick your agent and follow the steps." --- # Works with your agent. Yes, that one too. Official Sprites plugins for every serious coding agent — plus SDKs, API connectors, and native integrations. Your agent builds, tests, and runs services on a real Linux box instead of your laptop. Point any agent at `https://sprites.dev/mcp` ``` https://sprites.dev/mcp ``` OAuth in the browser. Nothing to install, nothing to run locally. ## Which agent are you using? Pick one and follow the steps below. / No integration matches that — but any MCP client can use the generic path above. ### Set up Sprites for Claude Code [superfly/sprites-claude-plugin](https://github.com/superfly/sprites-claude-plugin) 1. 1 Add the marketplace and install the plugin `/plugin marketplace add superfly/sprites-claude-plugin` ``` /plugin marketplace add superfly/sprites-claude-plugin ``` 2. 2 Install it `/plugin install sprites@sprites` ``` /plugin install sprites@sprites ``` 3. 3 Reload so Claude picks up the new tools `/reload-plugins` ``` /reload-plugins ``` 4. 4 Authorize the connector `/mcp` ``` /mcp ``` Pick the plugin-provided sprites server and complete browser OAuth for the Fly.io org you want. Restricted access with a name prefix such as mcp- is the safer default. 5. ✓ Check the integration `/sprites:status` ``` /sprites:status ``` An empty Sprite list means you're authenticated and working. /sprites:smoke runs the full list → create → exec → cleanup pass. Prefer the bare MCP server, without the plugin's skills and hooks? `claude mcp add --transport http sprites https://sprites.dev/mcp` ``` claude mcp add --transport http sprites https://sprites.dev/mcp ``` ### Set up Sprites for Codex [superfly/sprites-codex-plugin](https://github.com/superfly/sprites-codex-plugin) 1. 1 Install the Sprites plugin from the Codex plugin marketplace Codex distributes this one through its own marketplace UI, so there's no install one-liner to copy. 2. 2 Or add this repository as a marketplace from a local checkout `codex plugin marketplace add .` ``` codex plugin marketplace add . ``` Then restart Codex, open the plugin directory, choose the Sprites marketplace, and install Sprites. 3. 3 Authenticate when Codex prompts you The plugin talks to the hosted MCP server at https://sprites.dev/mcp. 4. ✓ Ask Codex to prove it's connected `List my sprites.` ``` List my sprites. ``` An empty list is a successful, authenticated response. ### Set up Sprites for Cursor [superfly/sprites-cursor-plugin](https://github.com/superfly/sprites-cursor-plugin) 1. 1 Install the Sprites plugin from the Cursor Marketplace Cursor prompts you to authorize with Sprites over OAuth on first use. 2. 2 Or wire up the MCP server by hand ~/.cursor/mcp.json ``` { "mcpServers": { "sprites": { "url": "https://sprites.dev/mcp" } } } ``` ``` { "mcpServers": { "sprites": { "url": "https://sprites.dev/mcp" } } } ``` Drop this in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one. 3. ✓ Ask the agent to prove it's connected `List my sprites.` ``` List my sprites. ``` ### Set up Sprites for Antigravity [superfly/sprites-antigravity-plugin](https://github.com/superfly/sprites-antigravity-plugin) 1. 1 Install straight from the repository `agy plugin install https://github.com/superfly/sprites-antigravity-plugin` ``` agy plugin install https://github.com/superfly/sprites-antigravity-plugin ``` 2. 2 Authenticate the sprites server `/mcp` ``` /mcp ``` Use restricted access unless your workflow genuinely needs broader organization control. 3. ✓ List what you've got `/sprites:list` ``` /sprites:list ``` The plugin also ships /sprites:new, /sprites:run, /sprites:checkpoint, /sprites:service, and /sprites:cleanup. ### Set up Sprites for Grok Build [superfly/sprites-grok-plugin](https://github.com/superfly/sprites-grok-plugin) 1. 1 Install the plugin `grok plugin install superfly/sprites-grok-plugin --trust` ``` grok plugin install superfly/sprites-grok-plugin --trust ``` 2. 2 Enable it `grok plugin enable sprites` ``` grok plugin enable sprites ``` 3. 3 Reload plugins, or restart Grok `/plugins` ``` /plugins ``` Then press r to reload. 4. 4 Complete browser OAuth The consent screen defaults to the restricted mcp- name prefix. Full access allows bare names but grants unrestricted access to every sprite in the org. 5. ✓ Run the status check `/sprites-status` ``` /sprites-status ``` Empty list means you're authenticated. /sprites-smoke does the full list → create → exec → confirm-before-destroy pass, and grok mcp doctor sprites diagnoses a bad install. ### Set up Sprites for Cortex Code [superfly/sprites-cortex-plugin](https://github.com/superfly/sprites-cortex-plugin) 1. 1 Install from GitHub `cortex plugin install superfly/sprites-cortex-plugin` ``` cortex plugin install superfly/sprites-cortex-plugin ``` 2. 2 Enable the plugin `cortex plugin enable sprites` ``` cortex plugin enable sprites ``` 3. 3 Reload inside your session, or restart Cortex Code `/plugin reload` ``` /plugin reload ``` 4. 4 Authorize Sprites when requested `/mcp` ``` /mcp ``` Complete browser OAuth and select the intended Fly.io organization. No Sprites CLI or pasted API token is required. 5. ✓ Check the connection `/sprites-status` ``` /sprites-status ``` An empty Sprite list still means authentication succeeded. The plugin includes skills, commands, safety hooks, and a runner for long builds and tests. It does not copy Snowflake credentials or sessions into Sprites. ### Set up Sprites for DeepSeek Harness [superfly/sprites-deepseek-plugin](https://github.com/superfly/sprites-deepseek-plugin) 1. 1 Add the plugin to your profile `npx @deepseek-ai/dsh plugin --profile web add github:superfly/sprites-deepseek-plugin` ``` npx @deepseek-ai/dsh plugin --profile web add github:superfly/sprites-deepseek-plugin ``` Swap web for whichever profile you actually use. 2. 2 Start that profile `npx @deepseek-ai/dsh --profile web` ``` npx @deepseek-ai/dsh --profile web ``` 3. 3 Complete browser OAuth and pick your Fly.io organization Restart Harness once if the first tool sync timed out while you were authorizing. 4. ✓ Confirm the layer loaded `npx @deepseek-ai/dsh --profile web --dump-config` ``` npx @deepseek-ai/dsh --profile web --dump-config ``` Output should include the dsh-sprites-plugin layer, sprites-mcp, and sprites-skill-filesystem. ### Set up Sprites for OpenCode [superfly/sprites-opencode-plugin](https://github.com/superfly/sprites-opencode-plugin) 1. 1 Add the plugin to your OpenCode config opencode.json ``` { "$schema": "https://opencode.ai/config.json", "plugin": ["@flydotio/sprites-opencode-plugin"] } ``` ``` { "$schema": "https://opencode.ai/config.json", "plugin": ["@flydotio/sprites-opencode-plugin"] } ``` OpenCode 1.18.23 or newer. Plugins install automatically with Bun at startup, so restart OpenCode after saving. Until the package lands on npm, clone the repository and use an absolute file:///path/to/sprites-opencode-plugin entry instead. 2. 2 Complete browser OAuth `/sprites-status` ``` /sprites-status ``` The first Sprites request starts OpenCode's browser OAuth flow. Pick the Fly.io org you want. If no browser opens, run opencode mcp auth sprites and retry. 3. ✓ Ask OpenCode to prove it's connected `List my sprites.` ``` List my sprites. ``` An empty list is a successful, authenticated response. /sprites-smoke walks the full list → create → exec pass, and opencode mcp debug sprites diagnoses a bad connection. ### Set up Sprites for Pi [superfly/pi-sprites](https://github.com/superfly/pi-sprites) 1. 1 Install from GitHub `pi install git:github.com/superfly/pi-sprites` ``` pi install git:github.com/superfly/pi-sprites ``` Not on npm yet. Node.js 24 or later is required by the Sprites SDK. 2. 2 Export a Sprites token into Pi's environment `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` This integration authenticates with a token, not browser OAuth. 3. ✓ Ask Pi to list your environments `List my sprites.` ``` List my sprites. ``` ### Set up Sprites for VS Code [superfly/sprites-vscode-ext](https://github.com/superfly/sprites-vscode-ext) 1. 1 Install the Sprites extension 2. 2 Set your API token `Sprites: Set API Token` ``` Sprites: Set API Token ``` Run it from the Command Palette and paste your Sprites.dev API token. 3. 3 Open a Sprite `Sprites: Open Sprite` ``` Sprites: Open Sprite ``` Its filesystem appears in your workspace, editable in place. 4. ✓ Open a shell on the box `Sprites: Open Terminal` ``` Sprites: Open Terminal ``` Sprites: Create Sprite, Sprites: Delete Sprite, and a right-click Download to Local round out the command set. ### Set up Sprites for Herdr [superfly/herdr-sprites-plugin](https://github.com/superfly/herdr-sprites-plugin) 1. 1 Log in with the Sprite CLI `sprite login` ``` sprite login ``` Linux or macOS, Node.js 22 or newer, Git, and Herdr 0.9.0 or newer. The plugin drives the sprite CLI you just authenticated, so there is no token to paste. 2. 2 Install the plugin from GitHub `herdr plugin install superfly/herdr-sprites-plugin` ``` herdr plugin install superfly/herdr-sprites-plugin ``` 3. 3 Find the plugin's config directory `herdr plugin config-dir sprites` ``` herdr plugin config-dir sprites ``` 4. 4 Choose an organization and an agent config.json ``` { "org": "your-sprites-organization", "agent": "claude" } ``` ``` { "org": "your-sprites-organization", "agent": "claude" } ``` Save it in the directory printed above. agent is claude, codex, or opencode. Add a command array to run a different agent or pass arguments; namePrefix defaults to herdr-. 5. 5 Start an agent from a Git worktree `herdr plugin action invoke start-agent --plugin sprites` ``` herdr plugin action invoke start-agent --plugin sprites ``` Opens a split pane, creates a Sprite, uploads the worktree with its uncommitted edits, checkpoints it, and hands the terminal to the agent. start-claude, start-codex, and start-opencode pick a harness for one launch. Claude Code and Codex reuse your local login when one is available. 6. 6 Optionally, bind it to a key config.toml ``` [[keys.command]] key = "prefix+shift+s" type = "plugin_action" command = "sprites.start-agent" description = "start agent in a Sprite" ``` ``` [[keys.command]] key = "prefix+shift+s" type = "plugin_action" command = "sprites.start-agent" description = "start agent in a Sprite" ``` Herdr's own config file, so the action runs from a prefix key instead of the CLI. 7. ✓ Show the pane's Sprite and sessions `herdr plugin action invoke info --plugin sprites` ``` herdr plugin action invoke info --plugin sprites ``` Info reports the Sprite, its checkpoint, and the remote session list. reconnect reattaches a detached agent, pull brings its edits back into your worktree, and stop, checkpoint, restore, and destroy round out the set. Git history, .env files, and credentials never leave your machine; the Sprite gets a fresh baseline repository. Pull rejects overlapping local edits before touching anything, and reconnect keeps remote files and authentication in place. ### Set up Sprites for Hermes Agent [NousResearch/hermes-plugin-sprites](https://github.com/NousResearch/hermes-plugin-sprites) 1. 1 Use a current Hermes installation with pluggable terminal backends This plugin needs the terminal-backend extension introduced in Hermes PR #94400. The commands below assume the standard macOS/Linux install and default Hermes home. 2. 2 Clone the plugin `git clone https://github.com/NousResearch/hermes-plugin-sprites.git ~/.hermes/plugins/sprites` ``` git clone https://github.com/NousResearch/hermes-plugin-sprites.git ~/.hermes/plugins/sprites ``` 3. 3 Install the supported SDK in Hermes's Python environment `uv pip install --python ~/.hermes/hermes-agent/venv/bin/python 'sprites-py>=0.5.0,<0.6'` ``` uv pip install --python ~/.hermes/hermes-agent/venv/bin/python 'sprites-py>=0.5.0,<0.6' ``` For a custom installation, use its Python environment instead. Do not install into an unrelated system Python. 4. 4 Add a Sprites API token to Hermes's local secrets file ~/.hermes/.env ``` SPRITES_TOKEN=your-sprites-api-token ``` ``` SPRITES_TOKEN=your-sprites-api-token ``` Create a token at sprites.dev/account for the intended organization. Edit the file locally; do not paste the token into an agent prompt or commit it. 5. 5 Enable the plugin `hermes plugins enable sprites` ``` hermes plugins enable sprites ``` 6. 6 Select the terminal backend `hermes config set terminal.backend sprites` ``` hermes config set terminal.backend sprites ``` 7. 7 Check configuration, then start a new Hermes session `hermes doctor` ``` hermes doctor ``` Doctor checks that the token and SDK are present, not that the API token works. Restart any running Hermes session or gateway before trying the backend. 8. ✓ Ask Hermes to execute a command in the Sprite `Use the terminal tool to run uname -a and pwd.` ``` Use the terminal tool to run uname -a and pwd. ``` Check the actual tool result and the Sprite in your Sprites dashboard. First use creates or resumes a Sprite and can incur usage charges. Hermes stays on its host; shell commands run remotely. Sprites persist by default, and remote edits are not automatically copied back. Hermes can upload configured credential files, skills, and caches to the Sprite; review those before use. ### Set up Sprites for Any MCP client [superfly/sprites-mcp](https://github.com/superfly/sprites-mcp) 1. 1 Add a remote server entry mcp.json ``` { "mcpServers": { "sprites": { "url": "https://sprites.dev/mcp" } } } ``` ``` { "mcpServers": { "sprites": { "url": "https://sprites.dev/mcp" } } } ``` Streamable HTTP over JSON-RPC 2.0, authenticated with OAuth 2.1 (sprites:read / sprites:write). Nothing runs locally. 2. 2 If your client only speaks stdio, bridge it mcp.json ``` { "mcpServers": { "sprites": { "command": "npx", "args": ["-y", "mcp-remote", "https://sprites.dev/mcp"] } } } ``` ``` { "mcpServers": { "sprites": { "command": "npx", "args": ["-y", "mcp-remote", "https://sprites.dev/mcp"] } } } ``` mcp-remote handles the OAuth flow on the client's behalf. 3. 3 Authorize in the browser on first use 4. ✓ Ask your agent to prove it's connected `List my sprites.` ``` List my sprites. ``` ### Set up Sprites for Agent Plugins v1 [superfly/sprites-agent-plugin](https://github.com/superfly/sprites-agent-plugin) 1. 1 Install the package with any Agent Plugins v1 client The client discovers plugin.json, the children of skills/, and mcp.json at fixed locations. Agent Plugins standardizes package contents, not the install UI, so follow your client's own local, Git, workspace, or marketplace flow. 2. 2 Complete browser OAuth on first MCP use Restricted connector tokens may enforce a sprite-name prefix, creation cap, label, or expiry. 3. ✓ Ask your agent to prove it's connected `List my sprites.` ``` List my sprites. ``` Claude Code, Grok, and Antigravity are not on the current compatible-client list. Use their dedicated packages above, which also carry hooks the portable format has no equivalent for. ## Which language are you building in? The same primitives the plugins are built on — create, exec, services, checkpoints, network policy. ### Build with Python [superfly/sprites-py](https://github.com/superfly/sprites-py) 1. 1 Install from PyPI `pip install sprites-py` ``` pip install sprites-py ``` 2. 2 Point it at your Sprites account `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` Create a token from the Sprites dashboard. ### Build with JavaScript [superfly/sprites-js](https://github.com/superfly/sprites-js) 1. 1 Install from npm `npm install @fly/sprites` ``` npm install @fly/sprites ``` 2. 2 Point it at your Sprites account `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` Create a token from the Sprites dashboard. ### Build with Go [superfly/sprites-go](https://github.com/superfly/sprites-go) 1. 1 Add the module `go get github.com/superfly/sprites-go` ``` go get github.com/superfly/sprites-go ``` 2. 2 Point it at your Sprites account `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` Create a token from the Sprites dashboard. ### Build with Elixir [superfly/sprites-ex](https://github.com/superfly/sprites-ex) 1. 1 Add the dependency mix.exs ``` {:sprites, "~> 0.2"} ``` ``` {:sprites, "~> 0.2"} ``` 2. 2 Fetch it `mix deps.get` ``` mix deps.get ``` 3. 3 Point it at your Sprites account `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` Create a token from the Sprites dashboard. ### Build with Google ADK [superfly/sprites-adk](https://github.com/superfly/sprites-adk) 1. 1 Install from PyPI `pip install sprites-adk` ``` pip install sprites-adk ``` 2. 2 Point it at your Sprites account `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` Create a token from the Sprites dashboard. ### Build with OpenAI Agents SDK [superfly/sprites-py](https://github.com/superfly/sprites-py) 1. 1 Install from PyPI `pip install sprites-openai-agents` ``` pip install sprites-openai-agents ``` 2. 2 Point it at your Sprites account `export SPRITES_API_TOKEN='...'` ``` export SPRITES_API_TOKEN='...' ``` This adapter reads SPRITES_API_TOKEN rather than SPRITES_TOKEN. The Agents SDK still wants OPENAI_API_KEY of its own. 3. 3 Know what you're pinning The Agents SDK's sandbox APIs are beta, so each release of the adapter supports a deliberately narrow openai-agents version range. The source lives in sprites-py under integrations/openai-agents. ### Build with OpenRouter Agent SDK [superfly/sprites-openrouter-sdk](https://github.com/superfly/sprites-openrouter-sdk) 1. 1 Build from the repository Not on npm yet, and the API may change before the first stable release. 2. 2 Point it at your Sprites account `export SPRITES_TOKEN='...'` ``` export SPRITES_TOKEN='...' ``` Create a token from the Sprites dashboard. ## Give your Sprite access to external APIs Connect through the Sprites API gateway while keeping provider credentials outside your Sprite. Choose a service and grant access in the dashboard. Available providers can vary by organization during rollout. Your dashboard shows which connectors you can enable. ### Use Sprites with Meta (Muse Spark) [fly.io/dashboard](https://fly.io/dashboard) Call Muse Spark from a Sprite while keeping your Meta API key outside the environment. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Meta Use your Meta developer team's API key. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Supports streaming and tool calls through OpenAI-compatible chat completions and responses, and Anthropic-compatible messages. The gateway also allows model discovery; other Meta API paths are blocked. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with OpenAI [fly.io/dashboard](https://fly.io/dashboard) Call OpenAI's Responses, Chat Completions and Embeddings APIs from a Sprite without an OpenAI key inside it. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure OpenAI Create a project API key at platform.openai.com. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Requests are billed to your OpenAI project. Only /v1/responses, /v1/chat/completions, /v1/embeddings and /v1/models are forwarded; files, fine-tuning and organization paths are rejected. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with TypeSafeAI [fly.io/dashboard](https://fly.io/dashboard) Ask Jev typed questions about your data from a Sprite while keeping your TypeSafeAI key outside it. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure TypeSafeAI Create an API key at console.typesafe.ai. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Jev is a decision model, not a chat model: it answers yes/no, choice and score questions with probabilities and confidence. Only POST /v1/systemone and GET /v1/models are forwarded. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Anthropic [fly.io/dashboard](https://fly.io/dashboard) Call Claude models from a Sprite without storing your Anthropic API key inside it. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Anthropic Create an API key in the Anthropic Console. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Requests are billed to your Anthropic account. Only the Messages API (including token counting and Message Batches) and /v1/models are forwarded; files, skills and administration paths are rejected. This is access to the Anthropic API through the gateway, not the Sprites listing in the Anthropic Connectors Directory. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with OpenRouter [fly.io/dashboard](https://fly.io/dashboard) Access models through OpenRouter with your own key or a Sprites-managed connection. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Choose your own key or managed access Use your own key instead accepts an OpenRouter API key. Where managed access is enabled, choose Enable OpenRouter and buy prepaid credits before making requests. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Managed access availability varies by organization. This connector is separate from the OpenRouter Agent SDK in the SDKs tab. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Ollama Cloud [fly.io/dashboard](https://fly.io/dashboard) Use Ollama's cloud-hosted models from a Sprite through the gateway. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Ollama Create an Ollama Cloud API key at ollama.com/settings/keys. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Connects to Ollama Cloud, not an Ollama server running on your laptop. The connection test checks that the gateway reaches Ollama; saving the key is what verifies it. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with GitHub [fly.io/dashboard](https://fly.io/dashboard) Give Sprites access to GitHub repositories, issues, and pull requests. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Authorize GitHub Choose GitHub, continue to GitHub, and approve the requested access. Review the account and permissions before returning to the dashboard. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Access follows the authorizing user's permissions and granted OAuth scopes. Re-authorize from the connector's Scopes editor if more access is needed. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Slack (User) [fly.io/dashboard](https://fly.io/dashboard) Let a Sprite read and post in Slack on your behalf. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Authorize your Slack user Choose Slack (User), select the intended workspace, and approve the requested permissions. Availability varies by organization; Slack may not appear yet. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Acts as the authorizing Slack user. Choose Slack (Bot) instead when messages should come from a bot. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Slack (Bot) [fly.io/dashboard](https://fly.io/dashboard) Let a Sprite work in Slack as a bot rather than as your user. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Authorize the Slack bot Choose Slack (Bot), select the intended workspace, and approve the bot permissions. Availability varies by organization; Slack may not appear yet. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Access depends on the bot's granted permissions and channel membership. It does not have the user connector's search permission. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Discourse [fly.io/dashboard](https://fly.io/dashboard) Read or post on a Discourse forum from a Sprite with your forum permissions. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Authorize your forum account Choose Discourse, enter the forum URL, and select Read-only or Read & write. Approve access on the forum, then paste its authorization code back into the connector form. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. The forum issues a user API key. This is not an admin API key or a Slack-style OAuth connection. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with S3-compatible Object Store [fly.io/dashboard](https://fly.io/dashboard) Access an S3-compatible bucket without keeping its storage credentials in a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure and test your bucket Choose S3-compatible Object Store. Enter the bucket, endpoint URL, region, access key ID, and secret access key. Test the connection before saving. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. The gateway signs storage requests. Use credentials scoped to the bucket and operations you need. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Fly.io Machines [fly.io/dashboard](https://fly.io/dashboard) Call the Fly Machines API from a Sprite using an organization-scoped token. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Generate a scoped Fly.io token Choose Fly.io Machines, select read-only or read-write access, and generate a token. Test the connection and save it. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. A built-in Custom API preset for api.machines.dev. Choose the least access required for your task. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Custom API [fly.io/dashboard](https://fly.io/dashboard) Connect a token-authenticated HTTP API through the Sprites gateway. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure and test your API Choose Custom API. Enter the base URL and token, choose its authentication method, and provide a test URL. Test the connection before saving. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Supports bearer or custom headers, query parameters, and token-bearing URL paths. The upstream must be publicly reachable; private and loopback addresses are blocked. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Steel Browser Tools [fly.io/dashboard](https://fly.io/dashboard) Stateless scraping, screenshots, and PDFs without storing your key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Steel Browser Tools Create a key at app.steel.dev/settings/api-keys. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Saving or replacing a key and each connection test run a one-page scrape charged to your Steel account. Browser Tools requests also use your Steel credits. Only POST /v1/scrape, /v1/screenshot and /v1/pdf are forwarded. CDP, WebSocket connections, sessions, credentials and profile management are not supported. Screenshot/PDF URLs are hosted publicly by Steel. Keep requests under the gateway's 120-second timeout. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Firecrawl [fly.io/dashboard](https://fly.io/dashboard) Scrape, search, and map websites without putting your key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Firecrawl Create a key at firecrawl.dev/app/api-keys. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Scrape, search, and map requests use your Firecrawl credits. Saving, replacing, and testing a key only read credit usage and do not start a scrape. Only POST /v2/scrape, /v2/search, /v2/map and GET /v2/team/credit-usage are forwarded. Crawl, batch jobs, browser sessions and agents are not supported. Keep requests under the gateway's 120-second timeout. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Deepgram [fly.io/dashboard](https://fly.io/dashboard) Prerecorded speech recognition and HTTP text-to-speech with your own Deepgram key. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Deepgram Create a project key at console.deepgram.com. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Saving or replacing a key and each connection test run a roughly 18-second sample transcription charged to your Deepgram account. Transcription and synthesis are also charged by Deepgram. Supports POST /v1/listen for prerecorded audio and POST /v1/speak for HTTP synthesis. Audio responses are buffered until complete; WebSocket realtime speech and Voice Agent are not supported. Request bodies are limited to 8 MB and the upstream timeout is 120 seconds; prefer a publicly reachable audio URL for larger inputs. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Fireworks [fly.io/dashboard](https://fly.io/dashboard) OpenAI-compatible inference without storing your Fireworks key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Fireworks Create an inference key at app.fireworks.ai/settings/users/api-keys. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Inference is charged to your Fireworks account. Saving, replacing and testing read one account name and require account-list permission; they do not verify inference permission or balance. Supports POST chat/completions, completions and embeddings under /inference/v1, including SSE, plus GET /v1/accounts, which lets authorized Sprites list account metadata visible to the key, not only the name read during validation. No account writes, deployments, files or batches. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Parasail [fly.io/dashboard](https://fly.io/dashboard) OpenAI-compatible inference without storing your Parasail key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Parasail Create a standard inference key at www.saas.parasail.io/keys. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Use a standard inference key, not a read-only management key. Saving, replacing and testing only list models; a successful check does not verify inference permissions or credit balance. Inference is charged to your Parasail account. Only POST chat/completions, completions, embeddings and GET models under /v1 are forwarded. SSE streaming is supported; deployment management, files and batches are not. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Depot build insights [fly.io/dashboard](https://fly.io/dashboard) Read container-build status and project metadata without storing a Depot token on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Depot build insights Create a token in the Depot dashboard under Organization Settings → API Tokens, or Account settings → API Tokens for a user token. It must be able to list your organizations; project-only tokens are not supported. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Read-only organization, project and build metadata through ListOrganizations, ListProjects, GetProject, ListBuilds and GetBuild. This connector does not run builds or proxy the Depot CLI/BuildKit; build logs, registry operations and token management are excluded. Saving, replacing and testing list organizations without starting compute. Send Connect JSON requests with Content-Type: application/json and Connect-Protocol-Version: 1. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Upstash Redis [fly.io/dashboard](https://fly.io/dashboard) Read and write Redis data over HTTP without placing your database token on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Enter your database REST URL and token Copy the REST URL and REST token from the Upstash database console. Availability varies by organization during rollout. The URL is immutable; create a new connector for a different database. The gateway supplies the stored token; do not copy it into your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Supports individual key/value, hash, list, set and sorted-set commands. No TCP Redis, SDK auto-pipelines, scripts, transactions, pub/sub or administrative commands. Saving, replacement and tests run PING, which may count toward Upstash usage. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Tigris [fly.io/dashboard](https://fly.io/dashboard) Access Tigris buckets and objects without placing keys on your Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Tigris Supply an existing Tigris access-key ID and secret. Configure bucket and object permissions in Tigris; bucket-listing permission is not required to connect. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Your Tigris key controls access. Authorize only trusted Sprites and keep both credentials off your Sprite. Listings, copies and bulk deletes require a connection without endpoint restrictions; a catch-all allowlist with no blocked paths is unrestricted. Credential checks do not verify storage permissions. Requests may incur Tigris charges. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with AgentMail [fly.io/dashboard](https://fly.io/dashboard) Send and receive email from a Sprite without exposing your AgentMail key. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure AgentMail Use an API key from your existing AgentMail account. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Email resources only, with polling for incoming mail. Sending messages has real external effects and may consume AgentMail usage. Domain, API-key and AgentID administration are not supported. The gateway stores the key; do not copy it into your Sprite. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Resend [fly.io/dashboard](https://fly.io/dashboard) Send email from a Sprite through Resend without putting your API key on it. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Resend Create a Resend API key with Sending access limited to your sending domain. Use a Full access key only if agents must read delivery status. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Sends real email from your domain and uses your Resend quota (every recipient counts). Only sending (single and batch, up to 100) and reading one email's status are forwarded; domains, API keys, contacts, broadcasts and the sent-mail list are refused even with a full-access key. Sending-access keys cannot read delivery status. Saving and testing do not send email. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Neon [fly.io/dashboard](https://fly.io/dashboard) Create and branch Neon Postgres databases without putting your Neon token on the Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Neon Use a Neon API key; choose a project-scoped key if Sprites should only reach one project. OAuth is also available where enabled for your organization. Existing API-key connections do not need to change. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Authorized Sprites can fetch database credentials and manage resources permitted by your Neon authorization or API key. Neon usage is billed to your account. Project deletion, organization and API-key administration, transfers, sharing and Neon Auth are refused. Connection tests only read metadata. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with ElevenLabs [fly.io/dashboard](https://fly.io/dashboard) Build and run ElevenLabs voice agents from a Sprite without putting your API key on it. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure ElevenLabs Create an ElevenLabs API key limited to ElevenAgents (and Voices and Models read if Sprites configure agents), with a credit limit. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Authorized Sprites can create and change agents, knowledge base and tools, read conversations, and place outbound calls, all billed to your ElevenLabs credits. Live conversations connect to ElevenLabs directly with a short-lived signed URL, so the key stays in the gateway. Workspace secrets, settings and members, voice cloning, and text to speech and speech to text are refused. Saving and testing only list agents. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with SenseLab [fly.io/dashboard](https://fly.io/dashboard) Share agent memory, briefings and outcomes across disposable Sprites. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure SenseLab Create a non-admin API key in SenseLab Settings → API Keys. Replace the default * scope with the memory paths and read/write permissions your Sprites need. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Admin keys are rejected. A non-admin key is not necessarily narrowly scoped: the default * scope can grant read/write access to every memory path. Authorized Sprites share the stored key's permissions; use separate scoped keys and connections for isolation. Agent and session IDs are provenance, not access controls. Saving, replacing and testing check key identity and admin status, not write permission. Requests use your SenseLab plan. Only supported memory operations are forwarded; no account administration, branch management, training or subscriptions. Your agent must explicitly read context and record findings and outcomes; the connector does not do this automatically. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Hugging Face [fly.io/dashboard](https://fly.io/dashboard) Run open models and optionally read or publish Hub repositories. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Hugging Face Create a fine-grained Hugging Face User Access Token with Make calls to Inference Providers permission. Add access to specific repositories only if you enable Hub access. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Inference uses your Hugging Face credits or the billing organization you choose. Hub access is off by default; writes allow private repo creation and small commits, including overwriting or deleting files. Repo creation requires private: true; commits to existing public repos still publish publicly. Authorized Sprites share the token's permissions. Saving and testing verify identity, not inference, billing or repo permissions; the gateway returns only a verification result. Downloads may return short-lived signed storage URLs. Responses supports local tools only. No Jobs, Sandboxes, remote MCP or large Git/LFS/Xet uploads. Use Custom API for dedicated Inference Endpoints. Hub and billing settings are fixed after creation. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Blotato [fly.io/dashboard](https://fly.io/dashboard) Publish to existing social accounts through Blotato without exposing its API key. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Blotato Connect social accounts in Blotato first, then provide your Blotato API key. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Creating a Blotato API key ends the free trial and starts a paid subscription. Use existing social accounts connected in Blotato; account authorization is not performed here. Publishing has real external effects and consumes your Blotato plan. Keep the API key off your Sprite. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Keenable [fly.io/dashboard](https://fly.io/dashboard) Search with Keenable without placing its key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Keenable Use an API key from your existing Keenable account. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Saving or replacing a key and each connection test fetch one small public page using your key, which consumes Keenable credits. Search and fetch requests also consume your plan. Only POST /v1/search and GET /v1/fetch are supported. The gateway supplies the stored credential; do not copy it into your Sprite. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with LemonSlice [fly.io/dashboard](https://fly.io/dashboard) Read the history and status of existing LemonSlice sessions. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure LemonSlice Create sessions outside the gateway first, then supply a LemonSlice API key from the developers dashboard. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Read-only session history and status for existing LemonSlice sessions. This connector does not create or control sessions, generate video, or support WebRTC or WebSockets. Saving, replacing and testing a key only read session history; they do not start a paid session. Sessions must already be created outside the gateway. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Mnemom [fly.io/dashboard](https://fly.io/dashboard) Read Mnemom trust and agent information without storing the API key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Mnemom Use an API key from your existing Mnemom account. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Read-only Mnemom agent, state, alignment/protection card, checkpoint, trust-edge, proof/certificate and trust advisory/IOC APIs. Enforcement setup and governance mutations are not supported. Saving and testing verify the key identity without changing agent data. The gateway supplies X-Mnemom-Api-Key; authorize only trusted Sprites. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Era [fly.io/dashboard](https://fly.io/dashboard) Read linked banking data through Era without exposing a banking API key. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Era Link your accounts in Era first and create an fmk key scoped to banking:read. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Read-only banking REST access to accounts already linked in Era: accounts, summaries, balances, transactions, categories and tags. Use an fmk key with banking:read permission, monitor its expiry and rotate it before it expires. Money movement, transfers, payments and account linking are not supported. Authorized Sprites can read the financial data visible to this key. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Composio Tools [fly.io/dashboard](https://fly.io/dashboard) Discover and execute tools against existing Composio connected accounts. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Composio Tools Connect accounts in Composio first. Supply a project API key scoped to tool discovery and execution. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Existing preconnected accounts are required. Use a scoped Composio project API key and the connected_account_id for the account you intend to use. Only tool discovery and named-tool execution are supported; no account setup, OAuth, API-key administration, raw credentials, proxy execution, MCP or sessions. Project access is not isolated to a downstream account or user per Sprite: authorized Sprites can act on the connected accounts permitted by the project key. Tool execution can change external data and incur charges. A successful key check does not verify a particular account or tool-execution permission. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Supabase Database [fly.io/dashboard](https://fly.io/dashboard) Access a hosted Supabase project's REST database API without exposing its secret key. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Supabase Database Copy the hosted project URL from Connect and a modern sb_secret_ key from Settings → API Keys. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Only hosted https://.supabase.co URLs and modern sb_secret_ keys are supported. This elevated key uses service_role and bypasses Row Level Security (RLS): authorized Sprites get project-wide database access to tables, views and RPCs. Use only trusted Sprites. REST database access only; Auth, Storage, Realtime, Edge Functions and project management are excluded. The project URL is fixed after creation. Saving and testing read the REST schema without changing rows. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Usable [fly.io/dashboard](https://fly.io/dashboard) Use your Usable workspace knowledge through its authenticated MCP service. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Usable Use an existing workspace and the official @usabledev/mcp-server@0.21.0 client. Set --usable-url to this connector's gateway URL and --api-token to the dummy value sprites-gateway, never your real key. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. The gateway supplies Bearer authentication to Usable's remote MCP service. Install the official @usabledev/mcp-server@0.21.0 client with this connector's gateway root as --usable-url and the dummy --api-token sprites-gateway; never put your real Usable key on the Sprite. MCP tools can read and write every workspace permitted by the stored key. Only MCP and client compatibility routes are forwarded, not account or API-key administration. Idle streams must reconnect. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Kagi [fly.io/dashboard](https://fly.io/dashboard) Search the web and extract pages with Kagi from your Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Kagi Create an API key without IP restrictions in your Kagi API dashboard and enable API billing. Requests come from the gateway, not your Sprite. For MCP clients, use the official local kagimcp client with the gateway URL as KAGI_API_HOST and the dummy KAGI_API_KEY sprites-gateway. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Enable API billing in Kagi. Saving or replacing a key and each connection test run one search charged to your Kagi API account, without page extraction. Returning one result does not reduce the search price. Search and extraction requests also incur charges. Use a key without IP restrictions; requests come from the gateway, not your Sprite. Authorize only trusted Sprites; never put your real key on a Sprite. Hosted MCP and legacy FastGPT/Summarizer endpoints are not forwarded. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Exa [fly.io/dashboard](https://fly.io/dashboard) Search the web and retrieve page contents without storing your Exa key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Exa Create an API key at dashboard.exa.ai/api-keys. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Saving or replacing a key and each connection test run a one-result search charged to your Exa account. Searches and page content requests also use your Exa credits. Only POST /search and POST /contents are forwarded. The gateway supplies your stored key; do not copy it into your Sprite. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ### Use Sprites with Linkup [fly.io/dashboard](https://fly.io/dashboard) Search the web and fetch pages without putting your key on a Sprite. 1. 1 Open your organization's Sprites Connectors In the Fly.io dashboard, select your organization, then open Sprites → Connectors → Add connector. 2. 2 Configure Linkup Create an API key at app.linkup.so. Availability varies by organization during rollout. The gateway keeps the credential off your Sprite. 3. 3 Grant your Sprite access Open access settings and turn off Allow all sprites before restricting access by name prefix or labels. If you set both, a Sprite must match both. Save the policy. A connector with no access policy denies all Sprites. 4. 4 Test from your Sprite Run the API Usage example from the connector's detail page inside an authorized Sprite. The gateway attaches the stored credential; do not copy it into the Sprite. Searches and page fetches use your Linkup credits. Saving, replacing, and testing a key only read credit balance and do not run a search. Only POST /v1/search, POST /v1/fetch and GET /v1/credits/balance are forwarded. Research and extraction jobs are not supported. Keep requests under the gateway's 120-second timeout. [Open the dashboard](https://fly.io/dashboard) [Read connector docs](https://docs.sprites.dev/concepts/connectors/) ## Use Sprites with your platform Use Sprites as an execution environment for another platform's agents and tools. Pick your product and follow its setup guide. ### Use Sprites with TanStack AI [tanstack.com](https://tanstack.com/ai/latest/docs/sandbox/providers#sprites) Sprites as a sandbox provider for TanStack AI agents. [Read the setup guide](https://tanstack.com/ai/latest/docs/sandbox/providers#sprites) ### Use Sprites with Claude Managed Agents [docs.sprites.dev](https://docs.sprites.dev/integrations/claude-managed-agents/) Anthropic runs the agent loop; each session's tool calls execute inside a Sprite you control. [Read the setup guide](https://docs.sprites.dev/integrations/claude-managed-agents/) ### Use Sprites with Anthropic Connectors Directory [claude.ai/directory/sprites](https://claude.ai/directory/sprites) Let Claude manage your Sprites. Connects Claude to Sprites through the hosted MCP server. For calling Claude models from inside a Sprite, use the Anthropic API connector in the Connectors tab. [Connect to Claude](https://claude.ai/directory/sprites) ### Use Sprites with QM [github.com/yc-software/qm](https://github.com/yc-software/qm) QM includes a built-in Sprites sandbox backend. Select Sprites and provide your Sprites API token. [View QM on GitHub](https://github.com/yc-software/qm) ### Use Sprites with Cursor Cloud Agents [docs.sprites.dev](https://docs.sprites.dev/integrations/cursor-cloud-agents/) Run Cursor Cloud Agent tools on a Sprite while Cursor hosts the agent and model. 1. 1 Prepare your Cursor account Create a Cursor user API key and enable Self-hosted Machines in Cursor's Cloud Agents settings. Use the current privacy setting, not legacy privacy mode. You also need a Sprites organization and a Cursor plan with Cloud Agents. 2. 2 Create the integration in the Fly.io dashboard Select your organization, then open Sprites → Integrations → Cursor Cloud Agents. Enter a name and your Cursor API key to create the Sprite and install the worker. 3. 3 Choose the machine in Cursor Wait for the Sprite to appear under My Machines in Cursor, then select it for a Cloud Agent session. This is separate from the Cursor plugin and API gateway connectors. The worker runs on the Sprite and stores the Cursor API key in its service environment. [Read the setup guide](https://docs.sprites.dev/integrations/cursor-cloud-agents/) ## Straight to the source | Integration | Ships | Auth | Repository | | --- | --- | --- | --- | | Claude Code | MCP Skills Hooks | Browser OAuth | [superfly/sprites-claude-plugin](https://github.com/superfly/sprites-claude-plugin) | | Codex | MCP Skills | Browser OAuth | [superfly/sprites-codex-plugin](https://github.com/superfly/sprites-codex-plugin) | | Cursor | MCP Skills | Browser OAuth | [superfly/sprites-cursor-plugin](https://github.com/superfly/sprites-cursor-plugin) | | Antigravity | MCP Skills Commands Hooks | Browser OAuth | [superfly/sprites-antigravity-plugin](https://github.com/superfly/sprites-antigravity-plugin) | | Grok Build | MCP Skills | Browser OAuth | [superfly/sprites-grok-plugin](https://github.com/superfly/sprites-grok-plugin) | | Cortex Code | MCP Skills Commands Hooks | Browser OAuth | [superfly/sprites-cortex-plugin](https://github.com/superfly/sprites-cortex-plugin) | | DeepSeek Harness | MCP Skills | Browser OAuth | [superfly/sprites-deepseek-plugin](https://github.com/superfly/sprites-deepseek-plugin) | | OpenCode | MCP Skills Commands Hooks | Browser OAuth | [superfly/sprites-opencode-plugin](https://github.com/superfly/sprites-opencode-plugin) | | Pi | SDK Skills | API token | [superfly/pi-sprites](https://github.com/superfly/pi-sprites) | | VS Code | Filesystem | API token | [superfly/sprites-vscode-ext](https://github.com/superfly/sprites-vscode-ext) | | Herdr | Sandbox Commands Filesystem | Sprite CLI | [superfly/herdr-sprites-plugin](https://github.com/superfly/herdr-sprites-plugin) | | Hermes Agent | Sandbox | API token | [NousResearch/hermes-plugin-sprites](https://github.com/NousResearch/hermes-plugin-sprites) | | Any MCP client | MCP | Browser OAuth | [superfly/sprites-mcp](https://github.com/superfly/sprites-mcp) | | Agent Plugins v1 | MCP Skills | Browser OAuth | [superfly/sprites-agent-plugin](https://github.com/superfly/sprites-agent-plugin) | ## What your agent can do with it ### Run the risky stuff somewhere else Builds, migrations, dependency upgrades, and whole test suites run on the Sprite. Your laptop stays clean and stays yours. ### Checkpoint before it breaks things A checkpoint snapshots the whole filesystem in about a second. If the agent wrecks the environment, restore and carry on. ### Keep services running between sessions Dev servers, workers, and databases live on as Sprite services, with a URL you can open. Closing your editor doesn't kill them. ### Confirm before anything destructive Confirmation behavior varies by plugin. Check its safety controls before destructive work; terminal backends such as Hermes do not provide Sprites-specific confirmation hooks. ## $30 in trial credits. Create, like, 500 Sprites free. [Play with Sprites](https://fly.io/app/sign-up)