Works with your agent. Yes, that one too.

1. 1

   Install from npm

   $ npm install @fly/sprites
2. 2

   Point it at your Sprites account

   $ export SPRITES_TOKEN='...'

   Create a token from the Sprites dashboard.

1. 1

   Add the module

   $ go get github.com/superfly/sprites-go
2. 2

   Point it at your Sprites account

   $ export SPRITES_TOKEN='...'

   Create a token from the Sprites dashboard.

1. 1

   Add the dependency

   mix.exs

   {:sprites, "~> 0.2"}

2. 2

   Fetch it

   $ mix deps.get
3. 3

   Point it at your Sprites account

   $ export SPRITES_TOKEN='...'

   Create a token from the Sprites dashboard.

1. 1

   Install from PyPI

   $ pip install sprites-adk
2. 2

   Point it at your Sprites account

   $ export SPRITES_TOKEN='...'

   Create a token from the Sprites dashboard.

1. 1

   Install from PyPI

   $ pip install llama-index-tools-sprites
2. 2

   Point it at your Sprites account

   $ export SPRITE_TOKEN='...'

   This adapter reads SPRITE_TOKEN. Create a token from the Sprites dashboard.

1. 1

   Install from PyPI

   $ pip install sprites-openai-agents
2. 2

   Point it at your Sprites account

   $ 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.

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='...'

   Create a token from the Sprites 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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://<project-ref>.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.

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.

Let agents in your Sprites request one-time payment cards from your Link wallet, approved by you in the Link app.

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 Link

   Choose Continue with Link and approve access in Link. The connection belongs to the Link account that approves it: every spend request goes to that person for approval. New connections allow no Sprites until you grant access. 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.

Your Sprite pays with a one-time virtual card, so your real card number isn't shared. An approved spend request returns the virtual card's number, CVC and expiry to the Sprite so the agent can check out. Anyone who controls an allowed Sprite can read them. The card works once and expires after 12 hours. Each spend request is approved by the Link account owner in the Link app within 30 minutes. Sprites cannot approve their own requests. Link allows up to $500 per spend request, $500 per day and $20,000 per 30 days. Agent payments are available in the US and Canada; financial insights scopes are US only. A connection is one person's wallet. Use the access policy to limit it to that person's Sprites; other Sprites that are allowed can still create spend requests for the owner to approve.

Read, download and upload files in your Box account from trusted 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 Box

   Continue with Box and approve file access. No Sprites can use a new connection until you grant 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.

Box requires read and write permission (root_readwrite), even for downloads. Allowed Sprites can read files, create folders and upload new files or versions wherever your Box account has permission. Metadata may include shared or signed content links. This is not a metadata-only or folder-scoped grant. Tokens refresh only when the connection is used. Box refresh tokens expire after 60 days and can be used once. Reconnect with the same Box account after idle expiry or revoked access; existing Sprite grants are preserved. Uploads are limited to 50 MiB including multipart overhead; chunked uploads are not supported. Downloads are limited to 64 MiB per response; use Range for larger files. Deletion, sharing changes and account administration are not forwarded.

Use Codex with your ChatGPT plan and keep credentials in the connector.

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 Codex

   Sign in with ChatGPT when creating a Sprite in the Codex integration. 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.

Requests use your ChatGPT plan and its usage limits.

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.

HTTP observability for Managed Cloud or self-hosted Gigapipe

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 Gigapipe

   Choose Managed Cloud or self-hosted and enter the public HTTPS endpoint. Supply a Cloud API token, or a username and password for self-hosted Basic authentication. 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.

Authorize only trusted Sprites. They can read or write telemetry wherever the credential permits. Prefer query-only Cloud tokens; self-hosted credentials have no scopes. Endpoint, deployment and username stay fixed during key rotation.

Use DigitalOcean's intelligent model routing without storing the 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 DigitalOcean Inference

   Create a model access key in DigitalOcean Inference → Manage. Scope it to the routers/models you need and select No VPC network: requests originate from the Sprites gateway, not a DigitalOcean VPC. 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 DigitalOcean account. Authorized Sprites can use any router or model the saved key permits. Prefer a scoped model access key over a broader personal access token. Saving, replacing and testing only list models; no billable inference is generated. A passing check does not confirm access to a particular router/model, deployment readiness or available credit.

