Head to head · Fine-tuning · October 2026 research run

Tinker vs Together AI Fine-tuning

Together AI Fine-tuning scores 55 (C) on agent readiness against Tinker's 53.7 (D), and leads in 3 of 7 scored categories. Tinker leads on agent ergonomics and maintenance & community. Both do fine-tuning.

Best fine-tuning services for AI models · All 36 fine-tuning comparisons

Which one, for what

Tinker D

Best for Researchers and teams writing custom post-training loops, especially RL, who want per-token billing and the weights at the end.

Ahead on

  • Agent ergonomics, 53 against 42
  • Maintenance & community, 87 against 80

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Together AI Fine-tuning loses 3 points for them

Watch for

LoRA only; no full-parameter training

Together AI Fine-tuning C

Best for Teams that want to tune a large open model, possibly with full fine-tuning, and take the weights away.

Ahead on

  • Reliability, 55 against 35
  • Schema & documentation, 83 against 70
  • Transparency & trust, 68 against 62

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Fine-tuned models don't run serverless; dedicated endpoints start at $5.49 an hour

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Together AI Fine-tuning +20

Tinker 35

The listing's kind is sdk, but the SDK is a thin client for a hosted training service, so the hosted checklist is kept as on 1 October; that's a judgement call. No status page found, on the vendor's pages read on 1 October or by search on 4 November (0), and so no readable incident history (5). The only published limit is the in-flight sample cap of 2,000, per the 1 October check, not re-read on 4 November (10). The SDK's retry handler retries sampling with stable request IDs, confirmed in the SDK repository, and the docs' guide on client-side retries is per the 1 October check (15). No SLA found (0). Sign-up is open and paid, but the cookbook README still says 'after our private beta is over' on 4 November, and no GA statement was found (5).

Together AI Fine-tuning 55

Better Stack status page at status.together.ai with component history for the website, the playground and each serverless model, but no component for fine-tuning jobs. A vendor page with no component for the product takes 15 in this run (15). Read on 4 November, its feed posts no incident since January 2025 (the newest items are maintenance on 21 April and 2 July 2026), and the monitors record downtime on single serverless models only. Fine-tuning jobs don't run on those models, and a page that has posted no incident in 22 months while its monitors show downtime isn't shown to post incidents, so the window isn't credited as clean. The 1 October 20 is kept, the value for a page that doesn't post incidents (20). The rate-limit page gives no numbers, and the dynamic serverless limits the 1 October note leaned on were retired on 2 October 2026. No limits for fine-tuning calls found (0). The docs say to reduce the rate and use exponential backoff on 429 and to retry 503 with backoff, with no idempotency key or safe-retry guidance for job creation (10). No SLA found for fine-tuning (0). Fine-tuning carries no beta label (10). 15 + 20 + 0 + 10 + 0 + 10 = 55.

Schema & documentation Together AI Fine-tuning +13

Tinker 70

No REST reference or OpenAPI. The contract is the typed Python SDK, whose API reference ships in the SDK repository's docs folder (15). llms.txt, llms-full.txt, models.json and serverless.json per the 1 October check, not re-read on 4 November, since the docs host is paused on its terms (10). Reference pages for ServiceClient, TrainingClient, SamplingClient and RestClient and an SDK cheatsheet (12). Typed parameter objects and bounded checkpoint TTLs (10). The cookbook's recipes are the examples; no page of error types found (8). Semver 0.x releases with a dated changelog that names removals, per the 1 October check (15).

Together AI Fine-tuning 83

A public OpenAPI 3.1.0 file at docs.together.ai/openapi.yaml ('Together APIs' 2.0.0), read in full on 4 November, has 12 fine-tuning paths under /v1/fine-tunes and /v1/finetune/download with typed schemas (25). llms.txt with .md twins (10). Field descriptions say what a field does and sometimes the trade-off ('may improve results but increase cost and risk of overfitting'), rarely when to use it (12). Two required fields, enums for training_type, training_method and the scheduler, defaults and limits such as n_checkpoints up to 10 and suffix up to 64 characters (13). Python, TypeScript, JavaScript and curl examples on each call. The error code page covers inference only, and in the OpenAPI file job creation lists only 200 and 503 while preview, cancel, delete, download and metrics list some 4xx answers, so the partial value is kept (8). Versioned /v1 paths and a dated changelog with 44 entry days from 6 August to 3 November 2026 (15). 25 + 10 + 12 + 13 + 8 + 15 = 83.

