What Connectors actually do
From inside a Sprite, calling an external API looks like calling a plain HTTP endpoint with no auth attached:
curl https://api.sprites.dev/v1/gateway/github/user/repos
See? No token in that request. You select which Sprites get access to each Connector. The Connector injects the real credentials, and proxies the call. The response streams back as if the Sprite had called the API directly. What the Sprite never gets is the key: that stays in the control plane (encrypted) and is attached to the request on the way out.
This is why you can safely run agents and their integrations (along with the code they generate) in Sprites. An agent that never holds a raw token can't leak it, log it, or ship it off in a curl to somewhere it shouldn't. You get the reach of a fully credentialed client with none of the exposure.
Connect a service once
Connect a service once at the org level, and it becomes a named Connector that any authorized Sprite can use. OAuth providers like GitHub and Slack go through the normal authorize-and-grant flow.
OpenRouter connects for model access with your OpenRouter key. Anything else fits the custom Connector; point it at a base URL, give it a token and how the token is sent, and it's ready to use.
S3-compatible object stores connect the same way, with their own endpoint and credentials. One setup, reused everywhere, instead of a key copied into every environment that needs it.
Agents with Connectors
More power and efficiency, without sacrificing security
-
Every model behind one Connector
Want to try the latest model blowing up the "trust-me-bro" benchmarks? Your OpenRouter Connector puts a huge catalog of models behind a single OpenAI-compatible endpoint. Your agent asks for a model by name and the Connector routes the call, streams the tokens back, and keeps a running tally of what was used.
-
The key never enters the sprite
The credential lives in the control plane, and is injected per request on the way to the provider. Your agent works with your real services while never being able to read the secret behind them. That is Spriteish behavior: hardware isolation around the environment, controlled egress out of it, and a way to hold real API access without the raw token ever touching the box.
-
Scope every Connector
A Connector is not all-or-nothing. No Sprites can use it by default, and you grant access deliberately. Connect all Sprites with a specific label, or those whose name starts with a given prefix.
You scope the endpoints too, with allow and block patterns on the request path: a Connector can permit posting messages on Slack and refuse everything else.
Fresh token, self service discovery
When OAuth tokens expire, Connectors refresh them. A Connector you set up months ago will still work without anyone having to rotate a token by hand. Sprites don't have to guess what they can reach.
A single list call returns the Connectors that are ready to use, each with its base URL, granted scopes, and a copy-paste example, alongside the providers still available to set up.
When an agent wants a permission it doesn't have, the same response points it at the URL to request more scopes. The agent discovers and uses its own integrations, and you decide what shows up there.