Together AI

Serverless and dedicated inference for open models with dynamic rate limits.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://docs.together.ai/docs/rate-limits

Properties · 5 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ api-key
contentFiltering	boolean	—	no	—	▸ false
customerManagedKeys	boolean	—	no	—	inherited
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
dynamicRateLimits · component property	boolean	—	no	true	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ multimodal
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
serving · component property	enum	serverless \| dedicated	no	serverless	inherited
trainingOptIn · component property	boolean	—	no	false	inherited
viaGateway	boolean	—	no	false	inherited
zeroDataRetention · component property	boolean	—	no	false	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

AI API key not managedwarning

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "together-ai", component: "together-ai" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Together AI: hosted open-model inference API (chat, image, embedding, rerank) over a public endpoint.
3# Per "Rate limits", limits are dynamic and adjust with recent usage rather than fixed per-model tiers;
4# per the Privacy Policy, prompts and completions are not used for training without explicit opt-in and
5# Zero Data Retention is an opt-in setting.
6schemaVersion: "1"
7type: "component"
8id: "together-ai"
9kind: "ai-service"
10provider: "default"
11docs: "https://docs.together.ai/docs/rate-limits"
12defaults:
13  auth: "api-key"
14  managed: true
15  modality: "multimodal"
16  publicEndpoint: true
17  contentFiltering: false
18properties:
19  serving:
20    type: "enum"
21    values: ["serverless", "dedicated"]
22    default: "serverless"
23  dynamicRateLimits:
24    type: "boolean"
25    default: true
26  zeroDataRetention:
27    type: "boolean"
28    default: false
29  trainingOptIn:
30    type: "boolean"
31    default: false

The same page as markdown, for an agent: /catalogue/components/together-ai.md