Integrations

Findings where
you already work.

Slack alerts, signed webhooks, a REST API, and an MCP server so any AI agent can trigger scans directly - no dashboard required for any of it.

Slack notifications

New critical findings delivered to a Slack channel of your choice within minutes. Useful for security channels and on-call workflows.

  • One incoming webhook per team, configured on the Integrations page
  • Subscribe independently: scan.completed, scan.failed, finding.critical, finding.high
  • "Send test" button to confirm delivery before relying on it

Webhook integration

Push findings to any system - Jira, Linear, PagerDuty, or your own. Signed payloads (HMAC), per-endpoint event selection, and a delivery log.

  • Multiple named endpoints per team, each with its own URL and event selection
  • Signed with HMAC-SHA256 - verify payloads the same way you would with Stripe
  • Delivery log of the last 50 attempts per endpoint, with response status

API access

Trigger scans programmatically and pull results via a REST API - poll status, fetch findings, list scans for a domain. Full OpenAPI docs included.

  • POST /api/v1/scans - trigger a free or full agent scan programmatically
  • GET /api/v1/scans/:id and GET /api/v1/scans?domain=... - poll status and results
  • GET /api/v1/scans/:id/findings - every finding, paginated and filterable by severity or type
  • Full OpenAPI 3.0 spec with interactive Swagger docs

MCP server for AI agents

Let Claude, Cursor, or any MCP-compatible AI agent trigger scans and poll results directly - create_scan, get_scan, list_scans, and wait_for_scan tools, no glue code required.

  • create_scan, get_scan, get_scan_findings, list_scans, and wait_for_scan tools
  • Works with Claude, Cursor, or any MCP-compatible AI agent - no glue code
  • Authenticated the same way as the REST API, team-scoped per session

All four ship on Pro and up.

Configure Slack, webhooks, and API keys from Account → Integrations once you're on a paid plan.

Get started See all features