> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Connect Superagent to agents, services, and internal tools.

# Interfaces

Use MCP, Webhooks, and the REST API to connect Superagent to the tools that
investigate findings, automate security work, or consume results.

## Choose an interface

| Interface | Use it when |
| --- | --- |
| [MCP](https://www.superagent.sh/docs/mcp) | An AI agent needs to read findings, start security work, or return a structured result |
| [Webhooks](https://www.superagent.sh/docs/webhooks) | Another tool or service needs events when reports, findings, updates, or guardrail decisions change |
| [REST API](https://www.superagent.sh/docs/api) | Your application needs direct programmatic access to Superagent resources |
| [SystemOne API](https://www.superagent.sh/docs/models/api) | Your service needs a calibrated security decision from Security-One |

Most automated remediation workflows use Webhooks to start work and MCP to
read or update the current Superagent record.

## Before you connect

Create a dedicated organization `sk_live_` API key for each MCP, REST API,
or [SystemOne API](https://www.superagent.sh/docs/models/api) integration.
Store API keys and webhook receiver credentials in the destination's secret
manager, keep them out of prompts and repositories, and retain human approval
for consequential actions.

## Next steps

- [Connect through Superagent MCP](https://www.superagent.sh/docs/mcp)
- [Subscribe to events with Webhooks](https://www.superagent.sh/docs/webhooks)
- [Use the REST API](https://www.superagent.sh/docs/api)

---
Source: https://www.superagent.sh/docs/build
Index: https://www.superagent.sh/llms.txt