Together GPU Clusters
by Together AI HTTP API in GPU & serverless compute
Hosted
Together Computer, Inc. · together.ai · status page · who's behind it
Together GPU Clusters rents multi-node NVIDIA H100, H200, B200 and B300 clusters with InfiniBand and shared storage, run as Kubernetes or Slurm, by the GPU-hour. Clusters are created and scaled from the console, the tg CLI, SDKs or REST API.
Best for Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in GPU compute. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
More from Together AI Together AI Inference (Models) · Together AI Fine-tuning (Fine-tuning) · Together Code Sandbox (Sandboxes)
Assessment. Multi-node H100 to B300 clusters on Kubernetes or Slurm, created and deleted headlessly through an OpenAPI-described API, a CLI with JSON output and two SDKs, at published GPU-hour prices. Clusters take 10 minutes to an hour to provision, can't be paused, and have no status component, SLA or idempotent create.
Facts
Access how an agent reaches and pays for it
- Endpoint
https://api.together.ai/v1/compute/clusters- Auth
- API key
- Pricing
- Pay per use
- x402
- No
- Licence
- Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT
- Capabilities
- compute.gpu compute.containers compute.batch
Where it lives packages, source, docs and releases
- Packages
pypitogethernpmtogether-ai- llms.txt
- published
- Last release
From our research 8 facts checked against the vendor's pages
- Surface listed
- Together GPU clusters (Instant Clusters) through the REST API at api.together.ai/v1/compute/clusters, the
tg clustersCLI and the Python and TypeScript SDKs, read from docs.together.ai (overview, quickstart, concepts, management, automation, pricing, preemptible compute, API reference and changelog) and status.together.ai on 6 November 2026. No account was made and no cluster was created - Scope
- Multi-node GPU clusters for training and batch work. Serverless and dedicated inference, fine-tuning and Code Sandbox have separate Anchor Terminal listings
- Hardware
- NVIDIA HGX H100 SXM (80 GB), H200 (141 GB), B200 (180 GB) and B300, in full nodes of 8 GPUs, with 3.2 Tb/s InfiniBand, local NVMe and a shared volume of at least 1 TiB
- Cluster types
- Kubernetes, reached with kubectl, or Slurm on Kubernetes through Slinky, reached by SSH to a login node
- Capacity types
- On-demand by the hour, reserved for 3 to 180 days, scheduled windows from a project capacity pool, and preemptible nodes (preview) with a five-minute drain
- Access
- Project roles admin and editor. Only admins download the admin kubeconfig, which has cluster-admin rights. OIDC gives editors kubectl access under Kubernetes RBAC
- Health
- Active and passive health checks, with repair recommendations that can be approved by hand or run fully automatically
- Lifecycle
- Reserved clusters are decommissioned at the end of the reservation after emails 7 days, 3 days, 1 day and 4 hours before. Volumes outlive clusters and are deleted 72 hours after credit runs out
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- Public OpenAPI 3.1, llms.txt and Markdown docs, with an automation guide for CI pipelines
- Published per GPU-hour prices for on-demand, reserved and preemptible capacity, with no egress fees
- Kubernetes or Slurm on the same hardware, with InfiniBand and a persistent shared volume
- Automatic health checks and node repair, approved by hand or run automatically
- Project-scoped keys, admin-only kubeconfig and OIDC access for team members
Weaknesses
- Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero
- No status page component, SLA or published rate limits for GPU clusters
- No idempotency key on creation, so a retried create can bill a second cluster
- No free trial; reservations are prepaid and non-refundable
- Volumes bill until deleted and outlive the clusters they were attached to
Before you call it notes for agents
- Use
tg clusters, nottg beta clusters, which stopped working with CLI 3.0 on 22 October 2026 - Pass
--jsonand--non-interactive, polltg clusters retrieveuntil status is Ready, and delete the cluster in a cleanup step - Check for an existing cluster by name before retrying a create, since creation has no idempotency key
- Read live availability from the regions API and prices from the pricing page; the regions response has no prices
- Use a project admin's key when the task needs the kubeconfig, since other roles get none
Who's behind it provenance 83/100
- Legal entity namedTogether Computer, Inc.20/20
- Domain agetogether.ai, no registry record we could read0/15
- Endpoint on the vendor's domainapi.together.ai15/15
- Terms of serviceread, states 5 of the 7 things a reader expects, and has 1 clause that costs points6.3/10
- Privacy policyread, states 7 of the 8 things a reader expects9.3/10
- Status pagestatus.together.ai10/10
- Changelogpublished10/10
- security.txtvalid10/10
- People named6 named with their role, 5 with a public profile10/10
- Support routehelp pages, a community5/5
Terms and privacy, as read
Terms of service gives no date, states 5 of 7, 1 to know
TL;DR Gives no date. States 5 of the 7 things a reader expects, and we didn't find how changes are announced. To know before relying on it, limits on benchmarking.
Restricts benchmarking or competitive usecosts points
(c) use or access the Services to develop a product or service that is competitive with the Company’s products or services or engage in competitive analysis or benchmarking;
A clause against publishing test results or using the service to build something that competes.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version they agreed to.
Names the governing law or courts The law of the State of California
This Agreement will be governed by the laws of the State of California, exclusive of its rules governing choice of law and conflict of laws.
Says where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 12 months before the claim
…even if informed of their possibility in advance, or (b) excluding customer's payment obligations, any aggregate liability in excess of the amounts paid by customer during the twelve (12) months preceding the claim (the "ordinary cap").
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
The Company may suspend your access to the Services immediately upon notice if you fail to pay any amounts hereunder at least five (5) days past the applicable due date.
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced
Not found in the text.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
You will not use the Services to transmit or provide to the Company any financial or medical information of any nature or any sensitive personal data (e.g., social security numbers, driver’s license numbers, birth dates, personal bank account numbers, passport or visa numbers, and/or credit card numbers).
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
No guarantees are made with respect to the Services’ quality, stability, uptime, or reliability, unless otherwise agreed between the parties in an order form.
Says whether availability is promised and where the promise is written.
The parties owe each other no confidentiality unless they agree it in writing.
The parties will have no confidentiality obligations to each other unless otherwise agreed in writing.
Noted by a second reader on 2026-10-08.
The customer may not cancel or end the agreement without Together's express written consent.
You may not cancel or terminate this Agreement without our express written consent.
Noted by a second reader on 2026-10-08.
Customers may not send financial or medical information or sensitive personal data to Together through the services.
You will not use the Services to transmit or provide to the Company any financial or medical information of any nature or any sensitive personal data
Noted by a second reader on 2026-10-08.
The document · read 2026-10-08 · 3,964 words
Privacy policy gives no date, states 7 of 8
TL;DR Gives no date. States 7 of the 8 things a reader expects. The rules found no clause to flag.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
Data that we collect, including your Personal Data, will not be used to train the Company’s models without your explicit opt-in and consent.
The basic statement a privacy policy exists to make.
Says how long data is kept For as long as needed, with no period named
The Company will retain your Personal Data only for as long as is necessary for the purposes set out in this Policy.
Says when data sent to the service is deleted.
Says who else receives the data
We may share your Personal Data with Service Providers, Third-Party Vendors, Consultants, and other Business Partners in order to provide Services on our behalf, monitor and analyze the use of our Services, contact you, and for the reasons stated in our Terms of Service.
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising Says it does not sell personal data
The Company does not sell your Personal Data as defined under CCPA.
A plain statement either way.
Says what rights people have over their data
If, in the future, we do sell your Personal Data, we will notify you, and you may have the right to opt out of such sale.
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact privacy@together.ai
In order to exercise any other privacy rights not specifically enumerated here, you may contact privacy@together.ai.
An address or officer to send a request to.
Says where data is transferred or stored Relies on standard contractual clauses
When we share Personal Data of individuals in the EEA, Switzerland, or UK with third parties, we make use of a variety of legal mechanisms to safeguard the transfer, including the European Commission-approved standard contractual clauses as well as additional safeguards where appropriate.
The countries data goes to and the safeguard used.
Data collected from a customer is not used to train Together's models unless the customer opts in.
We do not use any data collected from you to train our models without your explicit opt-in and consent.
Noted by a second reader on 2026-10-08.
With Zero Data Retention on, Together cannot later retrieve, correct, export or delete the data, because it is removed once processing ends.
This means we cannot later access, retrieve, correct, export, or delete your Personal Data on your behalf as it is removed from our systems as soon as processing concludes.
Noted by a second reader on 2026-10-08.
The document · read 2026-10-08 · 3,751 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
Legal entity, terms, privacy and security.txt as on the Together AI Inference listing, checked 1 November 2026, and not re-read for this listing.
docs.together.ai/robots.txt disallows only /cdn-cgi/ and /_next/, with Content-Signal ai-train=yes, search=yes, ai-input=yes. www.together.ai/robots.txt allows all.
status.together.ai has no component for GPU clusters on 6 November 2026.
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
-
Vipul Ved PrakashFounder and CEO
-
Ce ZhangFounder and CTO
-
Tri DaoFounder and Chief Scientist
-
Chris RéFounder, Together AI
-
Percy LiangFounder, Together AI
-
Charles ZedlewskiChief Product Officer
Together Computer, Inc. on LinkedIn @togethercompute
Valuation $8.3B post-money, Series C, July 2026 source
Backed byLux Capital,Kleiner Perkins,NVIDIA,Emergence Capital,Salesforce,Coatue,Aramco Ventures,NEA,Greycroft,Definition Capital,Long Journey Ventures,Factory,SV Angel,First Round Capital,A Capital,Robot Ventures,Common Metal,Susa Ventures,Cadenza Ventures,SCB 10x,Scott Banister,Jeff Hammerbacher,Dawn Song,Alex Atallah,MC Lader,Lip-Bu Tan,Jakob Uszkoreit,Marc Bhargava,Jennifer Campbell,Chafic Kazoun,Sabrina Hahn,SongYee Yoon,Chase Lochmiller,Yi Sun,Dave Eisenberg,Panos Madamopoulos-Moraris,Zach Frankel,Clem Delangue,Soumith Chintala,General Catalyst,DAMAC,March Capital,Schneider Electric,Brave Capital,SK Telecom,John Chambers,Vista Equity Partners,Pegatron,DTCP,Geodesic Capital,PSP Partners,SentinelOne
Researched 6 November 2026 from public pages. From the Our team section of Together AI's about page (read on 28 October 2026), which shows each person in a card with name, title, portrait and their own LinkedIn and X links. It lists five founders (Vipul Ved Prakash as Founder and CEO, Ce Zhang as Founder and CTO, Tri Dao as Founder and Chief Scientist, Chris Ré and Percy Liang as Founder) and Charles Zedlewski as Chief Product Officer, followed by other executives and vice presidents. Copied from the Together AI Inference listing (checked 28 October 2026) for this listing on 6 November 2026; nothing newer was looked for beyond the docs read. On 6 November 2026 the Series C post and Latham & Watkins' note were reread for a cumulative total; neither states how much Together AI has raised in all, so totalRaised is left out rather than summed from the rounds. A TechCrunch report on the Series C was dropped from the sources, as techcrunch.com's robots.txt is off limits; the valuation stays sourced to Latham & Watkins. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Sources (11)
Live watched around the clock · updated 2026-11-07 17:38 UTC
Probed every five minutes at https://api.together.ai/v1/compute/clusters. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials. Last note, asks for credentials.
- github
togethercomputer/together-pyv3.1.1, released 2026-11-04 - npm
together-ai1.0.0 - pypi
together3.1.1, released 2026-11-04 - GitHub stars 12
- npm downloads a week 100k
- PyPI downloads a week 425k
- security.txt valid, expires 2028-09-30T00:00:00.000Z · 1 hour ago
- llms.txt answers · 2 hours ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/together-gpu-clusters.json
Notable
- Together CLI 3.0 and Python SDK 3.0 on 22 October 2026 moved GPU clusters out of
beta(tg clusters,client.clusters), and the oldtg beta clusterspaths stopped working, with a migration guide source - Instant clusters became generally available on 9 September 2025, per the changelog source
- Provisioning usually takes 10 minutes to an hour, depending on size and region, per the quickstart source
- A cluster can't be paused. On-demand clusters bill until deleted, volumes bill until deleted, and when credit runs out an on-demand cluster is paused at once and deleted after a one-hour grace period source
- The automation guide shows a GitHub Actions job that creates an on-demand cluster with
--json, polls for Ready, runs a Kubernetes job and deletes the cluster with--non-interactivesource - status.together.ai lists the website, playground and serverless models, with no component for GPU clusters source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Together GPU Clusters, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Together GPU Clusters, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 7.6 | |
Read with the hosted lines. status.together.ai lists the website, the playground and serverless models with no component for GPU clusters, and a vendor page with no component for the product takes 15 in this run, as for Together's Code Sandbox and fine-tuning listings (15). No incident history for clusters can be read (5). No rate limits for the clusters API found (0). Together's docs give 429 and 503 backoff guidance for its APIs, per the inference listing's 1 November check, and the CLI has --non-interactive and --json for scripted retries, but creation has no idempotency key (8). No SLA for clusters found; the published 99% commitment covers provisioned inference throughput only (0). Generally available since 9 September 2025 and out of the CLI's beta paths since 22 October 2026, with preemptible nodes in preview (10). 15+5+0+8+0+10 = 38. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 14.9 | |
| Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92. | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 8.9 | |
Cluster objects are compact, and --json gives machine-readable output, but list calls take no field selection (15). No pagination or filters on the clusters list (8). 402 and 403 with readable messages such as "Insufficient credits for cluster creation", and troubleshooting for common failures (12). Status polling until Ready is documented and deletes run non-interactively, but there is no idempotency key on creation and a duplicate create bills a second cluster (8). Official Python and TypeScript SDKs and a CLI, though a create takes GPU type, region, driver and CUDA versions, cluster type and billing type (12). 15+8+12+8+12 = 55. | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 11.9 | |
Project-scoped API keys, revocable with optional expiry, read as Together's other listings read the same key model (30). Admin and editor roles with no read-only role. Only admins get the admin kubeconfig, which has cluster-admin rights, and OIDC lets editors use kubectl under RBAC. Deletes run without confirmation when --non-interactive is passed (8). The API returns cluster state, not third-party content (10). Invoices itemise reserved, on-demand and storage charges, and no audit log for cluster operations was found (5). security.txt with a HackerOne route, per the 1 November check of the inference listing (15). 30+8+10+5+15 = 68. | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 2.5 | |
| No machine payment protocol (0). Per GPU-hour prices for each capacity type and per GiB-month storage published without a login (20). No free trial, and creation needs credit for the full reservation or a minimum on-demand period (0). Sign-up and credit purchase are browser steps (0). 0+20+0+0 = 20. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 6.6 | |
| Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75. | |||
| Transparency & trusteditorial 46, provenance 83checked 6 November 2026 | 7%8.8 | 5.7 | |
| Closed service under Together's terms, with Apache-2.0 SDKs, which don't raise the line for a closed API (15). The privacy policy's data table covers GPU clusters, per the 4 November Code Sandbox check, and the billing page states when volumes are deleted after credit runs out, with no retention period for data on deleted clusters (15). The 3.0 breaking change came with a migration guide on the day, and reservations carry dated end-of-term emails, with no notice period for API changes found (8). Regions are listed through the API and US regions appear in examples; subprocessors and data locations for clusters were not established (8). 15+15+8+8 = 46. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 58.1 · C | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 58.1 C methodology v0.7
Fix list 14 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Together GPU Clusters. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: rate limits and 429 behaviour on the clusters API, which the reviewed pages don't state
- unchecked: whether the SLA language in Together's terms covers GPU clusters
- Together's terms, privacy policy and security.txt were not re-read for this listing; the provenance follows the Together AI Inference check of 1 November 2026
- GitHub's API was rate-limited during this run, so SDK stars and CI status were not read
Sources 12
- GPU clusters overview docs.together.ai · seen 2026-11-06
- GPU clusters pricing docs.together.ai · seen 2026-11-06
- manage GPU clusters docs.together.ai · seen 2026-11-06
- automate cluster operations docs.together.ai · seen 2026-11-06
- quickstart docs.together.ai · seen 2026-11-06
- concepts docs.together.ai · seen 2026-11-06
- preemptible compute docs.together.ai · seen 2026-11-06
- create cluster API reference with OpenAPI docs.together.ai · seen 2026-11-06
- list clusters API reference docs.together.ai · seen 2026-11-06
- changelog docs.together.ai · seen 2026-11-06
- status page status.together.ai · seen 2026-11-06
- llms.txt docs.together.ai · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Pay per use Pay per use On-demand from $3.99 per GPU-hour (H100) to $9.99 (B300); reserved 3 to 180 days from $3.19 to $7.99; preemptible (preview) from $1.99. Storage per GiB-month. No ingress or egress fees. Reservations are prepaid and non-refundable, and creation needs enough credit to cover them.
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| H100 on-demand | $3.99 | per GPU-hour | reserved $3.69 to $3.19, preemptible $1.99 |
| H200 on-demand | $5.99 | per GPU-hour | reserved $4.99 to $3.99, preemptible $2.99 |
| B200 on-demand | $8.19 | per GPU-hour | reserved $7.99 to $6.79, preemptible $4.09 |
| B300 on-demand | $9.99 | per GPU-hour | preemptible $4.99, reserved by sales |
Compared across listings on the price index.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/together-gpu-clusters.xml, or this listing's score history at history.json.
Connect
Install
uv tool install "together[cli]"First request
curl -H "Authorization: Bearer $TOGETHER_API_KEY" https://api.together.ai/v1/compute/clustersThrough letme picks today, calling later
GET https://letme.dev/together-gpu-clustersletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Together GPU Clusters
#10 of 22 in Best GPU and serverless compute for AI workloads · All 231 gpu compute comparisons
Nebius AI Cloud BBCloud Run GPUs BModal BCrusoe Cloud BCoreWeave CBeam C
Head to head Baseten vs Together GPU Clusters · Beam vs Together GPU Clusters · Cerebrium vs Together GPU Clusters · Cloud Run GPUs vs Together GPU Clusters · CoreWeave vs Together GPU Clusters · Crusoe Cloud vs Together GPU Clusters · GPUsMarket vs Together GPU Clusters · Hugging Face Inference Endpoints vs Together GPU Clusters · Hyperbolic vs Together GPU Clusters · Koyeb vs Together GPU Clusters · Lambda Cloud vs Together GPU Clusters · Massed Compute vs Together GPU Clusters · Modal vs Together GPU Clusters · Nebius AI Cloud vs Together GPU Clusters · Northflank vs Together GPU Clusters · Replicate Deployments vs Together GPU Clusters · Runpod vs Together GPU Clusters · Thunder Compute vs Together GPU Clusters · Together GPU Clusters vs Vast.ai · Together GPU Clusters vs Verda
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Nebius AI Cloud Nebius | BB | 71.2 | compute.gpu compute.batch compute.containers | no |
| Cloud Run GPUs Google Cloud | B | 68.4 | compute.gpu compute.containers compute.batch | no |
| Modal Modal | B | 62.7 | compute.gpu compute.batch compute.containers | no |
| Crusoe Cloud Crusoe | B | 62.4 | compute.gpu compute.containers compute.batch | no |
| CoreWeave CoreWeave, Inc. | C | 60.5 | compute.gpu compute.containers compute.batch | no |
| Beam Beam | C | 56.2 | compute.gpu compute.batch compute.containers | no |
Machine-readable
- JSON
/api/v1/tools/together-gpu-clusters.json· historyhistory.json· badge/badges/together-gpu-clusters.svg· changes feed/feeds/tools/together-gpu-clusters.xml - Markdown
/tools/together-gpu-clusters.md· slim/tools/together-gpu-clusters.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/together-gpu-clusters.md·/fixes/together-gpu-clusters.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool together-gpu-clusters --md(the CLI) · over MCPget_tool {"slug": "together-gpu-clusters"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT together-gpu-clusters.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/together-gpu-clusters"><img src="https://www.anchorterminal.com/badges/together-gpu-clusters.svg" alt="Together GPU Clusters on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/together-gpu-clusters)<a href="https://www.anchorterminal.com/tools/together-gpu-clusters">Together GPU Clusters on Anchor Terminal</a>It counts on a page on together.ai or one of its subdomains, or the README at the root of github.com/togethercomputer/together-py.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "together-gpu-clusters", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Together GPU Clusters is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/together-gpu-clusters. The logo is the one on this listing. If it's wrong or out of date, send us the right one.