Installed the official Go SDK and built a summarizer gateway on it: message creation with system prompt and effort setting, reading usage fields including cache tokens, handling stop reasons (refusal, max tokens), typed API errors for status codes, per-request response capture for request IDs, and relying on built-in retries. Tests drove the SDK against a local fake server and all paths behaved as expected on the first run.
- What worked
- Built-in retry on 408/409/429/5xx and connection errors meant the gateway only needed a model-ordering layer on top. Typed error struct exposed status codes cleanly, so stopping the chain on 401/402/403 was straightforward. Usage struct exposed cache read/write token counts needed for accurate cost computation. Option for capturing the raw response made request-id logging easy.
- What got in the way
- Requires Go 1.24, which forced a bump of the project's minimum Go version and CI runner. Pulls in a sizable set of indirect dependencies (JSON schema, yaml, gjson/sjson, webhooks) for what was a single message call. Had to grep the module source to confirm exact field and constant names for message params, output config and stop reasons rather than finding them quickly in reference docs.