# GPUsMarket vs Together GPU Clusters

> Together GPU Clusters scores 58.1 (C) to GPUsMarket's 39.6 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters
- Markdown: https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md (~4,850 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Together GPU Clusters scores 58.1 (C) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. GPUsMarket leads on payments & pricing. Both do gpu compute.

- GPUsMarket: grade E, 39.6/100, rank #1318 of 1486. Markdown https://www.anchorterminal.com/tools/gpusmarket.md · JSON https://www.anchorterminal.com/api/v1/tools/gpusmarket.json
- Together GPU Clusters: grade C, 58.1/100, rank #764 of 1486. Markdown https://www.anchorterminal.com/tools/together-gpu-clusters.md · JSON https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json
- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md
- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md

## Which one, for what

### GPUsMarket (E)

Good for: Cheap, short GPU rentals for open models behind an Ollama or OpenAI endpoint, where data sensitivity is low.

Ahead on:
- Payments & pricing, 30 against 20

Also in its favour:
- Runs on your own machine

Watch for: Peer rentals send prompts and outputs through individuals' hardware, with only the terms as protection

### Together GPU Clusters (C)

Good for: Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.

Ahead on:
- Reliability, 38 against 33
- Schema & documentation, 92 against 52
- Agent ergonomics, 55 against 50
- Security & auth, 68 against 30
- Maintenance & community, 75 against 69
- Transparency & trust, 65 against 50

Also in its favour:
- No incidents deducted, where GPUsMarket loses 3 points for them

Watch for: Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero


## Why the edge

### Schema & documentation: Together GPU Clusters +40

- GPUsMarket (52): API and MCP reading. No OpenAPI or other machine-readable contract was found, and the MCP tool schemas couldn't be read because the published package is obfuscated; the repository's history says 2.4.7 added output schemas to all 32 tools, which is the vendor's claim (8). llms.txt as a complete API reference (10). llms.txt says when to use peer or cloud rentals, the proxy or the relay, and which workload each listing type serves (12). Parameters are listed by name without types, enums or required markers, apart from instance and workload types (6). curl examples for each flow, an error code list and a sample deploy response (11). npm versions, but no public changelog (5). 8+10+12+6+11+5 = 52.
- Together GPU Clusters (92): 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.

### Security & auth: Together GPU Clusters +38

- GPUsMarket (30): Account keys are all-powerful within the account, with no scopes, expiry or rotation documented, but each rental gets its own proxy token (15). The per-rental token limits inference access to one rental; no read-only key or confirmation for destructive calls (6). Peer rentals send prompts and outputs through individuals' machines, protected only by the terms, with no prompt-injection or untrusted-host guidance (2). Per-rental usage stats of requests, tokens and cost (5). No security.txt, disclosure policy, bug bounty or certification; a DPO address for breaches. The CLI and host packages are obfuscated, so they can't be audited (2). 15+6+2+5+2 = 30.
- Together GPU Clusters (68): 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.

### Transparency & trust: Together GPU Clusters +15

- GPUsMarket (50): Closed, under Tyga.Cloud licences that are clear on use, but the docs call gpusmarket-host MIT open source while the package says otherwise (10). The privacy policy gives retention periods and names Stripe and MongoDB, while renter data on peer hosts falls outside its controls, which the terms disclaim (15). The terms promise 30 days' notice of material changes, with no deprecation policy or dated notices found (5). Processors partly named, with transfers under SCCs, and no host locations shown in the docs read (6). 10+15+5+6 = 36.
- Together GPU Clusters (65): 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.

### Payments & pricing: GPUsMarket +10

- GPUsMarket (30): No x402, MPP or L402 (0). Hourly prices for every listing and GPU type are public through the unauthenticated search and types endpoints, with a $0.50 minimum (20). No free tier; a card hold is placed on every rental (0). Sign-up and key issue are one API call with no browser, but renting needs a saved, verified card, which the docs don't show being added without a person (10). 0+20+0+10 = 30.
- Together GPU Clusters (20): 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.

### Maintenance & community: Together GPU Clusters +6

- GPUsMarket (69): gpusmarket 2.5.1 on 16 October 2026, 21 days before this check (30). Releases 2.4.18 to 2.5.1 between 17 August and 16 October, and gpusmarket-host 1.5.3 and 1.6.0 (20). Support by chat widget; the repository, which holds only a README, server.json and a licence, has no open issues and one star (5). Published in the official MCP registry under the verified io.github.jyswee namespace, though the newest registry version, 2.4.16, trails npm (12). No dependencies, but an obfuscated build and no public CI (2). 30+20+5+12+2 = 69.
- Together GPU Clusters (75): 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.

### Reliability: Together GPU Clusters +5

- GPUsMarket (33): Read with the hosted lines. No status page found; listing health is shown per listing only (0). No incident history to read (5). Rate limits published, 60 requests a minute per rental and 10 sign-ups an hour per IP (15). 429 is documented, but no Retry-After, backoff or idempotency guidance (3). The terms give no availability guarantee and put host outages on hosts (0). No beta label on the API (10). 0+5+15+3+0+10 = 33.
- Together GPU Clusters (38): 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.

## Score by category

| Category | Weight | GPUsMarket | Together GPU Clusters | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 33 | 38 | Together GPU Clusters +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 52 | 92 | Together GPU Clusters +40 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 55 | Together GPU Clusters +5 |
| Security & auth | 14% (17.5 this run) | 30 | 68 | Together GPU Clusters +38 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | GPUsMarket +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 69 | 75 | Together GPU Clusters +6 |
| Transparency & trust | 7% (8.8 this run) | 50 | 65 | Together GPU Clusters +15 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **39.6 · E** | **58.1 · C** | |

## Facts side by side

| Fact | GPUsMarket | Together GPU Clusters |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Tyga.Cloud Ltd | Together AI |
| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://api.together.ai/v1/compute/clusters` |
| Transports | stdio, SSE (legacy) |  |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |
| Tools exposed | 32 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.jyswee/gpusmarket` | not listed |
| Last release | 2026-10-16 | 2026-10-22 |
| Terms last updated | 2026-06-01 | no date given |
| Privacy policy last updated | 2026-03-01 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 1 stars, 79 npm/wk | none |

## Verdicts

**GPUsMarket.** An agent can sign up with one API call, search priced GPUs without a key, rent a peer or cloud GPU as an Ollama or OpenAI-compatible endpoint and stop it, billed per second. Prompts on peer rentals pass through individuals' machines, the CLI is obfuscated, and there is no status page, security policy or free tier.

**Together GPU Clusters.** 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.

## Before you call either

### GPUsMarket

1. Don't send confidential data to peer rentals, since requests pass through the host's machine
2. Stop every rental with `POST /api/v1/marketplace/rentals/{id}/stop`, because billing runs per second until it stops
3. Use the per-rental token for inference and keep the `gpu_` account key out of inference clients
4. Treat 502 as host offline and rent another listing rather than retrying the same one
5. Ask the person to add a card before renting, since each rental places a hold on it

### Together GPU Clusters

1. Use `tg clusters`, not `tg beta clusters`, which stopped working with CLI 3.0 on 22 October 2026
2. Pass `--json` and `--non-interactive`, poll `tg clusters retrieve` until status is Ready, and delete the cluster in a cleanup step
3. Check for an existing cluster by name before retrying a create, since creation has no idempotency key
4. Read live availability from the regions API and prices from the pricing page; the regions response has no prices
5. Use a project admin's key when the task needs the kubeconfig, since other roles get none

## Questions

### Which is better for AI agents, GPUsMarket or Together GPU Clusters?

Together GPU Clusters scores 58.1 (C) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. GPUsMarket leads on payments & pricing.

### Do GPUsMarket and Together GPU Clusters need an API key?

Both need an API key.

### Can an agent call GPUsMarket and Together GPU Clusters without installing anything?

Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "gpusmarket", "b": "together-gpu-clusters"}`. From a terminal: `anchor compare gpusmarket together-gpu-clusters`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpusmarket.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json

## Other comparisons with GPUsMarket or Together GPU Clusters

- [Baseten vs GPUsMarket](https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.md)
- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)
- [Beam vs GPUsMarket](https://www.anchorterminal.com/compare/beam-vs-gpusmarket.md)
- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)
- [Cerebrium vs GPUsMarket](https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket.md)
- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)
- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)
- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)
- [CoreWeave vs GPUsMarket](https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.md)
- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)
- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)
- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)
- [GPUsMarket vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/gpusmarket-vs-hugging-face-inference-endpoints.md)
- [GPUsMarket vs Hyperbolic](https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic.md)
- [GPUsMarket vs Koyeb](https://www.anchorterminal.com/compare/gpusmarket-vs-koyeb.md)
- [GPUsMarket vs Lambda Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.md)
- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)
- [GPUsMarket vs Modal](https://www.anchorterminal.com/compare/gpusmarket-vs-modal.md)
- [GPUsMarket vs Nebius AI Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud.md)
- [GPUsMarket vs Northflank](https://www.anchorterminal.com/compare/gpusmarket-vs-northflank.md)
- [GPUsMarket vs Replicate Deployments](https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.md)
- [GPUsMarket vs Runpod](https://www.anchorterminal.com/compare/gpusmarket-vs-runpod.md)
- [GPUsMarket vs Thunder Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.md)
- [GPUsMarket vs Vast.ai](https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai.md)
- [GPUsMarket vs Verda](https://www.anchorterminal.com/compare/gpusmarket-vs-verda.md)
- [Hugging Face Inference Endpoints vs Together GPU Clusters](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters.md)
- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)
- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)
- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)
- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)
- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)
- [Nebius AI Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md)
- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md)
- [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md)
- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md)
- [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md)
- [Together GPU Clusters vs Vast.ai](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.md)
- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp