Integrations
Expunct integrates with several developer surfaces. They are distribution surfaces, not separate products — every integration calls the same Redaction API, and (where supported) the same Document Intelligence API.
Surface coverage matrix
| Surface | Redaction | Document Intelligence (beta) |
|---|---|---|
Raw HTTP (curl / httpx / fetch) | ✓ | ✓ (recommended path today) |
Python SDK (expunct) | ✓ | Coming in a future release |
Node.js SDK (@expunct/sdk) | ✓ | Coming in a future release |
CLI (expunct-cli) | ✓ | Coming in a future release |
MCP server (@expunct/mcp) | ✓ | Coming in a future release |
LangChain (langchain-expunct) | ✓ | Not planned for the LangChain package — call HTTP directly from your chain |
Until SDK / CLI / MCP support for Document Intelligence ships, the truthful onboarding path for parse, extract, and safe-parse is raw HTTP.
Integration options
-
MCP Server — Use Expunct redaction tools directly in Claude Code, Claude Desktop, and other MCP-compatible clients. The
@expunct/mcpnpm package provides a stdio-based Model Context Protocol server. -
Claude Code Skill — Teaches Claude Code when and how to use Expunct automatically. Activates on keywords like “redact”, “PII”, and “sanitize”.
-
LangChain —
langchain-expunctis drop-in PII redaction middleware. Today it covers the Redaction API only. -
SDKs — Python and Node.js libraries for custom integrations. Type-safe clients for the Redaction API.
-
Document Intelligence (beta) — Parse, extract, and safe-parse PDF and DOCX. Use raw HTTP today; integration-surface support is rolling out.
-
Webhooks — Get notified when jobs complete or fail. Configure webhook endpoints in your redaction policies to receive real-time status updates.
-
Cloud Connectors — Automatically sync and redact files from S3 and GCS. Configure cloud storage credentials and watch folders to process files as they arrive. See the cloud connectors documentation for setup details.