AckuityRequest access
Menu
Request accessHomePlatformThreat modelsDiscoverResourcesSurveyTeamContact

INTEGRATIONS

Three ways to connect Ackuity to your agents.

Ackuity is the Agent Execution Control Switch AI builders add to their agents, verifying every action before it runs. Pick the way in that fits where your agents run. Everything stays in your cloud account.

View full diagram
Three ways to connect Ackuity, ordered left to right by depth of coverage. Event pull: Ackuity attaches beside your telemetry and reads agent events from OpenTelemetry, Langfuse or LangSmith. It is observe-only and the fastest start. API injection: Ackuity attaches beside the agent platform and connects through the APIs of platforms such as Copilot Studio. Sidecar: Ackuity attaches beside the agent and runs in the agent's pod, in the execution path. An init container reroutes traffic, so there is no agent code change, and it gives the deepest coverage. Everything stays in your cloud account.FASTEST STARTDEEPEST COVERAGE01 · EVENT PULLEvent pullATTACHES BESIDE TELEMETRYAgentTelemetryREADSAckuityReads agent events fromOpenTelemetry, Langfuseor LangSmithOBSERVE-ONLY02 · API INJECTIONAPI injectionATTACHES BESIDE THE PLATFORMAGENT PLATFORMAgentAPISAckuityConnects through the APIsof agent platforms such asCopilot StudioPLATFORM AGENTS03 · SIDECARSidecarATTACHES BESIDE THE AGENTAGENT PODAgentAckuityTools and APIsRuns in the agent's pod.An init container reroutestraffic. No agent code change.IN THE EXECUTION PATHEverything stays in your cloud account.
Ackuity connects to agents in three ways: event pull reads the telemetry you already collect, API injection works through agent platforms, and the sidecar sits in the execution path for the deepest coverage. Everything stays in your cloud account.

SIDECAR · DEEPEST COVERAGE

In the execution path.

Checks every action before it runs, and can stop it.

AVAILABLE

Ackuity sidecar for Kubernetes

Runs in the agent’s pod. An init container reroutes traffic, so the agent needs no code change.

IN DEVELOPMENT

NVIDIA OpenShell

Connects to the OpenShell supervisor through its middleware hook, so sandboxed agents get context-aware verdicts.

API INJECTION · PLATFORM AGENTS

Inside agent platforms.

For agents built on hosted platforms where you cannot run a sidecar.

AVAILABLE

Microsoft Copilot Studio

Ackuity connects through the platform’s APIs to check agent actions.

EVENT PULL · OBSERVE-ONLY

From the telemetry you already collect.

The fastest way to start. Ackuity reads agent events and reports findings without blocking anything.

AVAILABLE

OpenTelemetry

Pulls agent traces and spans you already export.

AVAILABLE

Langfuse

Pulls agent traces from your Langfuse projects.

AVAILABLE

LangSmith

Pulls agent runs from LangSmith.

YOUR QUESTIONS, ANSWERED

Before you take the next step.

Which way in should we start with?

Start with event pull if you want results fast. It reads the telemetry you already collect and changes nothing. Move to the sidecar or API injection when you want Ackuity to stop actions before they run.

Does Ackuity work with NVIDIA OpenShell?

An integration is in development. Ackuity is building it on OpenShell’s supervisor middleware, so the supervisor can ask Ackuity for a verdict on each outbound action.

Do any of these need agent code changes?

No. The sidecar reroutes traffic with an init container, API injection works through the platform, and event pull reads existing telemetry.

Does Ackuity replace our gateway, IAM or SIEM?

No. Ackuity works alongside them and feeds them the context they lack about each agent action.

NEXT STEP

Not sure which way in fits?

Tell us where your agents run, and we’ll suggest the fastest start.

Request access