Skip to main content
When a service offers keys or tokens but not OAuth or MCP, paste the key once. Skydive stores it as a secret, injects it into requests at the network layer, and never exposes it to the model. This also covers your own internal APIs and anything else that authenticates with a header. When a service offers keys or tokens but not OAuth or MCP, paste the key into a secure card. Skydive stores it as a secret, injects it into requests at the network layer, and never exposes it to the model.
1

Generate a key from the service

Most services have an API keys or developer settings section. Create a key there and copy it.
2

Add the connection

From the agent’s connections, choose the service and paste the key when prompted.
3

You're connected

The key is stored securely. The agent uses it on every request without seeing the raw value.
Keep the scope tight when the service lets you. An agent that only reads data doesn’t need write access. If you need to rotate the key later, paste the new one in the same place and the old one stops working.

​
Calling an API directly

With the key stored, the agent calls the service the normal way and the proxy attaches the credential in flight. It does not need a wrapper or an SDK, and it never handles the raw value.

​
Managing a connection

Once a service is connected, manage it from the integration’s card in your workspace. The card shows which agents use the connection and gives you two options to pull access back:
  • Remove from one agent. The connection stays live for your other agents.
  • Disconnect entirely. This revokes Skydive’s access at the provider and removes it from every agent using it.

Catalog

Every service available to connect.

Permissions

How credentials stay out of the model’s reach.