Claude Enterprise Meets Your AI Security Posture: AIR Integrates with Anthropic's Compliance API

AIR already vets the skills, MCPs, plugins, and sub-agents your agents pull into context. Connect Anthropic's Compliance API and Claude's usage and governance data comes into view, so it falls under the same posture, runtime, and supply-chain controls as everything else you run.

Security teams can usually name the AI tools they've approved and the policies they've written. The harder problem is the activity in between: who is running which agent, what it is permitted to do, and which extensions it loaded to do it. For a growing number of teams Claude sits at the center of that activity, yet its usage and governance records have lived inside Anthropic, apart from the AI estate AIR maps.

A single Compliance API key brings the two together. AIR gains read access to your organization's Claude governance, usage, and audit records and folds them into the views your teams already work in, with no new agent to deploy and no export to reconcile by hand. The Compliance API exposes this administrative data only, not the content of prompts or model responses, and the integration covers Claude usage within your Anthropic organization.

Claude, inside your posture

Posture management is AIR's running picture of every agent in your environment and the risk each one carries. The Compliance API places Claude directly into that picture: the workspaces and users that are active, how their configurations drift, and where real usage departs from the policy you set. A misconfiguration becomes a finding in the same queue as the rest of your AI estate, not a separate report someone has to remember to open.

Held to your runtime policy

AIR's runtime layer decides what an agent may do and enforces it action by action. The governance and usage signals from the Compliance API make that enforcement sharper. AIR can surface usage that strays from an approved configuration and hold new Claude workspaces to the same bar every other agent meets before they reach production.

Traced back to the supply chain

A Claude agent is only as trustworthy as the components it loads. Because AIR carries a security verdict on every skill, MCP, plugin, and sub-agent in the marketplace, it can link a Claude workspace or agent to the exact extensions behind it and tell you the moment one of them is unvetted, has changed, or is known to be malicious.

Connecting the Compliance API

Connecting the integration takes one key and a few minutes in the admin console. With an account that holds the Organization Admin role:

  1. Sign in to AIR and open the Admin Console.
  2. Go to Settings → Integrations and select the Anthropic Compliance card.
  3. Paste your key into the Compliance API Key field and select Connect.
  4. AIR validates the key with Anthropic and begins the first compliance sync.

Keys are stored encrypted, used only for read access to your organization's compliance records, and can be rotated or revoked at any time from the same screen.

Get started

Connecting Claude Enterprise to AIR starts with a Compliance API key from your Anthropic organization. Anthropic's documentation covers eligibility, requesting access, and generating the key.

Read Anthropic's guide

Opens support.claude.com in a new tab