TypeSafe AI Swift SDK

The README describes it as a dependency-free Swift client ported from the official JavaScript and Python SDKs, and its Package.swift snippet uses a typesafe-ai organization path, while the repository here lives under alterhq. Which of those URLs actually resolves for SwiftPM is not documented in the README, so verify the dependency URL before wiring it into a target.

Not on iOS. Direct API-key initialization is blocked by default on iOS/iPadOS, tvOS, and watchOS, with dangerouslyAllowAPIKeyInClient reserved for controlled development builds. The recommended production shape on every platform is your own authenticated backend holding the key with the client pointed at your baseURL, and supplying any explicit authentication strategy bypasses TYPESAFE_API_KEY even when it exists in your environment.

Implement HTTPTransport and inject it into TypeSafeClient. The repository's suite uses a scripted actor-backed transport, so serialization, decoding, retry behavior, timeouts, cancellation, and errors are all covered without network requests, and swift test runs it. Live integration testing is intentionally deferred until an API key is available, so nothing in the suite proves a live call works.

Every error conforms to TypeSafeError: TypeSafeConfigurationError for bad config or request input, APIError for non-2xx with status, kind, body, headers, requestID and retryAfterMilliseconds, plus APIConnectionError, APITimeoutError, APIUserAbortError for caller cancellation, and APIResponseValidationError carrying the failing field path. Defaults are a 10-second per-attempt timeout and two retries on 408, 429, 5xx, connection failures and timeouts, with retry-after headers taking precedence.

macOS 13+, iOS/iPadOS 16+, tvOS 16+ and watchOS 9+, built on Swift 6 strict concurrency, URLSession, Codable and native task cancellation, with no third-party packages. Installation is a SwiftPM entry at from: "0.6.0" plus a dependency on the product named TypeSafe, so it drops into an Xcode target without a package manager beyond SwiftPM.

Five steps, spelled out in the README: authenticate and authorize the incoming app request, accept only the SDK routes /v1/systemone and /v1/models, forward the JSON body to the matching https://api.typesafe.ai route, replace the app's authentication header with Authorization: Bearer <TYPESAFE_API_KEY> server to server, and return the upstream status, JSON body and useful headers such as X-TypeSafe-Request-ID. The backend must never return or log the key and should not blindly forward arbitrary client headers upstream.

Logging defaults to warn, settable with TYPESAFE_LOG_LEVEL across debug, info, warn, error and off. Every header returned by your authentication provider is redacted from debug output, and sensitiveHeaderNames can additionally mark conditional headers that may originate in another layer. Request and response bodies are redacted too unless you set logBodies: true, and explicit initializer values take precedence over the environment.