Skip to content
Agentic Control Plane

Install in your AI client. Keep everything else.

ACP sits between your AI client and the tools it calls. Install the hook (or point at our MCP endpoint) and every tool call gets identity, policy, and audit — without changing how your team works.

Building the agent yourself (CrewAI, LangGraph, Anthropic Agent SDK, OpenAI Agents SDK)? See Frameworks for guided starter code.

Clients

The AI tools your team already uses.

Step-by-step install guides for each AI client — with the caveats vendor docs leave out. Two install paths: a local hook (for coding agents) or an MCP server connection (for chat clients).

Using a client we don't list? If it speaks MCP (Windsurf, Continue, ChatGPT’s connectors) or the OpenAI chat-completions API, point it at ACP — same governance, no code change.

Identity Providers

Your IdP. Your users. Our governance.

ACP verifies JWTs against your IdP's JWKS endpoint on every call. Any OIDC-compliant provider works out of the box — your users stay in your directory.

Auth0 OIDC + JWKS
Okta OIDC + JWKS
Microsoft Entra ID OIDC + JWKS
Google Identity Google Workspace SSO
Firebase Auth Firebase tokens
Any OIDC provider Configurable issuer, audience, JWKS URI

How agent identity works →

What every integration gets

Regardless of which client you install — every agent action passes through the same governance pipeline.

Identity binding
JWT-verified user or agent on every call
Deny-by-default policy
Per-call authorization enforcement
PII detection
Scan and redact sensitive data
Audit logging
Identity-attributed trail on every action
Budget controls
Per-user and per-agent spend limits
Tenant isolation
Multi-tenant separation at every layer

Your clients. Our governance.

Free to start. Add governance to your existing AI client in minutes.