Integrations Overview
ANTS Platform connects to your AI stack in three directions:
- Send data in with an SDK, OpenTelemetry, a framework integration or a connector that pulls from a cloud platform.
- Send findings out to Slack, Microsoft Teams, Jira, Linear, ServiceNow and PagerDuty, and to your security tools through SIEM push and policy violation webhooks.
- Export data to your own storage or to PostHog.
Send data in
SDKs
pip install ants-platform
@antsplatform/tracing and @antsplatform/otel
ai.agenticants:ants-platform-java
Any OTLP/HTTP exporter, any language
Frameworks and model SDKs
Drop-in import (Python) and observeOpenAI (JS/TS)
Callback handler for Python and JS/TS
Native OTel for CrewAI Enterprise, or the SDK EventListener
Coding agents
Claude Code, GitHub Copilot CLI and OpenAI Codex CLI
Push the settings to a fleet
Claude Cowork is supported through its OpenTelemetry monitoring settings. See Claude Cowork.
Notebooks
Connectors (no code changes)
Bedrock Agents from CloudWatch Logs, and Bedrock Flows
Agent Engine from Cloud Logging and Cloud Trace
Copilot interactions from Microsoft Graph, and Copilot Studio traces
Gemini use in Gmail, Docs and other Workspace apps, from the audit log
Send findings out
| Tool | How it connects | What it is used for |
|---|---|---|
| Slack | OAuth app install | Recommendations, unapproved model findings and evidence requests sent on demand; prompt automations |
| Microsoft Teams | Workflows or Incoming Webhook URL, one channel per project | Unapproved model findings and drift alerts sent on demand; drift alerts sent automatically when automatic drift notifications are on |
| Jira | Jira Cloud site, email and API token | Tickets for recommendations, unapproved model findings and evidence requests, on demand |
| Linear | Personal API key | Issues for recommendations, unapproved model findings and evidence requests, on demand |
| ServiceNow | Instance URL with Basic Auth or API key | CMDB sync of agents, automatic incidents for detected violations, risk records |
| PagerDuty | REST API key | A service per agent, automatic incidents for detected violations, on-demand incidents |
| Policy violation webhooks | Signed JSON webhook, the Webhook action of an automation rule, with a v2 event envelope | Guardrail violations, drift alerts, unsanctioned tool use and Discover AI device alerts, filtered by rule conditions such as category and severity, for Falcon Fusion SOAR, Splunk SOAR, Tines or a ServiceNow flow |
Drift alerts can be sent to Microsoft Teams, ServiceNow and PagerDuty.
Security operations
Next-Gen SIEM and Fusion SOAR
Real-time events and alerts to Falcon Next-Gen SIEM, Splunk and other HEC collectors
Signed, documented payloads for your SOAR playbooks
Export data
Scheduled export to S3, S3-compatible storage or Azure Blob Storage
Traces, generations and scores as PostHog events
Where integrations are configured
| Location | Integrations |
|---|---|
| Project Settings > Integrations | PostHog, Blob Storage, Slack, Microsoft Teams, Jira, Linear, ServiceNow, PagerDuty, and the AI Studio connectors (AWS Bedrock, Google Vertex AI) |
| Organization Settings > Integrations | Okta and Microsoft Entra ID directories, Microsoft 365 Copilot, Microsoft Copilot Studio, Google Workspace (Gemini), SIEM Push |
| Project Settings > Automations | Policy violation webhooks, as the Webhook action of a rule |
| Project Settings > API Keys | Keys for the SDKs, OpenTelemetry and coding agents |
Project integrations apply to one project. Configuring them needs the Owner role or a custom role with the matching Integrations access. See Members & Roles.
Some integrations need an entitlement or deployment configuration: blob
storage export needs the scheduled-blob-exports entitlement; the Microsoft
and Google Workspace connectors need enterprise-governance; and on self-hosted deployments the
Bedrock, Vertex and Microsoft connector services are off by default. Each
page lists its requirements.
Planned integrations are listed on the roadmap.