# Anthrophic Claude API Docs

## Kurzbeschreibung
**Anthropic** offers current LLMs via the Claude API for language processing, reasoning, coding, agentic workflows, tool use, and document-related tasks. According to the official model overview, all current Claude models support text and image input, text output, multilingual capabilities, and vision. For direct API access, Anthropic refers users to the Messages API; Managed Agents are also available for longer-running tasks.

## Claim
LLM “highly performant, trustworthy, and intelligent AI platform”

## Geeignet für
- API Integration
- Automation / Workflows
- Education
- Data Analysis
- Data Extraction / Document Analysis
- Customer Service & Chatbots
- Programming / Software Development
- Research
- Writing & Editing
- Texts / Content
- Knowledge Management / Internal Search

## Kernfunktionen
- Document analysis
- Function calls
- AI agents
- LLM API
- Multimodal AI
- Programming
- Reasoning model
- Language model
- Text generation

## Preismodell
- **free:** Anthropic states that new users receive a small amount of free credits to test the API. However, this is not a traditional permanent free plan in the SaaS sense, but rather trial credit.
- **other:** **Token-based Claude API** Billing by model family such as Opus, Sonnet, and Haiku, as well as input, output, cache-write, and cache-read tokens.


**Prompt Caching** Reuse of large prompts, system instructions, or document contexts to reduce costs and latency.
**Batch API** Asynchronous processing of large request volumes with a reduced billing model.


**Long Context / 1M Context** Available for certain current models; suitable for very large documents, codebases, and analysis contexts.


**Data Residency / Third-Party Platforms** Claude is also available through AWS Bedrock, Google Vertex AI, and Microsoft Foundry; regional pricing and data handling depend on the respective platform.

## DSGVO und Datenschutz
**Gesamteinschätzung:** Conditional

**On-prem / local hosting: partially**


No full on-prem model hosting is documented on the website. However, with self-hosted sandboxes, tool execution and the sandbox file system remain on customer-controlled infrastructure; the model inference itself continues to run at Anthropic.


**Private Cloud / Data Center: Partially**


"Claude Platform on AWS" is documented, featuring Anthropic-operated infrastructure, AWS integration, and support for AWS PrivateLink. This is a more controlled cloud connection, but there is no documented dedicated EU/EEA data center listed on the website.


**EU SaaS / Managed: Indirect / Not Available**


The provider does not specify an EU/EEA data residency for its first-party SaaS on its website. For “workspace geo,” only “us” is currently documented; EU SaaS in the strict sense is therefore not supported.


**Hybrid: Partially**


The combination of external Claude inference and self-hosted sandboxes enables a hybrid setup in which parts of the processing remain within the customer’s own infrastructure. However, the website describes this only for certain components, not as a complete hybrid product model.


**TOS / DPA: unclear**


A General Terms of Service (GTC) or Data Processing Agreement (DPA) is not provided on the website. While the website describes individual contractual arrangements such as the ZDR or BAA, it does not provide a GTC or DPA for EU/EEA customers that is viewable on the domain itself.


**No training: partial**


The website documents zero data retention upon request; in such cases, data is not stored after the API response is returned, except where required by law or to combat abuse. However, there is no general statement clearly documented on the website itself indicating that content is generally not used to train the general model.


**Open Source / Transparency Path: Indirect / Not Available**


An open-source model or self-hostable complete product is not specified on the website. While there are technical transparency measures such as self-hosted sandboxes and documented APIs, there is no genuine open-source/sovereignty path for the core model on the website.


**Data Processing**


The website describes two levels of data residency controls for the Claude API: 'inference_geo' for the location where model inference is performed per request, and 'workspace geo' for at-rest storage and endpoint processing. For the first-party documentation, only “us” is currently specified as “workspace geo.” For “inference_geo,” “us” and “global” are documented; “global” allows routing through any available regions. For Claude Platform on AWS, it is explicitly stated that Anthropic operates the infrastructure, serves as the data processor for inference inputs and outputs, and that content can be processed outside of AWS. Self-hosted sandboxes move tool execution and the file system to the user’s own environment, while the actual model inference remains external.


**Conclusion**


For an EU/EEA tool directory, the documentation is mixed from a hosting and GDPR perspective. Strengths include the control options for data retention and parts of the execution, as well as the documented hybrid option via self-hosted sandboxes. Weaknesses preventing a positive overall rating in the EU/EEA include the lack of EU/EEA data hosting documented on the website, the workspace location currently documented only as “us,” and the lack of information on the website itself regarding the AVV/DPA, subprocessors, and certifications. Therefore, the overall rating is “conditional.”


