Getting Started
Everything you need to get started with the anymize API.
Everything you need to get started with the anymize API.
The anymize API gives you GDPR-compliant access to all major AI models — with built-in anonymization when you need it.
https://app.anymize.ai/api/v1/llmhttps://app.anymize.ai/api/v1/llm-anonymoushttps://app.anymize.ai/apiGet to your first API request in minutes — it's that simple.
1curl -X POST https://app.anymize.ai/api/v1/llm/chat/completions \2 -H "Authorization: Bearer YOUR_API_KEY" \3 -H "Content-Type: application/json" \4 -d '{5 "model" : "fountain-1 .0 " ,6 "messages" : [7 {"role" : "user" , "content" : "Hello, how are you?" }8 ]9 }'OpenAI Chat Completions plus Anthropic Messages. Streaming, function calling, anonymization included.
Mask personal data before it reaches any model.
Chat and anonymization combined in a single request.
Access GPT-4o, Claude, Gemini, DeepSeek, and more.
OpenAI SDK, Anthropic SDK, Vercel AI SDK, LangChain, n8n. One key, one pipeline.
Fair limits with clear headers and transparent behavior.
API key required
Send your API key as a Bearer token in the Authorization header.
1curl https://app.anymize.ai/api/v1/llm/models \2 -H "Authorization: Bearer YOUR_API_KEY" If your API key is invalid or expired, you'll get a 401 error.
{
"error": {
"message": "Invalid API key",
"type": "invalid_request_error",
"code": "invalid_api_key",
"param": null
}
}{
"type": "error",
"error": {
"type": "authentication_error",
"message": "Invalid API key"
}
}An API key can do everything to begin with. In your key's settings you can take individual areas away. If a key lacks the area it needs, the API answers 403 and names the scope.
{
"error": "api_key_scope_missing",
"scope": "deanonymize"
}| Scope | Endpoints |
|---|---|
| anonymize | /api/anonymize, /api/v1/llm-anonymous, /api/v1/llm/chat/completions/anonymous |
| process_plain | /api/v1/llm/*, /api/v1/messages |
| deanonymize | /api/deanonymize, /api/status/{id}/strings |
| documents | /api/status/{id}, /api/ocr, /api/v1/jobs/*, /api/v1/chunks/* |
| transcribe | /api/transcribe, /api/v1/transcriptions/*, /api/v1/audio/*, /api/v1/meetings/* |
| knowledge:read | GET /api/v1/knowledge-bases/*, /api/v1/rag/search, /api/mcp |
| knowledge:write | POST, PATCH, DELETE /api/v1/knowledge-bases/* |
| files:read | GET /api/v1/workspace/* |
| files:write | POST, PATCH, DELETE /api/v1/workspace/* |
| office | /api/v1/office/* |
| chats | /api/v1/memory/*, /api/v1/search |
| projects | /api/v1/projects/* |
| workflows | /api/v1/workflows/* |
| skills | /api/v1/skills/*, /api/mcp/skills |
| connectors | /api/v1/connectors/* |
| other | * |
process_plain and anonymize also apply to uploads: what counts is whether the document is actually processed anonymized. textType=original on a job export needs deanonymize. Endpoints without an area of their own fall under other.
Protect your API key
You can create, rotate, and revoke API keys in your account settings. Go to API settings