Have Echo draft docs, release notes and posts in a chosen voice 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 Echo

   Sign in with Google at echo.fulcrum.inc/keys and create an 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.

Requests run on your Echo account and count toward its usage. Authorized Sprites can make any request the key permits on the forwarded routes. Saving, replacing and testing a key only list models; no writing is generated. A passing check does not confirm available usage.

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.

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.

Start voice sessions without putting your Vocal Bridge 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 Vocal Bridge

   Create and configure an agent in Vocal Bridge, then copy its agent-scoped API key. Account-wide keys that require an agent ID are not supported. 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 obtain voice-session credentials for this agent. Voice usage is billed to your Vocal Bridge account. Treat returned tokens as secrets and only authorize trusted Sprites. Saving, replacing and testing a key read version metadata without creating a session. A passing check does not verify that the agent is deployed or that your account has available usage.

Use Gemini models with your Google API key held outside 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 Google Gemini

   Create a Gemini API key in Google AI Studio at aistudio.google.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.

Usage follows your Gemini Developer API project's billing and quotas. This connection does not grant Antigravity subscription or Vertex AI access. Only generation, streaming, token counting, model listing and decision creation are forwarded. Request bodies are limited to 8 MB and the Files API is not forwarded, so large images, audio, video and PDFs cannot be sent inline or uploaded. Where an endpoint accepts one, pass a public or signed HTTPS URL instead; the Decisions API takes URLs up to 15 MB.

Run Nebius GPU jobs without putting cloud credentials 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 Nebius Serverless AI Jobs

   Create a dedicated Nebius service account with job permissions scoped to your project and upload an RSA public key for it as an authorized key. You need the service account ID, project ID, public key ID and matching private key. Saving verifies access by listing jobs without starting compute. 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.

Jobs run and incur charges in Nebius. Use project-scoped IAM and Nebius quotas. The project ID selects the setup test; it is not a gateway project or spending restriction. The service account's IAM permissions determine accessible projects. The gateway renews the access token before it expires. To rotate the key, replace the credential for the same service account and project, then revoke the old key in Nebius. Mount durable storage for results: job disks disappear after termination. Jobs logs and object-storage downloads are outside this connector.

Use CockroachDB with PostgreSQL drivers while the platform holds its password.

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 CockroachDB

   Use S2 Sprites, a public CockroachDB Cloud SQL endpoint and an existing dedicated database role. 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.

All authorized Sprites share this SQL role. Restrict it with CockroachDB grants. Saving, rotating and testing credentials connect over verified TLS and run SELECT 1.

Read Granola meeting notes without storing your API key on a Sprite.

This connector is built and maintained by the community, not Fly.io.

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 Granola

   On a Granola Business or Enterprise plan, open Settings → Connectors → API keys in the desktop app. Create a key with the note access scopes you need, then paste it here. Workspace admins can also create a workspace 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.

Requires a Granola Business or Enterprise subscription. Saving or testing a key reads at most one note summary and creates no meeting or AI summary. Requests count against Granola’s API rate limits. Read notes, summaries, transcripts, folders and spaces, and search notes or transcripts. Webhooks, audit logs, legal holds and account management are not forwarded. Results follow the key’s scopes and workspace controls. An empty list passes the key check. Only notes with a generated summary are returned. Transcript access may be disabled by an administrator; a successful check does not verify that permission.

Read and write your Notion workspace from a Sprite without putting the token on it.

This connector is built and maintained by the community, not Fly.io.

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 Notion

   Create an internal connection at app.notion.com/developers/connections, copy its token from the Configuration tab, then share the pages or databases it may use (page menu, Connections, Add connection) or grant them under the connection's Content access tab. 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.

Notion's API has no per-request charge. Saving or testing the token reads the token's bot user (GET /v1/users/me). Notion rate limits each connection to 180 requests per minute (600 on Business and Enterprise plans) and answers with 429 and a Retry-After header when exceeded. Forwards the Notion data APIs: users, search, pages (including /markdown and /move), blocks, databases, data sources and queries, views and view queries, comments, file uploads, custom emojis and async tasks. The connection only sees content shared with it. OAuth, Notion Agents and Sessions, AI meeting notes, workspace analytics and Admin APIs are not forwarded. Every request must include a Notion-Version header (currently 2026-03-11); the gateway forwards it as sent and Notion returns 400 missing_version without it. Writes and deletes have real effects in your workspace; deleting a block or trashing a page moves it to Notion's trash.

