General-purpose · General-purpose assistants · High confidence

Claude API

Anthropic, PBC · First-party Claude API and Claude Platform (api.anthropic.com). ZDR and HIPAA-ready are optional and feature-limited. Amazon Bedrock, Google Vertex AI and Microsoft Foundry need separate profiles/contracts.

Developer API for Anthropic models. Zero data retention is available on eligible endpoints only. The wrapping application owns retrieval, logging, identity and human gates.

Opens a private software assessment of Claude API for one task, with this profile’s questions to hand.

Document summarisationContract draftingAgentic workflowsKnowledge search
Published facts
DeploymentSaaS, Private cloud
Hosting regionsUnited States, Worldwide or dynamically routed
Australian regionNo
Model providersAnthropic
AssuranceSOC 2 Type II, ISO 27001:2022, ISO/IEC 42001:2023, CSA STAR, NIST 800-171
Training on customer contentNo
Retention summaryStandard API deletes inputs/outputs within 30 days. ZDR available on request for eligible Messages/Token Counting features and Claude Code; many features excluded. Covered Models require 30-day retention. Activity Feed 6 years.
IntegrationsAmazon Bedrock (separate contract), Google Vertex AI (separate contract), Microsoft Foundry (separate contract)
Pricing summaryPublished token pricing by model. Optional US-only inference multiplier. Batch discount advertised. Console/API credits or invoiced spend depending on account.
Legal content coverageNone native. Any legal grounding is supplied by the wrapping application.
Australian presenceYes — API access from Australia is supported. Workspace geo is US-only. Named AU customers may use Platform, Team or Enterprise; not confirmed as API-only.

Product and intended use

Define the configuration, people, information and tasks being assessed.

Plan in scope

Public claim only

Direct Claude API (api.anthropic.com) and Claude Platform, including optional Claude Platform on AWS. Bedrock, Vertex and Foundry are separate contracts with the cloud provider as processor. ZDR and HIPAA-ready are optional arrangements with feature eligibility tables. Console playground is outside ZDR.

Ask: Confirm we are contracting first-party API versus Bedrock/Vertex/Foundry, and list enabled endpoints, tools, Files API, Batch, Managed Agents and MCP.

Deployment

Public claim only

API SaaS. Workspace geo is currently US-only and cannot be changed after workspace creation. Inference geo is global (default) or us, on Claude 4.6+ models, at 1.1x price for US-only. Private-cloud style options are Bedrock/Vertex/Foundry under other agreements.

Ask: Record workspace geo, default_inference_geo and allowed_inference_geos in the order form.

API features

Public claim only

Messages, Token Counting, Files, Batch, Skills, Managed Agents, code execution, web search/fetch, computer use and MCP connectors. Several of these are excluded from ZDR (Console, Managed Agents, Claude for Excel, consumer products, some Covered Models, CORS, third-party integrations).

Ask: Which API features will be enabled, and which of them fall outside ZDR or HIPAA-ready?

Australia

Public claim only

Australia is supported for API access. There is no Australian workspace geo. Global routing may process inference in selected countries including Australia; storage remains US.

Ask: Is US storage plus optional AU inference routing acceptable under our APP 8 and client guidelines?

Adoption and implementation

Record the practical work needed to introduce and maintain the software.

Application integration

Not confirmed

The API has no Word add-in of itself; the customer application must implement identity, logging and save-back. Console organisations can use SSO/JIT/SCIM (SCIM on Enterprise/Console parent orgs).

Ask: Who owns the wrapping application (internal build, Harvey, Legora, other) and does that wrapper's contract flow down these API terms?

Quality and human effort

Compare complete work at the required quality, including checking and correction.

Task fit

Not confirmed

The API is a model endpoint. Task fit is determined by the customer application (prompts, retrieval, citations, human gates). Using the raw API for advice or court documents without those controls is a firm design choice, not a product guarantee.

Ask: Document the wrapping application's retrieval sources, citation checks and refusal behaviour for our tasks.

Data, controls and requirements

Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.

Subprocessors

Public claim only

Published list (GCP, AWS, Azure, Cloudflare, and feature services). DPA flow-down and 15-day objection. Web search (Brave, TurboPuffer) applies if that tool is enabled.

Ask: Map each enabled API tool to a subprocessor and disable unused tools.

Feedback

Public claim only

Console thumbs-up/down and explicit bug reports can retain conversations up to 5 years and allow training. Avoid sending matter content through those channels.

Ask: Disable or administratively forbid feedback from production API keys.

Retention and ZDR

Public claim only

Standard API: inputs/outputs deleted within 30 days except Files API, agreed otherwise, ZDR, Covered Models, Usage Policy flags or law. ZDR: Anthropic does not store prompts/responses at rest after the response is returned, per organisation, on eligible Messages/Token Counting features and Claude Code with commercial keys; must be enabled by sales. Console, Managed Agents, consumer products, Team/Enterprise UIs, Claude for Excel, and several tools are outside ZDR. Activity Feed retains 6 years.

Ask: Enable ZDR in writing for our organisation, list excluded features we will not call, and state Covered Model handling.

Deletion

Public claim only

DPA 30-day return/delete on termination. ZDR organisations have little stored content to delete except excluded features, flags and legal holds. Files API and Managed Agents persist until deleted by the customer.

Ask: How are Files, batches, agent transcripts and abuse-monitoring stores deleted on instruction, with what certificate?

Human access

Public claim only

Access Transparency can log Anthropic personnel views of covered Messages API and Claude Code content to the Compliance API (eligibility required; does not cover claude.ai apps, consumer, Files/Batch/non-ZDR features, or Bedrock/Vertex). Automated safety processing does not emit those events.

Ask: Enable Access Transparency for our API organisation and confirm support staff cannot read prompts without a logged reason code.

Assurance

Public claim only

Trust Center: Claude via Anthropic API in scope for SOC 2 Type II, ISO 27001, ISO 42001, CSA STAR, HIPAA, NIST 800-171. Reports on request. Not inspected here.

Ask: Provide current reports scoped to the first-party API, including AI features we will call.

Tools and MCP

Public claim only

API tools (web search, MCP, computer use, code execution) send data to subprocessors or customer-configured MCP servers. They are often outside ZDR. The wrapping app must not enable them by default for privileged matter.

Ask: Which tools are allowed on production keys, and are MCP servers only our own allow-listed endpoints?

Sources

Official pages reviewed for this profile, last reviewed 2026-09-20.

Related tasks

Related tools

Add this product to your toolset for a particular task, or use it with a practice-area checklist. Add to your toolset Practice areas Best AI general-purpose assistants tools Australia