**Sources**


- [https://platform.claude.com/docs/it/about-claude/pricing](https://platform.claude.com/docs/it/about-claude/pricing)
- [https://platform.claude.com/docs/de/manage-claude/data-residency](https://platform.claude.com/docs/de/manage-claude/data-residency)
- [https://platform.claude.com/docs/en/manage-claude/api-and-data-retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention)
- [https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws](https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws)
- [https://platform.claude.com/docs/en/managed-agents/self-hosted-sandboxes-security](https://platform.claude.com/docs/en/managed-agents/self-hosted-sandboxes-security)
- [https://platform.claude.com/docs/en/api/ip-addresses](https://platform.claude.com/docs/en/api/ip-addresses)
- [https://platform.claude.com/docs/en/docs/about-claude/security-compliance](https://platform.claude.com/docs/en/docs/about-claude/security-compliance)

The documentation on platform.claude.com substantiates individual privacy-relevant components for use in an EU/EEA context, but not fully substantiated GDPR compliance for standard use. Positive aspects include documented data residency controls, Zero Data Retention upon request, and self-hosted sandboxes for parts of execution. At the same time, the website currently documents only 'us' as the workspace geo for the First-Party Claude API; an EU/EEA data center or EU data residency is not specified on the website. DPA, subprocessors, and specific certifications are also not available on the website itself or are referenced only indirectly via an external Trust Center notice. GDPR-compliant use for users across the European region is therefore realistically possible only subject to certain conditions and with their own contractual and organizational review.


**Positive**


The website documents data residency controls via 'inference_geo' and 'workspace geo', Zero Data Retention as a contractual special arrangement upon request, and self-hosted sandboxes in which tool execution and the sandbox file system remain on infrastructure controlled by the customer. In addition, the AWS variant explicitly describes Anthropic as a data processor for inference inputs and outputs.


**Negative**


The website currently documents only 'us' as the available option for 'workspace geo'; EU/EEA data residency or an EU data center location is not specified. For the standard API, 'global' is also documented as a possible inference route, meaning potentially Anthropic data centers worldwide. DPA, subprocessors, specific server locations in the EU/EEA, and relevant certifications are not specified on the website or cannot be viewed on the domain itself.


**Server location**


No EU/EEA server location is stated on the website. For First-Party data residency, only 'us' is documented as the sole available 'workspace geo'; 'us' and 'global' are described for 'inference_geo'. For Claude Platform on AWS, it is also stated that inference with 'global' may be routed to any Anthropic-operated data centers worldwide.

## Hosting und Daten
- **On-Prem / lokales Hosting:** teilweise / indirekt
- **Private Cloud / Rechenzentrum:** teilweise / indirekt
- **EU SaaS / Managed:** unknown
- **Hybrid:** teilweise / indirekt
- **AVV / DPA:** unknown
- **Kein Training auf Kundendaten:** teilweise / indirekt
- **Open-Source / Transparenz-Pfad:** unknown

## Standort
**Land:** USA

**Taxonomie:** USA

Anthropic, PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, USA

## Vorteile
- Very strong position in coding, agentic workflows, computer use, document understanding, and long contexts.
- Clear price/performance tiering: Opus for maximum quality, Sonnet as the productive standard, Haiku for speed and volume.
- Strong business/privacy positioning: DPA, SCCs, Zero Data Retention for eligible APIs, documented retention policies.
- Useful API features such as prompt caching, batch processing, tools, structured control, and service tiers.

## Nachteile
- The most powerful model directly available (Opus 4.7) is more expensive than necessary for many everyday workloads; Sonnet 4.6 or Haiku 4.5 is often more economical.
- The model portfolio is smaller than that of some competitors, but still requires explanation due to active and older snapshots that remain available.
- For strict regional requirements, the direct Claude API (1P) is publicly designed primarily for global or US-only inference geo-routing; broader regional options are mainly available on partner platforms such as Bedrock and Vertex.
- Anthropic explicitly states in its Commercial Terms that factual claims in outputs should be independently verified before use.

## Quellen
- Offizielle Website: https://platform.claude.com/docs/it/about-claude/pricing

## Letzter Datenstand
2026-04-16

## Originalseite
https://kifox.ai/en/ki-tools/anthrophic-claude-api-docs-en/