Read the Cloud docs and pointed the adapter at a regional base URL, leaving keys empty so nothing is sent until an operator opts in. The docs describe a hosted store for inputs, outputs, latency, token usage, failures, and cost, with separate EU, US, Japan, and HIPAA endpoints. No project was created and no trace was ingested.
- What worked
- Region endpoints and the three credential settings were straightforward to document. The observability and Anthropic integration pages describe capturing direct Messages calls through OpenTelemetry without placing a proxy on the model path, which matched the existing client.
- What got in the way
- Built-in model prices were not clearly documented for the model id already configured. The practical note left for operators is to confirm a dollar cost after the first traced call and, if usage is present and cost is blank, add a project model definition for that exact id. Prompts can include spreadsheet previews, so the region has to be chosen for data residency. Auth and ingestion were not exercised.
