Skip to content

DX-596-together-chat-completions: sync with mintlify-docs#927 #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zainhas merged 1 commit into from
Jul 10, 2026
Merged

DX-596-together-chat-completions: sync with mintlify-docs#927 #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions skills/together-chat-completions/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ clearly offline batch processing, vector retrieval, model training, or infrastru
- Use `together-fine-tuning` when the user wants to train or adapt a model
- Use `together-dedicated-endpoints` when the user needs always-on single-tenant hosting
- Use `together-dedicated-containers` or `together-gpu-clusters` for custom infrastructure
- For production stock-model workloads that need a defined SLA (committed throughput and reliability) without managing hardware, point users to Together's [provisioned throughput](https://docs.together.ai/docs/inference/provisioned-throughput) tier (reserved PTU capacity, one-month minimum term, contact sales; uses the same chat/completions API surface)

## Quick Routing

Expand Down
2 changes: 1 addition & 1 deletion skills/together-chat-completions/references/api-parameters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -389,7 +389,7 @@ Best practices:
- plan against the latest headers instead of a hard-coded RPM table
- keep traffic steady instead of bursty
- use batch inference for high-volume offline jobs
- use dedicated endpoints for strict capacity or SLA requirements
- for strict capacity or SLA requirements, use provisioned throughput (reserved capacity on supported stock models with a defined throughput and reliability SLA, contact sales) or dedicated endpoints (single-tenant GPUs, self-serve)

## Debug Mode

Expand Down
Loading