Alpha
Contact
Implement · Together AI

Can you run it?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input C ยท 69.6/100

This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

API integration

Together's docs describe an OpenAI-compatible REST API at api.together.ai/v1 with Python and TypeScript SDKs, covering chat, completions, vision, image generation, text-to-speech and speech-to-text. An existing OpenAI client integrates by changing the base URL and API key. Model ids are namespaced (openai/gpt-oss-120b), so bare OpenAI model names return a 404. Embeddings are dedicated-only and moderations.create returns 404; there is no serverless embedding model. A Messages API and a Responses API are also listed.

Authentication & account setup

Authentication uses a bearer API key (TOGETHER_API_KEY). Organisation admins control three privacy toggles (Prompt storage, Passthrough models, Model training) in Organization Settings, and the docs list roles and permissions (RBAC) and single sign-on under administration. No key-rotation or project-scoping detail is stated. An organisation on the Limited tier must add a payment method before changing the privacy settings.

Region & ZDR configuration

ZDR is not the default. An organisation admin turns off Prompt storage in the Privacy section of Organization Settings. That also disables passthrough models, and it applies only to later requests. For US-only processing send requests to us-api.together.ai (1.25x rates, 8 models). A model that is not available there fails with 404 region_unavailable and does not fall back, so do not retry against api.together.ai. EU residency is not self-serve: it needs a dedicated endpoint or VPC deployment arranged with sales.

Rate limits, tiers & quotas

Serverless is best-effort: under high demand you may see 429 or 503, and the docs advise exponential backoff. Together may apply model-specific limits or access restrictions to models in high demand. Purchased limits on legacy Enterprise and Scale contracts stay until the contract expires. Committed throughput and a defined SLA come from provisioned throughput through sales. Numeric per-tier limits are not stated.

Portability & exit

Together speaks the OpenAI-compatible API over portable open-weight checkpoints, and third-party analysis lists the same models across many providers, so exit is a base-URL change plus output re-validation. With ZDR on, no prompt history is kept. Files you uploaded for fine-tuning or batch jobs stay stored until you delete them through the API, CLI or console.

How this scores

The ownership factors this domain covers, drawn from the one entry record.

3

ReliabilityDoes it stay up and stay secure?

Moderate

A public status page shows per-model 90-day uptime of 99.28% to 100%, and SOC 2 Type II and ISO 27001:2022 are announced. The terms disclaim uptime, serverless is best-effort, and the only SLA is sales-only provisioned throughput.

How this scores (AOI sub-dimensions)
Reliability3/5whether it stays up, with an SLA and status historyA public status page exists at status.together.ai (ev-status).
Security4/5the controls protecting your traffic and dataThe DPA Annex 2 (ev9) commits to a written security programme, MFA for remote access, and encryption in transit and storage.
Compliance4/5which independent certifications and attestations it holdsSOC 2 Type II (ev3) and ISO 27001:2022 from A-LIGN, an ANAB-accredited body (ev-iso), are both vendor announcements of independent audits.
4

Doesn't extract your dataDo the binding terms keep your data and IP yours?

Moderate

You own Your Content and Output and training is opt-in. Prompt storage is on by default and Together may use stored prompts for product improvements, and ZDR is an admin opt-in. Passthrough models send prompts to third parties by default, ToS Sec 9 disclaims confidentiality, and US HQ carries standing CLOUD Act exposure.

How this scores (AOI sub-dimensions)
Data governance3/5retention, training-on-inputs and data ownershipHeld at 3 by the confidentiality cap, and the posture earns a 3 on the merits.
Residency3/5where your data is processed and storedScore 3.
What this means for adoptionYou own your inputs and outputs under the Terms, training is opt-in, and the open-weight catalogue on an OpenAI-compatible API gives a clean portable exit. Ownership is partial. By default Together stores your prompts and may use them for product improvements, and zero data retention is an admin opt-in. Passthrough models send prompts to third parties until you switch them off, and the Terms disclaim any duty of confidence. Residency is US-only on serverless, with EU limited to sales-led dedicated deployments. Turn prompt storage off for ZDR, negotiate confidentiality and EU terms in an enterprise contract, and do not rely on the default terms for trade secrets or regulated data.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Privacy Policyread2026-11-19
Privacy Policy (updated 2025-12-17).
Documentationread2026-11-19
Privacy and security docs: see ev-docs for the default-storage, passthrough and ZDR clauses.
Vendor announcementread2026-11-19
SOC 2 Type II announcement (published 2025-07-08): completed via an independent multi-month audit, auditor not named; HIPAA adherence and business associate agreements stated.
Documentationread2026-11-19
Support knowledge base article, "Last updated 1 year ago": EU data centres exist, and dedicated endpoints on targeted data centres including EU locations are available only on Scale and Enterprise tier plans.
Vendor announcementread2026-11-19
Pricing page: serverless per-token rates with cached-input prices for 24 chat models plus vision, image, video and audio models; on-demand dedicated GPU endpoints (H100 $5.49 per GPU hour); GPU clusters; fine-tuning; provisioned throughput via sales; promotions with end dates.
Documentationread2026-11-19
OpenAI-compatibility docs: an OpenAI-compatible REST API and SDKs across chat, completions, vision, image generation, text-to-speech and speech-to-text, used by pointing an OpenAI client at Together's base URL.
Terms of serviceread2026-11-19
Terms of Service (updated 2026-05-19).
Third-party analysisread2026-11-19
Artificial Analysis provider page: independent third-party analysis of 18 Together AI models by intelligence, speed and price (Kimi K3.1 Pro ranked first), showing the same open-weight models compared across providers.
Data Processing Addendumread2026-11-19
Data Processing Addendum PDF (no effective date on the PDF): Together (US) Inc.; EU SCCs and UK Addendum; the conflict clause prefers the DPA for personal data it covers; 24-hour breach notice (Annex says 48).
Documentationread2026-11-19
Privacy and security and zero-data-retention docs.
Documentationread2026-11-19
Geo-specific inference docs: only a United States endpoint (us-api.together.ai, 1.25x standard rates, 8 models) keeps inference processing in the US.
Vendor announcementread2026-11-19
ISO 27001:2022 blog (published 2026-06-10): Together AI "has received an ISO 27001:2022 certification from A-LIGN Compliance and Security, Inc., an ANAB-accredited certification body", scoped to the ISMS for the global platform including third-party data centres.
Slaread2026-11-19
Public status page (rendered page, index.json and feed): "All services are online".
Securityunverified2026-11-19
Trust centre (trust.together.ai): a Vanta single-page app shell of about 7.9 KB with no readable content.