Put production traffic on Together AI only after each model you pin has passed your own tool-calling and long-prompt tests. Match each workload to serverless, provisioned throughput or a dedicated endpoint, keep the prepaid balance funded, and settle prompt storage, passthrough and sign-in first. This checklist covers modes, models, credits, limits, data and access.
When you need this
- An app or agent built on another model API is moving open-model traffic to Together.
- A pipeline depends on one exact open model staying served on Together.
- Security asks where prompts go, how long Together keeps them, and who can sign in.
Evaluation criteria
Pick the inference mode
Serverless, provisioned throughput or a dedicated endpoint?
Look forServerless bills per input and output token with no minimum cost and is best-effort. Provisioned throughput reserves capacity for five listed models at US$0.05 per PTU per minute on a one-month minimum, through sales. Dedicated endpoints serve a model on reserved hardware billed by the minute per replica, an H100 80GB at US$5.49 per hour.
Test each model you pin
Does each model do what your app needs on Together?
Look forRun your tool definitions, structured output and longest prompts through the client you ship. Practitioners report tool calls failing on gpt-oss-120b through ChatTogether and on Qwen3-Coder-Next through LiteLLM, and a grammar error on Llama 3.3 70B. Confirm each model is in the serverless catalog.
Plan for model retirements
What happens when Together retires a model?
Look forA developer reports notice emails from Together deprecating GLM-5.1 on July 10, 2026, with no upgrade path. A models.dev issue found six models still listed as active that the serverless endpoint no longer serves. MLCommons' evaluation broke twice when annotator models left serverless. Keep a tested replacement for every pinned model, or serve it on a dedicated endpoint.
Fund credits and watch limits
Will a zero balance or a 429 stop production?
Look forAccess needs a minimum US$15 credit purchase and is suspended at zero, and the cut-off is not an exact cap. API keys have no spending limits of their own. Expect 429 or 503 responses at high demand, and retry with backoff.
Settle data handling
Where do prompts go, and does Together keep them?
Look forTogether stores prompts and responses by default, and admins turn storage off for zero data retention. Passthrough models send data to the upstream provider under its policy, behind a separate organization toggle. US-only processing covers where requests are processed, and data storage falls outside that scope.
Decide sign-in and audit
Do you need SSO, SCIM or an audit log?
Look forSSO via SAML and OIDC is available for Scale and Enterprise accounts, and SCIM is listed under What's coming. Audit and lifecycle events are listed per dedicated endpoint, so record organization changes in your own change log.
Questions to ask vendors
- Which models will production pin, and has each passed our tool-calling tests on Together this month?
- Which workloads stay on serverless, and which need provisioned throughput or a dedicated endpoint?
- Who keeps the prepaid balance funded, and what alerts us before it reaches zero?
- Is prompt storage off, and are passthrough models allowed for our data?
- Do we need a Scale or Enterprise account for SSO, and what date does Together give for SCIM?
Red flags
- A production model pinned on serverless with no tested replacement.
- Tool calls tested on another host and assumed to work on Together.
- A prepaid balance with no owner and no alert before zero.
- Prompt storage left at its default for customer data.
- A security review that expects an organization-wide audit log.
Products in this piece
Sources
- Official documentation
- 12
- Public source
- 5
- Together AI docs: Serverless overview
- Together AI docs: Serverless models
- Together AI docs: Provisioned throughput
- Together AI docs: Dedicated endpoints overview
- Together AI docs: Dedicated endpoints pricing
- Together AI docs: Billing and credits
- Together AI docs: Billing spend controls
- Together AI docs: Serverless rate limits
- Together AI docs: Privacy and security
- Together AI docs: Geo-specific inference
- Together AI docs: Single sign-on
- Together AI API reference: List endpoint events
- langchain-ai/langchain-together issue #19: gpt-oss-120b fails once tools are added (Aug 20, 2025)
- OpenHands/software-agent-sdk issue #1899: move qwen3-coder-next from together.ai to OpenRouter (Feb 4, 2026)
- earendil-works/pi issue #6132: Together.ai models to be deprecated July 10 (Jun 28, 2026)
- anomalyco/models.dev issue #3324: six Together.ai models no longer served on serverless (Jul 18, 2026)
- MLCommons, modelbench issue #1045: Find replacement for missing annotator model (May 20, 2025)