Get an audit

Head to head · Compute gpu · October 2026 research run

CoreWeave vs Thunder Compute

CoreWeave scores 61.5 (C) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on reliability. Both do compute gpu.

CoreWeaveCoreWeave, Inc. · HTTP API C61.5/100#421 of 841 Thunder ComputeThunder Compute · HTTP API C56.1/100#576 of 841

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

  • Schema & documentation, 79 against 70
  • Agent ergonomics, 58 against 48
  • Security & auth, 74 against 51
  • Transparency & trust, 77 against 64

Watch for

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

Thunder Compute C

Good for Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.

Ahead on

  • Reliability, 65 against 50

Watch for

No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability

Score by category

CategoryWeight this runCoreWeaveThunder ComputeEdge
Reliability16%205065Thunder Compute +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27970CoreWeave +9
Agent ergonomics13%16.25848CoreWeave +10
Security & auth14%17.57451CoreWeave +23
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88079CoreWeave +1
Transparency & trust7%8.87764CoreWeave +13
Negative events≤1500
Total61.5 · C56.1 · C

Facts side by side

FactCoreWeaveThunder Compute
KindHTTP APIHTTP API
VendorCoreWeave, Inc.Thunder Compute
Hosted endpointhttps://api.coreweave.comhttps://api.thundercompute.com:8443/v1
TransportsHTTPHTTP, Streamable HTTP
AuthTokenOAuth or key
PricingPay per usePay per use
Price for compute gpunot published$0.219 per GB per month
x402nono
LicenceProprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MITProprietary service under Thunder Compute's Terms and Conditions. The tnr CLI on GitHub is MIT
Tools exposed3828
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Thunder-Compute/thunder-compute
Last release2026-10-022026-09-16
Terms last updated2022-06-302026-09-28
Privacy policy last updated2026-02-242026-09-28
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularitynone34 stars

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.

Thunder Compute

The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document with keyless price and availability endpoints. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and instances cannot be stopped, only deleted.

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

Thunder Compute

  1. Call GET /v2/status or the get_availability tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.
  2. List instances before retrying a failed create, because the call has no idempotency key.
  3. Pass public_key on create. If omitted, the response carries a generated private key that is returned once.
  4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.
  5. For headless use set TNR_API_TOKEN to a token from the console. The MCP server needs a browser sign-in on first connection.

Questions

Which is better for AI agents, CoreWeave or Thunder Compute?

CoreWeave scores 61.5 (C) on agent readiness against Thunder Compute's 56.1 (C), and leads in 5 of 7 scored categories. Thunder Compute leads on reliability.

Do CoreWeave and Thunder Compute need an API key?

CoreWeave needs an access token. Thunder Compute takes an API key or an OAuth sign-in.

Can an agent call CoreWeave and Thunder Compute without installing anything?

Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and Thunder Compute at https://api.thundercompute.com:8443/v1.

Other comparisons with CoreWeave or Thunder Compute

Machine-readable

For companies

Do agents find, use and choose your tools?

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

Get an auditSee a sample report