Agent Integrations Overview
An agent integration stores the credentials beeps needs to invoke an AI agent: an API key plus any provider-specific settings. Relay rules of ruleType: "agent" reference an integration; when a matching alert fires, beeps invokes the agent, polls until it finishes, and writes the result (usually a PR URL) onto the alert responder.
How it works
Section titled “How it works”- An alert fires on one of your relays.
- A relay rule of
ruleType: "agent"matches and points at an integration. - Beeps invokes the agent over its REST API — whether it’s a provider-hosted cloud agent or one running on your own infrastructure.
- Beeps polls the agent until it reaches a terminal state.
- The alert responder is updated:
done(withprUrlwhen the agent opened one) on success, ordroppedon failure.
Storm-detection holds, alert deduplication, polling intervals, and max-attempts apply to every provider. They’re configured on the relay rule, not the integration. See Relay Rules for the full rule shape.
Supported providers
Section titled “Supported providers”| Provider | How it runs | Output |
|---|---|---|
| Devin | Cloud API | PR URL |
| Cursor | Cloud API | PR URL |
| OpenCode | Self-hosted HTTP | File diff |
| AWS DevOps Agent | Agent Space (HMAC webhook + AWS SDK) | Investigation report |
| Zup | Self-hosted HTTP | Investigation report |
Where to next
Section titled “Where to next”- Pick a provider above for setup instructions.
- Manage integrations: CRUD via SDK, API, or CLI.
- Integration API reference: full endpoint and type reference.
- Best Practices — Agent Integrations: configuration guidelines.
MCP Clients
Section titled “MCP Clients”To connect beeps tools in Claude Code or Codex, see MCP Setup for Claude Code and Codex.