> For the complete documentation index, see [llms.txt](/llms.txt).
> A full single-fetch corpus is available at [llms-full.txt](/llms-full.txt).
---
title: Integrations
description: Connect AGNT5 to external services - model providers, event sources, and more - with credentials stored once and scoped to a workspace, project, or environment.
last_verified: 2026-07-09
---

An **integration** connects AGNT5 to an external service. Credential integrations are configured in Studio, while deployment-host integrations are configured in the provider project and connected with the AGNT5 CLI.

Integrations fall into these families today:

- **[AI providers](/docs/integrations/ai-providers.md)** - model APIs your agents and prompts call: OpenAI, Anthropic, Google, Groq, OpenRouter, Mistral, DeepSeek, and xAI. The credential is an **API key**.
- **[Sandbox providers](/docs/integrations/sandbox-providers.md)** - isolated code execution providers your agents use through `Sandbox()`: E2B, Daytona, Vercel, Northflank, and Together. The credential is an **API key** or provider token.
- **[Event sources](/docs/integrations/event-sources/overview.md)** - third-party services that trigger your workflows over webhooks: Sentry, Stripe, GitHub, Slack, and any Standard Webhooks publisher. The credential is a **signing secret**.
- **[Deployment hosts](/docs/integrations/cloudflare-workers.md)** - provider-managed runtimes that serve AGNT5 components over the serverless protocol. Start with Cloudflare Workers and keep provider deployment controls in Wrangler.

---

## How an integration is stored

Every integration is a **provider** plus one or more **secrets**:

- **Provider** - which service it connects (for example `openai` or `sentry`).
- **Secret role** - what the credential is for. `api_key` calls a provider's API; `webhook_secret` verifies the signature on an inbound webhook.

Secrets are stored encrypted and decrypted only at the point of use: the gateway fetches a `webhook_secret` to verify a delivery, and a worker receives an `api_key` as an environment variable when it deploys. Your code never sees the raw secret material.

---

## Scope

An integration applies at the scope you create it in:

- **Workspace** — available to every project in the workspace.
- **Project** — available to a single project.

A secret can additionally be pinned to one **environment**, so a production key can differ from staging. Choose the narrowest scope that works: a production billing secret belongs on the project or environment, not the whole workspace.

---

## Manage integrations

In Studio, open **Integrations** to add, view, and remove credential integrations and their secrets. Adding one has the same shape regardless of credential category: pick the provider, choose the scope, and supply the credential.

<DocsImage
  src="/docs/integrations/configure-light.png"
  darkSrc="/docs/integrations/configure-dark.png"
  alt="Screenshot of the AGNT5 Studio Integrations page. The page shows a search field, display control, add integration button, and configured integrations grouped by provider type and connection status."
  caption="Studio shows configured integrations with provider type and connection status before you add or edit a credential."
  width={1008}
  height={639}
/>

What that credential is, and where you get it, depends on the category — follow the guide for [AI providers](/docs/integrations/ai-providers.md), [sandbox providers](/docs/integrations/sandbox-providers.md), or [event sources](/docs/integrations/event-sources/overview.md). Deployment hosts use their provider CLI instead; follow [Deploy a serverless endpoint to Cloudflare Workers](/docs/integrations/cloudflare-workers.md).

---

## Related

- [AI providers](/docs/integrations/ai-providers.md): connect model APIs for agents and prompts.
- [Sandbox providers](/docs/integrations/sandbox-providers.md): connect isolated code execution providers for agents.
- [Event sources](/docs/integrations/event-sources/overview.md): connect Sentry, Stripe, GitHub, and Slack.
- [Cloudflare Workers](/docs/integrations/cloudflare-workers.md): deploy and connect a provider-hosted serverless endpoint.
- [Webhooks](/docs/build/webhooks.md): trigger workflows from inbound events.