Agent ergonomics Tinker +11

Tinker 53

Sampling takes token limits and logprob options, so responses can be sized; no field selection (15). RestClient filters training runs by project_id since 0.22.6, and the console filters sessions by status (10). No documented error codes found (5). Stable request IDs make SDK retries of sampling safe; nothing on retrying an optim_step (15). A LoRA client needs only a base model and a rank, but the SDK is Python only (8).

Together AI Fine-tuning 42

GET /v1/fine-tunes returns truncated job objects, with no limit or field selection (10). The OpenAPI file lists no query parameters on the list call, so no pagination or filters (0). An error page maps 11 status codes to a cause and a fix, scoped to inference; fine-tuning errors aren't listed (12). No idempotency keys or client-chosen job IDs; the docs advise trying 5xx again after a short wait (5). Only model and training_file are required, defaults are documented, and official SDKs exist for Python and TypeScript plus the tg CLI (15). We didn't score POST /v1/fine-tunes/estimate-price, a dry-run quote the checklist has no line for, though it saves an agent a failed or overpriced job.

Maintenance & community Tinker +7

Tinker 87

tinker-cookbook v0.5.9 tagged on 27 October 2026, 8 days before this check. The SDK repository's newest version bump is 0.37.0 on 2 November, untagged, so it isn't counted (30). Cookbook tags v0.5.4 (11 August), v0.5.5 (19 August), v0.5.6 (1 September), v0.5.7 (3 September), v0.5.8 (21 October) and v0.5.9 (27 October) in the 90 days from 6 August (20). The cookbook had 22 open issues and 55 open pull requests on 1 October and its README defers outside PRs until the private beta ends; GitHub's pages refuse us, so not re-read (12). The SDK is current (15). The cookbook runs pytest on push and pull request, plus pyright, recipe smoke tests and a security workflow (10).

Together AI Fine-tuning 80

Together Python SDK v3.0.0 of 22 October 2026 changed fine-tuning code, and the newest fine-tuning changelog entry is 13 October (lower batch size for Qwen 27B full fine-tuning) (30). From 6 August, 20 changelog sections across 14 entry days name fine-tuning, and 8 together-py tags (v2.30.0 on 7 August to v3.0.0) touch its fine-tuning modules (20). Public changelog and support channels; the SDK issue tracker wasn't read (github.com answers 403, clone only), so no evidence of replies either way (10). Python (together 3.x) and TypeScript (together-ai 1.0) SDKs are current (15). We didn't confirm CI results on together-py (5). 30 + 20 + 10 + 15 + 5 = 80.

Transparency & trust Together AI Fine-tuning +6

Tinker 62

The SDK and the cookbook are Apache-2.0, and the hosted service has Service Terms of Use, last updated 10 January 2026, at thinkingmachines.ai/legal/terms/, which the 1 October check didn't find. Closed service with clear terms (15, up from 5). The terms commit not to use Customer Content for model training or fine-tuning, keep it only as needed for the service, and carry a DPA with deletion on request. Checkpoints carry user-set TTLs. The privacy notice moved to /legal/privacy/ and wasn't re-read (15, up from 8). A model deprecations page lists dated retirements and promises to 'aim to give advance notice' by email, per the 1 October check. Dated notices with no stated notice period, up from 12 (15). The DPA's Annex 2 names Google Cloud, Cloudflare, WorkOS and OpenAI with their service and location, mostly 'Global' (15, up from 5). 15 + 15 + 15 + 15 = 60.

Together AI Fine-tuning 68

