Tags

Tags give the ability to mark specific points in history as being important

  • v0.3.1

    a2e6417d · v0.3.1: add applied credit to billing usage line items · 
    v0.3.1

- Added the optional `AppliedCredit` field to `BillingUsageLineItem`. It holds the credit that covers the usage and is nil for uncovered usage.
- Added the `BillingUsageLineItemAppliedCreditType` type with the constants `BillingUsageLineItemAppliedCreditTypeCREDIT`, `BillingUsageLineItemAppliedCreditTypePOSTPAID` and `BillingUsageLineItemAppliedCreditTypePREPAID`, and a `Valid` method.

  • v0.3.0

    b107df20 · v0.3.0: drop remediation_id param from create remediation · 
    v0.3.0

- Breaking: the upstream spec dropped the optional `remediation_id` query parameter from the create remediation operation, so `RemediationServiceCreateRemediationParams` was removed.
- Breaking: the `params *RemediationServiceCreateRemediationParams` argument was removed from `Client.RemediationServiceCreateRemediation`, `Client.RemediationServiceCreateRemediationWithBody`, `ClientWithResponses.RemediationServiceCreateRemediationWithResponse` and `ClientWithResponses.RemediationServiceCreateRemediationWithBodyWithResponse`. The `ClientInterface` and `ClientWithResponsesInterface` entries changed the same way.
- Breaking: `NewRemediationServiceCreateRemediationRequest` and `NewRemediationServiceCreateRemediationRequestWithBody` no longer take the params argument.

  • v0.2.0

    2ae4e789 · v0.2.0: regenerate client for new upstream spec · 
    v0.2.0

- Breaking: the generated client now follows the new upstream spec, which puts the version in each path. Create the client with the base URL `https://api.together.ai` and drop `/v1` or `/v2`. One client now reaches both versions.
- Breaking: methods without a version in their name were removed and replaced by versioned ones. For example `Client.GetFineTunesModelsSupported`, `Client.GetFiles`, `Client.GetBatches` and `Client.GetDeployments` became `GetV1FineTunesModelsSupported`, `GetV1Files`, `GetV1Batches` and `GetV1Deployments`. The `WithResponse` variants and the `ClientInterface` and `ClientWithResponsesInterface` entries changed the same way, as did the matching params types such as `GetFineTunesModelsLimitsParams`.
- Breaking: the upstream spec dropped `GET /v1/models`, so `Client.Models`, `ClientWithResponses.ModelsWithResponse` and `ModelsParams` are gone. `SupportedModelsServiceListSupportedModelsWithResponse` calls `/v2/supported-models` and returns a different shape, with the models in `JSON200.Data`.
- Breaking: `ChatCompletionMessageParam.FromChatCompletionFunctionMessageParam` and `MergeChatCompletionFunctionMessageParam` were removed.
- Breaking: the `FunctionCall` field was removed from the delta in `ChatCompletionChunk.Choices`.
- Added many `V1` operations, for example `GetV1FilesIdContent`, `PostV1FineTunesEstimatePrice`, `PostV1ImagesGenerations` and `PostV1DeploymentsIdRollback`. See the type definitions for the full list.
- The module now requires Go 1.26.10, which fixes `GO-2026-6809` in `crypto/x509`. The development image is pinned to the same version.
- The README, the agent skill and the tests use the new base URL and the supported models call.

  • v0.1.3

    f4c1b38d · docs: show how to look up the full API in the skill and README · 
    v0.1.3

- Documentation only. The agent skill explains how to look up every endpoint, parameter and model with `go doc` or on pkg.go.dev, and declares its license.
- The skill no longer lists the API credentials under OpenClaw's `requires.env`, which kept OpenClaw from loading it until they were set. It requires only `go`; the credentials are still documented as what your program reads.
- The README points to the full API reference, and the examples in the README and the skill were checked against the current code.
- The setup reference says that operations under `/organizations`, `/public`, `/supported-models`, `/videos` and some `/projects` paths use the `https://api.together.ai/v2` server, which the generated client does not switch to on its own, so they need a second client with that base URL.

  • v0.1.2

    4f6b7e1e · v0.1.2: document the daily regeneration workflow · 
    v0.1.2

- Documentation only. The README and `AGENTS.md` describe the daily regeneration workflow: what it checks, how it fixes failing checks, how it picks the next version and which paths a fix may not touch.

  • v0.1.1

    6044774d · v0.1.1: add the go-togetherai agent skill · 
    v0.1.1

- Added the `go-togetherai` agent skill. It installs with `claude plugin install go-togetherai@psyb0t` in Claude Code, `codex plugin add go-togetherai@psyb0t` in Codex and `openclaw skills install @psyb0t/go-togetherai` from ClawHub.

  • v0.1.0

    ba074c2d · v0.1.0: Together AI client generated from the official OpenAPI spec · 
    v0.1.0

- Added `together`, a REST client generated with oapi-codegen from Together AI's OpenAPI document (spec version 2.0.0, OpenAPI 3.1.0).
- `make generate` downloads the current spec from docs.together.ai, patches the two shapes oapi-codegen can't read (discriminators without a mapping, inline enums on array items inside a union) and regenerates the client. The spec is not committed.