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?
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
Client-facing applications
Not confirmed
If the firm exposes Claude via a client portal, unqualified-practice and disclosure rules fall on the firm. Commercial Terms require notifying users that outputs may be false.
Ask: Will any end-client application call this API, and what practitioner review is mandatory before the client sees output?
Model provider
Public claim only
Anthropic. Covered Models (including named Fable/Mythos versions) require 30-day retention and are not ZDR-eligible unless expressly authorised. Customer can pin models per request.
Ask: Which model IDs are approved, and will Covered Models be disabled if we require ZDR?
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.
Training
Public claim only
Commercial Terms: Anthropic may not train on Customer Content from the Services. Commercial privacy article: API inputs/outputs not used to train by default. Feedback/bug reports remain an exception if submitted.
Ask: Confirm no-training in the signed API agreement, including embeddings and evaluation datasets.
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.
API keys and SSO
Public claim only
API keys and Console roles (Admin, Developer, Billing, etc.). SSO/JIT/SCIM available for Console organisations on documented tiers. Key handling is the customer's responsibility.
Ask: How are production keys scoped, rotated, stored in our vault, and revoked on leaver?
Encryption
Public claim only
DPA AES-256 at rest, TLS 1.2+. CMEK available for Claude Platform (per workspace) in US regions; some Console features disable when CMEK is on. ZDR is compatible with CMEK.
Ask: Will CMEK be attached to a new US workspace before any prompts are sent?
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.
Contract
Public claim only
Commercial Terms + DPA. Customer owns Outputs. 12-month fee cap. California / SF arbitration for Australian customers. Rate card may change on 30 days' notice.
Ask: Execute DPA, confirm no-training and ZDR on the order form, and negotiate cap/forum if required.
Transfers
Public claim only
US workspace storage. Inference global or US. SCCs in DPA. No Australian region. Cloud-provider routes have their own regions.
Ask: Document inference_geo for production traffic and complete an APP 8 assessment for US storage.
Incidents
Public claim only
DPA 48-hour Security Breach notice. Status page. Responsible disclosure policy. Evaluation-environment incidents have been published separately by Anthropic.
Ask: Confirm 48-hour notice and NDB cooperation for API tenants, plus status-page SLA.
Changes
Public claim only
Terms and prices updatable on 30 days' notice. Model deprecation commitments exist. Feature eligibility for ZDR/HIPAA can change. Covered Model list can expand.
Ask: What notice before a model snapshot is retired or a tool loses ZDR eligibility?
Exit
Public claim only
DPA 30-day export/delete. API customers can export via their own logs if they captured them. Activity Feed is a vendor-side record with a long retention.
Ask: Will we receive deletion of Files, agents, activity feed and abuse stores, with a certificate, within 30 days?
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?
Web search tool
Public claim only
Web search is an API tool using Brave Search / TurboPuffer. Not on by default unless the application enables it. Outside some ZDR/HIPAA feature tables.
Ask: Keep web_search disabled on production keys unless a named non-confidential task requires it.
Tool use and agents
Not confirmed
Managed Agents persist transcripts. Computer use, bash and MCP can act outside the model. Human confirmation is an application design choice. Anthropic can suspend for Usage Policy or attack.
Ask: Which tools require an application-level human confirm, and how do we revoke keys and halt agents immediately?
Oversight
Public claim only
Commercial Terms place evaluation of outputs on the customer. Compliance API Activity Feed (6 years) and Access Transparency support supervision if enabled. The API will not itself refuse to answer a legal question.
Ask: How will our wrapping application log prompts/outputs into our matter file and force lawyer review before use?