Closed service under terms (19 May 2026) that name Together Computer, Inc., a Delaware corporation; SDKs are Apache-2.0. The checklist gives 15 to a closed service with clear terms, and open SDKs on a closed API don't raise it, as together-inference's 1 November check and anthropic-api read the same evidence (15). The privacy policy (2025-12-17) says no training on customer data without opt-in and the docs agree, but the docs also say prompts and responses are stored by default unless storage or ZDR is turned off, and no retention period for training files or tuned weights found (18). The deprecations page keeps a dated history of models removed from fine-tuning, and its lifecycle policy states notice periods for serverless and dedicated endpoints but none for fine-tuning. Dated notices with no period for the product give 15 in this run (15). EU-region and VPC options for enterprises are mentioned; no subprocessor list found (5). 15 + 18 + 15 + 5 = 53.

Score by category

CategoryWeightTinkerTogether AI Fine-tuningEdge
Reliability16%3555Together AI Fine-tuning +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7083Together AI Fine-tuning +13
Agent ergonomics13%5342Tinker +11
Security & auth14%5757even
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8780Tinker +7
Transparency & trust7%6268Together AI Fine-tuning +6
Negative events≤150-3
TotalD 53.7/100C 55/100

Facts side by side

FactTinkerTogether AI Fine-tuning
KindSDK + MCPHTTP API
VendorThinking Machines LabTogether AI
Hosted endpointno (local only)https://api.together.ai/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
Price for fine-tuningnot published$0.34 per 1M tokens
x402nono
LicenceApache-2.0 (cookbook)Apache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-10-22
Terms last updatednot read yetno date given
Privacy policy last updatednot read yetno date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity4k stars, 331k PyPI/wk10 stars, 118k npm/wk, 369k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Tinker higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Tinker

Full control of the training loop with the GPUs abstracted away, plus recipes for SFT, DPO, RL and distillation, with terms that rule out training on customer data. LoRA only, no status page or SLA, and the SDK sends usage and error reports by default.

Together AI Fine-tuning

31 tunable base models, 11 or 12 of them with full fine-tuning as well as LoRA, and weights can be downloaded at any saved checkpoint. Fine-tuned models don't run serverless; dedicated endpoints start at $5.49 an hour. Over 100 base models were removed from fine-tuning on 29 July 2026 with notice posted only that day.

Before you call either

Tinker

  1. Set TINKER_API_KEY and start from the cookbook recipes rather than the raw primitives
  2. Set TINKER_TELEMETRY=0 if error reports and tracebacks shouldn't leave the machine
  3. Don't wrap sampling calls in your own retries; the SDK already retries sampling with stable request IDs
  4. Save intermediate checkpoints with a TTL between 1 hour and 10 years; storage bills at $0.10 a GB-month until they expire
  5. Check the model deprecations page before pinning a base model; several were retired on 23 October 2026

Together AI Fine-tuning

  1. Call POST /v1/fine-tunes/estimate-price with the same body before creating the job, and check the model's minimum charge
  2. Read lora_training.max_rank from the model limits response before setting lora_r; most models went to 128 on 2026-09-29
  3. Don't retry a create call blindly after a timeout; there's no idempotency key, so list jobs and check first
  4. Download with checkpoint=adapter if you'll merge locally; merged weights for a 70B model are a large stream
  5. Tear down the dedicated endpoint once evaluation ends, since it bills while idle

Questions

Which is better for AI agents, Tinker or Together AI Fine-tuning?

Together AI Fine-tuning scores 55 (C) on agent readiness against Tinker's 53.7 (D), and leads in 3 of 7 scored categories. Tinker leads on agent ergonomics and maintenance & community.

Can an agent call Tinker and Together AI Fine-tuning without installing anything?

No hosted endpoint is listed for Tinker. Together AI Fine-tuning has a hosted endpoint at https://api.together.ai/v1.

Are Tinker and Together AI Fine-tuning open source?

Tinker is open source (Apache-2.0 (cookbook)). No open-source release is listed for Together AI Fine-tuning.

Other comparisons with Tinker or Together AI Fine-tuning

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.