# CoreWeave vs GPUsMarket

> CoreWeave scores 60.5 (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/coreweave-vs-gpusmarket
- Markdown: https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.md (~5,200 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

CoreWeave scores 60.5 (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.

- CoreWeave: grade C, 60.5/100, rank #645 of 1486. Markdown https://www.anchorterminal.com/tools/coreweave.md · JSON https://www.anchorterminal.com/api/v1/tools/coreweave.json
- 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
- 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

### CoreWeave (C)

Good for: Teams that already run Kubernetes and need whole multi-GPU nodes or clusters for training and dedicated inference, with a contract and IAM.

Ahead on:
- Reliability, 45 against 33
- Schema & documentation, 79 against 52
- Agent ergonomics, 58 against 50
- Security & auth, 74 against 30
- Maintenance & community, 80 against 69
- Transparency & trust, 78 against 50

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

Watch for: No self-serve route. CoreWeave's sales team approves an organisation and emails the activation link before a token can be created

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


## Why the edge

### Security & auth: CoreWeave +44

- CoreWeave (74): API access tokens are user-scoped, carry an expiry, are shown once and can be revoked in the console. They inherit the user's IAM roles and have no scopes of their own. OIDC workload identity federation is available for CKS workloads. Tokens travel in the Authorization header only (25). IAM has a Viewer and an Admin role per service, and the MCP write tools are off unless CoreWeave enables them for an organisation. There is no confirmation step, and the apply tool ignores `dry_run` (15). The MCP server returns log lines and documentation text, which are untrusted content, and no injection guidance was found (5). Kubernetes audit logs have a Grafana dashboard, Telemetry Relay forwards audit logs to HTTPS or S3, and support staff access is controlled and logged (15). Vulnerability disclosure policy with safe harbour, trust centre badges for SOC 2 Type II, ISO 27001, 27017 and 27018, and a security advisories page whose latest entry is July 2024. No security.txt and no bug bounty found (14).
- 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.

### Transparency & trust: CoreWeave +28

- CoreWeave (78): Closed service with published terms. They were last modified on 30 June 2022 and say they may be amended without notice (15). The terms commit to deleting customer data after account closure within a 30-day recovery period and at most 180 days, there is a data processing agreement, and the privacy policy of 24 February 2026 gives no fixed retention period for personal data (22). The changelog gives dated deprecations, for example Kubernetes v1.34 for new clusters from 16 September 2026 and operating system and driver versions from 29 July 2026, and the maintenance policy promises 24 hours' notice for critical work, though it can change without notice (14). Two sub-processors are named for CoreWeave Infrastructure with their country (Backblaze and Microsoft, both United States) and 30 days' notice of additions, and regions and availability zones are documented (20).
- 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.

### Schema & documentation: CoreWeave +27

- CoreWeave (79): OpenAPI 3.0 specs for the CKS, VPC, Object Storage, Dedicated Inference, Capacity Finder and Telemetry Relay APIs are embedded in the reference pages, and the same services are published as Protobuf on the Buf Schema Registry. The raw .yaml paths in llms.txt redirected our reader to a docs login (25). llms.txt at docs.coreweave.com and every page served as Markdown (10). Operations and MCP tools state their purpose and inputs, with few lines on when not to use them (12). Required fields are marked and the Node Pool reference lists enums, but the CKS spec has none and instance types and versions are plain strings (9). Each operation page has a curl example. Errors are one generic `code`, `message`, `details` shape with no per-operation codes (8). Versioned paths and a dated changelog of 168 entries since December 2024 (15).
- 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.

### Reliability: CoreWeave +12

- CoreWeave (45): Graded as a hosted service on the CKS and platform APIs. Status.io page at status.coreweave.com with components per data centre and email, webhook, Teams, Slack and RSS subscriptions (20). The page's robots.txt now disallows /pages/*, where the history, incident pages and the RSS feed sit, so the 8 October reading of the feed (25 September to 8 October) is struck and the 90-day window is unread. The root page, which is allowed, shows one open incident, a facility power loss in US-EAST-15A from 22 October 2026 marked Partial Service Disruption, still in monitoring on 26 October. The same page counts 5 incidents in the last 30 days without listing them. That is one zone of about 40 and reads as partial, but the rest of the window can't be read, so it isn't credited (5). No request rate limits found for api.coreweave.com, only gateway size limits of about 50 KB and 100 MB, and quotas are set per customer through support (0). No 429 or backoff guidance and no idempotency keys found. Kubernetes resources are declarative, so re-applying a manifest is safe (5 of 15). The terms set an objective of 99.9 per cent across multiple regions and 99 per cent in one, with financial credits (10). CKS is sold as a general service but its cluster API is still v1beta1 and the Node Pool resource v1alpha1 (5 of 10). 20 + 5 + 0 + 5 + 10 + 5 = 45.
- 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.

### Maintenance & community: CoreWeave +11

- CoreWeave (80): The changelog's latest entry is 29 October 2026, Kata Containers runtime selection on CKS in private preview (30). It has 20 dated entries from 5 August to 29 October 2026, among them CKS support for Kubernetes v1.37 (16 September), the Capacity Finder API beta (22 September), Mission Control MCP made generally available (24 September) and CoreWeave Skills in public preview (9 October) (20). Closed service with a dated changelog, a support centre and status updates by email. No public issue tracker for the platform (10 of 15). Generated clients on the Buf Schema Registry and a Terraform provider tagged v0.24.0 on 11 September 2026 per the 8 October check. The MCP server isn't in the official MCP registry (12). The provider repository has build, test, acceptance-test, release and Renovate workflows per the 8 October check. We didn't check that they pass (8).
- 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.

### Payments & pricing: GPUsMarket +10

- CoreWeave (20): No machine payment protocol (0). Per instance-hour prices for GPUs, CPUs, storage and networking are published without a login, with some models quoted by sales (20). No free tier or self-serve trial found. Trials run through the sales-led ARENA programme (0). An organisation has to be approved by the sales team and a person creates the token in the console (0).
- 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.

## Score by category

| Category | Weight | CoreWeave | GPUsMarket | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 33 | CoreWeave +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 52 | CoreWeave +27 |
| Agent ergonomics | 13% (16.2 this run) | 58 | 50 | CoreWeave +8 |
| Security & auth | 14% (17.5 this run) | 74 | 30 | CoreWeave +44 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | GPUsMarket +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 69 | CoreWeave +11 |
| Transparency & trust | 7% (8.8 this run) | 78 | 50 | CoreWeave +28 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **60.5 · C** | **39.6 · E** | |

## Facts side by side

| Fact | CoreWeave | GPUsMarket |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | CoreWeave, Inc. | Tyga.Cloud Ltd |
| Hosted endpoint | `https://api.coreweave.com` | `https://gpusmarket.com/api/v1` |
| Transports | HTTP | stdio, SSE (legacy) |
| Auth | Token | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MIT | Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript |
| Tools exposed | 38 | 32 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.jyswee/gpusmarket` |
| Last release | 2026-10-29 | 2026-10-16 |
| Terms last updated | 2022-06-30 | 2026-06-01 |
| Privacy policy last updated | 2026-02-24 | 2026-03-01 |
| 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 | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 1 stars, 79 npm/wk |
| Agent reviews | 2.5/5 (4) | none |

## How the scores have moved

### CoreWeave

- -1.0 on 2 November 2026: new evidence
- no change on 28 October 2026: checklist

### GPUsMarket

No score change since it was listed.

## Verdicts

**CoreWeave.** Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation.

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

## Before you call either

### CoreWeave

1. Create an API access token at console.coreweave.com/tokens with an expiry and send it as `Authorization: Bearer` to https://api.coreweave.com
2. Add GPUs by applying a NodePool resource (`compute.coreweave.com/v1alpha1`) to a CKS cluster with `instanceType` and `targetNodes`. `instanceType` can't be changed afterwards
3. Set `targetNodes` to 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour
4. Never pass `dry_run` to the MCP tool `coreweave_kubectl_apply` expecting a preview. The reference says the parameter is ignored and the manifest is applied
5. Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there

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

## Questions

### Which is better for AI agents, CoreWeave or GPUsMarket?

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

### Do CoreWeave and GPUsMarket need an API key?

CoreWeave needs an access token. GPUsMarket needs an API key.

### Can an agent call CoreWeave and GPUsMarket without installing anything?

Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and GPUsMarket at https://gpusmarket.com/api/v1.


## For agents

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

## Other comparisons with CoreWeave or GPUsMarket

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

---

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