Skip to main content
Audact
See the offer

Connectors

Governance where the enterprise already works.

Four connectors planned · no dates set

An integration connects a tool to an agent. A connector does something different: it surfaces Audact governance inside a platform an organisation has already standardised on, so the DPO, the risk team or the Azure administrator does not have to learn a second console. Four are planned, each with its own scope.

The four

What each one is for.

  • Platform
    OneTrust
    What it surfaces
    Consent records and governance events in the privacy console
    Status
    Planned
  • Platform
    ServiceNow
    What it surfaces
    Governance events into GRC and ITSM workflows
    Status
    Planned
  • Platform
    Azure Marketplace
    What it surfaces
    Deployment and billing through your Azure agreement
    Status
    Planned
  • Platform
    Anthropic MCP
    What it surfaces
    Audact governance as Model Context Protocol tools in Claude Enterprise
    Status
    Planned

The distinction that keeps being missed

Two MCP surfaces, and they are not the same thing.

The Audact platform MCP server is the generic surface a Model Context Protocol client would connect to (In development).

They carry different scopes, and conflating them is how a procurement conversation goes wrong. Each has its own page for that reason.

Questions

What does Planned mean here?
That we are building towards it and no date is set. It is not a signed partnership, a marketplace listing, or a pilot with a customer.
Do I need a connector to use Audact with these platforms?
No. The six endpoints run inside the managed platform and a connector is a shorter path, not a precondition; no public API is served on api.audact.ai yet, apart from the published Merkle roots. Access runs through onboarding, and availability is confirmed per endpoint there.

Access runs through onboarding

Every connector on this page is a wrapper around the same six endpoints. They run inside the managed platform; no public API is served on api.audact.ai yet, apart from the published Merkle roots. The evidence chain they write is identical.

See the API

Related