# Anthrophic Claude API Documentation

## Kurzbeschreibung
Through the Claude API, **Anthropic** offers state-of-the-art LLMs for natural language processing, reasoning, coding, agent-based workflows, tool usage, 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 recommends the Messages API; additionally, Managed Agents are available for longer-running tasks.

## Claim
LLM: "a 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 a trial credit.
- **other:** **Token-based Claude API** Billing based on model families 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 volumes of requests 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 via AWS Bedrock, Google Vertex AI, and Microsoft Foundry; regional pricing and data management 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 details specific privacy-related components for use in the EU/EEA context, but does not provide comprehensive evidence of GDPR compliance for standard use. Positive aspects include documented data residency controls, zero data retention upon request, and self-hosted sandboxes for parts of the execution. At the same time, the website currently lists 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. Furthermore, the AVV/DPA, subprocessors, and specific certifications cannot be found on the website itself or are only indirectly referenced via a link to an external trust center. For users throughout Europe, GDPR-compliant use is therefore only realistic under certain conditions and following their own contractual and organizational review.


**Positive**


The website documents data residency controls via 'inference_geo' and 'workspace geo', zero data retention as a special contractual provision available upon request, as well as self-hosted sandboxes, where tool execution and the sandbox file system remain on customer-controlled infrastructure. In addition, the AWS variant explicitly designates Anthropic as the data processor for inference inputs and outputs.


**Negative**


The website currently documents only “us” as an available option for “workspace geo”; an 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 worldwide Anthropic data centers. The Terms of Service (TOS)/Data Processing Agreement (DPA), subprocessors, specific server locations in the EU/EEA, and relevant certifications are not listed on the website or are not viewable on the domain itself.


**Server Location**


No EU/EEA server location is listed on the website. For first-party data residency, only “us” is documented as the sole available “workspace geo”; for “inference_geo,” both “us” and “global” are described. For Claude Platform on AWS, it is also stated that, when set to “global,” inference can be routed to any of Anthropic’s 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 performance in coding, agent-based workflows, computer use, document comprehension, and long contexts.
- Clear tiering based on price/performance: Opus for maximum quality, Sonnet as a productive standard, Haiku for speed and volume.
- Strong business/privacy positioning: DPA, SCCs, zero data retention for suitable APIs, documented retention rules.
- Useful API features such as prompt caching, batch processing, tools, structured control, and service tiers.

## Nachteile
- The most powerful model (Opus 4.7) is more expensive than necessary for many everyday workloads; Sonnet 4.6 or Haiku 4.5 are often a more cost-effective choice.
- 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 use in terms of inference geotargeting; broader regional options are primarily 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/