Add undocumented public fine-tunes endpoints

[connermanuel]

No description provided.

[github-actions]

✱ Stainless preview builds

This PR will update the togetherai SDKs with the following commit message.

feat: Add undocumented public fine-tunes endpoints

Edit this comment to update it. It will appear in the SDK's changelogs.

✅ togetherai-typescript studio · code · diff

Your SDK built successfully.
generate ⚠️ → build ✅ → lint ✅ → test ✅

npm install https://pkg.stainless.com/s/togetherai-typescript/7e1d0c669ffe8fa9ddabe30bd444184569ccc816/dist.tar.gz

✅ togetherai-openapi studio · code · diff

Your SDK built successfully.
generate ⚠️

⚡ togetherai-python studio · conflict

There was a conflict between your custom code and your generated changes.
You don't need to resolve this conflict right now, but you will need to resolve it for your changes to be released to your users. Read more about why this happened here.

New diagnostics (1 note)

💡 Python/NameNotAllowed: Encountered response property `model_name` which may conflict with Pydantic properties. Renamed to `api_model_name`. Pydantic uses model_ as a protected namespace that shouldn't be used for attributes of our own API's models. To provide a different name, use a merge transform.

✅ togetherai-go studio · code · diff

Your SDK built successfully.
generate ⚠️ → lint ✅ → test ✅

go get github.com/stainless-sdks/togetherai-go@21d22a3970ee22eff6fc7f0660dd99443a27be36

✅ togetherai-terraform studio · code · diff

Your SDK built successfully.
generate ⚠️ → lint ❗ → test ❗

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-01-30 23:36:44 UTC

[blainekasten]

make sure to add required entries otherwise every key will be marked as optional

[blainekasten]

I'm surprised we don't put the model name in the url so that way we can get CDN caching on get requests to reduce load and increase speed

[blainekasten]

we should probably not put this in the spec

[blainekasten]

Why would a user ever use this?

[blainekasten]

is this the same response that is given on a normal create? If so let's not make a new schema component but reference the same one