Nscale serverless inference without storing your service token on a Sprite.

This connector is built and maintained by the community, not Fly.io.

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 Nscale

   Sign in at console.nscale.com, open Settings → Service Tokens and create a service token. Copy the token when it is shown, then paste it here. 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, replacing and testing a token only call GET /v1/models and run no paid inference. Chat, text completions and embeddings consume your Nscale credits. A successful check does not verify inference permissions or credit balance; Nscale documents 429 for insufficient credit. Only GET /v1/models, POST /v1/chat/completions, POST /v1/completions and POST /v1/embeddings are forwarded. Completions can stream with SSE. Images, endpoint management, compute, storage, service tokens, billing and account management are not forwarded. Nscale service tokens are time-limited. Rotate an expiring token in Nscale and replace it in this connection; the connector does not refresh tokens automatically.

Send push notifications from a Sprite without putting your Pushover token on it.

This connector is built and maintained by the community, not Fly.io.

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 Pushover

   Create an application at pushover.net/apps/build and copy its API Token/Key. This is not the user key on your dashboard; your Sprite passes that as user on each request. 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 testing the token reads your monthly limit (GET /1/apps/limits.json) and sends nothing. Each account can send 10,000 messages a month across all its applications; after that Pushover answers 429 until the limit resets on the 1st. Only POST /1/messages.json, POST /1/users/validate.json, GET /1/apps/limits.json and GET /1/receipts/:receipt.json are forwarded. Groups, teams, subscriptions, licensing, Glances, receipt cancellation and the Open Client API are not. Pushover takes the token as a request parameter, so the gateway adds it to the query string as token, replacing any token your Sprite sends. URLs are logged more readily than headers, including on Pushover's side. Every send is delivered to real devices. Messages are limited to 1,024 characters. Pushover temporarily blocks IP addresses that send many failing (4xx) requests, and every request reaches Pushover from the shared gateway IP, so do not retry a rejected request unchanged.

Open-weight models and specialized small models without storing your ZeroGPU key on a Sprite.

This connector is built and maintained by the community, not Fly.io.

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 ZeroGPU

   Log in at platform.zerogpu.ai/dashboard, open API Keys and create a key (it starts with zgpu-api-). 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 ZeroGPU account. Saving, replacing and testing a key read GET /v1/me, which is free and does not check your balance; an account without credit saves its key, and inference then returns 402 until you add credit. Only POST /v1/chat/completions and POST /v1/responses (including SSE streaming) and GET /v1/me (the key's own key, project and organization IDs) are forwarded. Requests run in the key's own project. Model listing, embeddings, moderations, audio, batches, files, API keys, billing and account routes are not forwarded.

Anthropic runs the agent loop; each session's tool calls execute inside a Sprite you control.

Google runs the agent loop; shell and file tools execute inside a Sprite you control.

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.

QM includes a built-in Sprites sandbox backend. Select Sprites and provide your Sprites API token.

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.

Run Mastra agents' commands in persistent Sprites sandboxes with @mastra/sprites.

1. 1

   Install the sandbox provider

   $ npm install @mastra/sprites

   Requires Node.js 24 or later.

2. 2

   Point it at your Sprites account

   $ export SPRITES_TOKEN='...'

   Create a token from the Sprites dashboard.

Run Pydantic AI agents' commands and file edits in SpritesSandbox, including Temporal workflows.

Let Goose manage Sprites and other Fly.io resources through Fly MCP.

1. 1

   Add Fly MCP to a Goose session

   $ goose session --with-streamable-http-extension https://mcp.fly.io

   This setup uses mcp.fly.io so Goose can manage Sprites and other Fly.io resources.

2. 2

   Authorize in the browser

   Complete OAuth for the intended Fly.io organization and authorize Sprites access. Goose can also use other Fly.io resources through this connection, limited to the permissions you approve.

Give Datasette Agent tools to manage Sprites, run shell commands, and read and write files.

1. 1

   Install the plugin in your Datasette environment

   $ datasette install datasette-agent-sprites
2. 2

   Configure the Sprites secret

   $ export DATASETTE_SECRETS_SPRITES_API_KEY='...'

   Use your Sprites API token; the plugin reads it through datasette-secrets.

datasette-agent-sprites 0.1a0 requires Datasette 1.0a28 or later; stable Datasette 0.65.x is not supported.