Skip to main content

Overview

Preview: The ZeroDrift API and this documentation are in preview. Endpoints and response formats may change before general availability.
The ZeroDrift Enforcement API enforces regulations, company policies, and security controls on content and communications. Every result is a verdict. Pass. Rewrite. Block. Escalate. The API returns the verdict; Guard applies it inline.

Authentication

All API endpoints require authentication via API Key in the request header. Your Enforcement API key is provisioned when your account is created.

Quick Start

Enforcement runs in two steps. Send content and get a job ID. Poll for the verdict.
  1. Send content with Enforce Content — the response returns a job_id
  2. Poll Get Results until the job is done or failed

Policy

Import a policy and ZeroDrift extracts enforceable rules. Review, activate, train an adapter in Training Studio, then enforce against it.
  1. Upload a policy document (PDF, DOCX, or plain text), or sync one from a connected MCP source
  2. Poll until AI rule extraction completes
  3. Review or simulate the rules, then activate them
  4. Start adapter training from the activated import
  5. Poll training status until the adapter succeeds
  6. Enforce with the import ID in validation_scope.imports
You can also create and edit custom rules directly via POST /api/policies/rules and PATCH /api/policies/rules/{rule_id}.

Activity

Every verdict is logged in Command. The Activity endpoints read that log for the last 30 days.

OpenAPI specification

A machine-readable OpenAPI 3.0 document of the public API is available at /openapi.json. See OpenAPI specification for the operations it covers, and Generate a client SDK to produce a typed Python or TypeScript client from it.

Rate Limits

Contact support@zerodrift.ai for higher limits.

Support

For API support or to request higher rate limits, contact: support@zerodrift.ai For data handling and retention, see Data Retention.