Documentation
Maskflare documentation
Put Maskflare between your AI traffic and the providers, then tune what it masks.
Quickstarts
- Gateway mode
Send your application's AI calls through Maskflare by changing the SDK's base URL and key. Personal data is masked before it reaches the provider.
- Proxy mode
Route AI traffic through the Maskflare proxy with HTTPS_PROXY, without changing application code. The proxy inspects AI provider hosts only.
- SDKs (mask and unmask)
Mask personal data in any text with the Python or TypeScript SDK, send the masked text anywhere, and restore the values later.
- MCP servers
Mask the arguments and results of MCP tool calls by registering the MCP server in Maskflare and pointing your agent at the gateway.
- Desktop agent
Protect AI apps and tools on Windows, macOS and Linux devices: deploy the Maskflare agent with your MDM or let people sign in.
Concepts
- Concepts
Environments, API keys, policies, rule actions and packs, approvals, shadow rules, and how masking tokens and response re-hydration work.
Console
- Console guide
What each page of the Maskflare console shows and does, from Traffic and Policies to Devices, Webhooks and Compliance.
Reference
- Platform API
Automate Maskflare with an API client: keys, providers, masking rules, devices and audit events over a versioned OpenAPI 3.1 API.
- Error codes
Every problem code the gateway and the proxy return, what it means and how to fix it.
- Detector reference
Every detector with its pack, category, an example and the keywords that gate it.