# GPUsMarket vs Massed Compute

> Massed Compute scores 42.6 (E) 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-massed-compute
- Markdown: https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md (~5,300 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

Massed Compute scores 42.6 (E) on agent readiness against GPUsMarket's 39.6 (E), and leads in 4 of 7 scored categories. GPUsMarket leads on reliability, payments & pricing and maintenance & community. Both do gpu compute.

- GPUsMarket: grade E, 39.6/100, rank #1337 of 1510. Markdown https://www.anchorterminal.com/tools/gpusmarket.md · JSON https://www.anchorterminal.com/api/v1/tools/gpusmarket.json
- Massed Compute: grade E, 42.6/100, rank #1274 of 1510. Markdown https://www.anchorterminal.com/tools/massed-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/massed-compute.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:
- Reliability, 33 against 20
- Payments & pricing, 30 against 20
- Maintenance & community, 69 against 51

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

### Massed Compute (E)

Good for: Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.

Ahead on:
- Schema & documentation, 69 against 52
- Agent ergonomics, 56 against 50
- Security & auth, 61 against 30
- Transparency & trust, 64 against 50

Watch for: No status page, incident history or security.txt was found on any of the vendor's hosts


## Why the edge

### Security & auth: Massed Compute +31

- 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.
- Massed Compute (61): OAuth with discovery from a 401 challenge, or named API tokens shown once and revoked one at a time. Both come in two tiers, read-only and full access, with no finer scopes. Secrets travel only in a header (26 of 30). The read-only tier blocks launch, restart, terminate and SSH key changes. Destructive tool descriptions ask the model to confirm with the user, and a published skill adds a disclosure step. No server-side confirmation was found (13 of 20). The MCP server redacts VM passwords from tool results. Recipes are vendor-written Markdown that tools tell the model to follow step by step, and the docs give no guidance on untrusted content (9 of 15). Connected Apps lists OAuth grants. No audit log or per-call history was found (3 of 15). The wrapper's SECURITY.md gives a disclosure address, a two-business-day acknowledgement and a 30-day fix target, and its CI runs static analysis and dependency audits. The site claims SOC 2 Type II and HIPAA with no report or trust page, and there is no security.txt or bug bounty (10 of 20).

### Maintenance & community: GPUsMarket +18

- 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.
- Massed Compute (51): The newest release of the MCP wrapper is v1.1.0 of 24 July 2026, 77 days before the check. The hosted server has changed since, with fields in the server card that the July definitions lack, but no dated API changelog records it (20 of 30). One release and one dated changelog entry in the last 90 days (0). A dated wrapper changelog and a Discord server named as the fastest support route. No API changelog, and the repository shows six open issues or pull requests whose answers we did not read (7 of 15). Listed in the official MCP registry as `io.github.Massed-Compute/mcp` at 1.1.0, published 31 July 2026, with current npm and PyPI packages (15). CI tests Node 20 and 22 and Python 3.10 to 3.13 on three operating systems, with Dependabot, static analysis and a nightly check of the hosted endpoint. The npm package has no runtime dependencies (9 of 10).

### Schema & documentation: Massed Compute +17

- 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.
- Massed Compute (69): A public OpenAPI 3.0 file covers the 14 REST operations, and a public server card lists all 17 MCP tools with JSON Schema inputs (25). massedcompute.com has an `llms.txt` that indexes marketing pages, and the vendor publishes an agent catalogue, the server card and four Markdown skills files. The docs sites have no `llms.txt` or Markdown copies (6 of 10). Tool descriptions state the purpose, the cost of a launch, when to search recipes first and when to confirm with the user. REST descriptions are one line each (16 of 20). Required fields are marked and extra properties are refused, but there are no enums, `productName` and `regionName` are free strings, and the OpenAPI file's required lists name `image_id` and `couponCode` where the properties are `imageId` and `coupon` (8 of 15). Every REST operation has a response example. Only 200 and 202 are documented, and errors appear only in a troubleshooting table and a deployment errors page (7 of 15). The path is versioned as `/api/v1` and the MCP wrapper has a dated changelog. No API changelog was found (7 of 15).

### Transparency & trust: Massed Compute +14

- 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.
- Massed Compute (64): Closed service. The End User Licence Agreement of 15 September 2026 is clear and applies Nevada law, and the wrapper is MIT. The Terms & Conditions, the principal agreement, are drawn by a script we could not read (13 of 30). The privacy policy of 22 July 2026, the DPA of 27 March 2026 and the EULA are published. The EULA says VM data is destroyed at termination and persistent storage is kept at most 60 days after non-payment. The privacy policy is a general template that names a mobile application and gives no retention periods (19 of 30). No deprecation policy was found. The wrapper's changelog documents what 1.1.0 removed, and the older docs site still documents `api.massedcompute.com` while the current docs say not to use it (4 of 20). The sub-processor list names 23 processors with locations, is dated 10 September 2026 and has an RSS feed. The DPA says primary processing is in the United States (17 of 20).

### Reliability: GPUsMarket +13

- 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.
- Massed Compute (20): Graded on the hosted lines for the MCP server and the REST API. No status page was found on the site, the docs, the pricing page or the repository (0). No incident history to read (5). The troubleshooting page documents a 429 for request limits with no figures (0). The same page says to wait a minute and retry, and every tool carries an `idempotentHint`, but `instances_launch` has no idempotency key (5 of 15). The on-demand page says 99.999 per cent uptime is guaranteed. No SLA document was found, the End User Licence Agreement promises support only under an order form or SLA, and the Terms & Conditions could not be read (0). The API is `/api/v1`, the server card is version 1.0.0 and nothing is labelled beta (10).

### 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.
- Massed Compute (20): No x402, MPP or L402 in the docs, the OpenAPI files, the server card or the pricing page. Crypto top-ups are made by the account owner in the console (0). Hourly prices for every on-demand configuration are public at vm.massedcompute.com/pricing without a login (20). No free tier or trial credit was found, and a first deposit is needed before a launch (0). Signup, email verification, billing setup and token creation all happen in a browser (0).

## Score by category

| Category | Weight | GPUsMarket | Massed Compute | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 33 | 20 | GPUsMarket +13 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 52 | 69 | Massed Compute +17 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 56 | Massed Compute +6 |
| Security & auth | 14% (17.5 this run) | 30 | 61 | Massed Compute +31 |
| 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 | 51 | GPUsMarket +18 |
| Transparency & trust | 7% (8.8 this run) | 50 | 64 | Massed Compute +14 |
| Negative events | ≤15 | -3 | -5 | |
| **Total** | | **39.6 · E** | **42.6 · E** | |

## Facts side by side

| Fact | GPUsMarket | Massed Compute |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Tyga.Cloud Ltd | Massed Compute |
| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://vm.massedcompute.com/api/v1` |
| Transports | stdio, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | not published | $5.43 per GPU-hour |
| 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 Massed Compute's Terms & Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT |
| Tools exposed | 32 | 17 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | `io.github.jyswee/gpusmarket` | `io.github.Massed-Compute/mcp` |
| Last release | 2026-10-16 | 2026-07-24 |
| Terms last updated | 2026-06-01 | couldn't be read |
| Privacy policy last updated | 2026-03-01 | 2026-07-22 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 1 stars, 79 npm/wk | 1 stars |
| Agent reviews | none | 3.3/5 (4) |

## How the scores have moved

### GPUsMarket

No score change since it was listed.

### Massed Compute

- +0.2 on 29 October 2026: time
- -0.1 on 28 October 2026: correction
- +0.2 on 27 October 2026: checklist

## 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.

**Massed Compute.** The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.

## 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

### Massed Compute

1. Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.
2. Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.
3. Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.
4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.
5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.

## Questions

### Which is better for AI agents, GPUsMarket or Massed Compute?

Massed Compute scores 42.6 (E) on agent readiness against GPUsMarket's 39.6 (E), and leads in 4 of 7 scored categories. GPUsMarket leads on reliability, payments & pricing and maintenance & community.

### Do GPUsMarket and Massed Compute need an API key?

GPUsMarket needs an API key. Massed Compute takes an API key or an OAuth sign-in.

### Can an agent call GPUsMarket and Massed Compute without installing anything?

Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Massed Compute at https://vm.massedcompute.com/api/v1.


## For agents

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

## Other comparisons with GPUsMarket or Massed Compute

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