Python SDK v2.0 release candidate adds Jobs API and Hardware API

Together AI is releasing the Python SDK v2.0 Release Candidate, a new, OpenAPI-generated, strongly-typed client that replaces the legacy v1.0 package and brings the SDK into lock-step with the latest platform features.

• Install: pip install together==2.0.0a9.
• RC period: The v2.0 RC window starts today and will run for approximately one month. During this time Together will iterate quickly based on developer feedback and may make a few small, well-documented breaking changes before GA.
• Type-safe, modern client: Stronger typing across parameters and responses, keyword-only arguments, explicit NOT_GIVEN handling for optional fields, and rich together.types.* definitions for chat messages, eval parameters, and more.
• Redesigned error model: Replaces TogetherException with a new TogetherError hierarchy, including APIStatusError and specific HTTP status code errors such as BadRequestError (400), AuthenticationError (401), RateLimitError (429), and InternalServerError (5xx), plus transport (APIConnectionError, APITimeoutError) and validation (APIResponseValidationError) errors.
• New Jobs API: Adds first-class support for the Jobs API (client.jobs.*) so you can create, list, and inspect asynchronous jobs directly from the SDK without custom HTTP wrappers.
• New Hardware API: Adds the Hardware API (client.hardware.*) to discover available hardware, filter by model compatibility, and compute effective hourly pricing from cents_per_minute.
• Raw response and streaming helpers: New .with_raw_response and .with_streaming_response helpers make it easier to debug, inspect headers and status codes, and stream completions via context managers with automatic cleanup.
• Code interpreter sessions: Adds session management for the code interpreter (client.code_interpreter.sessions.*), enabling multi-step, stateful code-execution workflows that were not possible in the legacy SDK.
• High compatibility for core APIs: Most core usage patterns, including chat.completions, completions, embeddings, images.generate, audio transcription/translation/speech, rerank, fine_tuning.create/list/retrieve/cancel, and models.list, are designed to be drop-in compatible between v1 and v2.
• Targeted breaking changes: Some APIs (Files, Batches, Endpoints, Evals, code interpreter, select fine-tuning helpers) have updated method names, parameters, or response shapes. These are fully documented in the Python SDK Migration Guide and Breaking Changes notes.
• Migration resources: A dedicated Python SDK Migration Guide is available with API-by-API before/after examples, a feature parity matrix, and troubleshooting tips to help teams smoothly transition from v1 to v2 during the RC period.