Get an audit

Head to head · Compute gpu · October 2026 research run

Thunder Compute vs Verda

Verda scores 62.3 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 6 of 7 scored categories. Both do compute gpu.

Thunder ComputeThunder Compute · HTTP API C56.1/100#576 of 841 VerdaVerda · HTTP API B62.3/100#396 of 841

Which one, for what

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.

Also in its favour

  • No incidents deducted, where Verda loses 3 points for them

Watch for

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

Verda B

Good for Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP.

Ahead on

  • Schema & documentation, 82 against 70
  • Agent ergonomics, 63 against 48
  • Security & auth, 68 against 51
  • Transparency & trust, 76 against 64

Also in its favour

  • Runs on your own machine

Watch for

No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero

Score by category

CategoryWeight this runThunder ComputeVerdaEdge
Reliability16%206567Verda +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27082Verda +12
Agent ergonomics13%16.24863Verda +15
Security & auth14%17.55168Verda +17
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87983Verda +4
Transparency & trust7%8.86476Verda +12
Negative events≤150-3
Total56.1 · C62.3 · B

Facts side by side

FactThunder ComputeVerda
KindHTTP APIHTTP API
VendorThunder ComputeVerda
Hosted endpointhttps://api.thundercompute.com:8443/v1https://api.verda.com/v1
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyOAuth
PricingPay per usePay per use
Price for compute gpu$0.219 per GB per monthnot published
x402nono
LicenceProprietary service under Thunder Compute's Terms and Conditions. The tnr CLI on GitHub is MITProprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0
Tools exposed2818
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.Thunder-Compute/thunder-computenot listed
Last release2026-09-162026-10-07
Terms last updated2026-09-282025-09-30
Privacy policy last updated2026-09-28no date given
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 benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity34 stars10k PyPI/wk

Verdicts

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.

Verda

The REST API has a public OpenAPI 3.1 document, a dated changelog, published rate limits with Retry-After, and an audit log endpoint. The CLI's MCP server refuses billed or destructive calls without confirm: true. Access needs a browser signup and a prepaid balance, credentials carry one scope, and instance creation has no idempotency key.

Before you call either

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.

Verda

  1. Exchange the client ID and secret at POST /v1/oauth2/token, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.
  2. Send location_code on every create call. Requests without it have returned 400 since March 2026.
  3. Call GET /v1/instance-availability before launching. POST /v1/instances returns 503 service_unavailable when the location has no capacity.
  4. List instances before retrying a failed launch, because create has no idempotency key.
  5. Use the delete action to stop charges. shutdown keeps billing, and deleted volumes stay recoverable for 96 hours unless delete_permanently is set.

Questions

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

Verda scores 62.3 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 6 of 7 scored categories.

Do Thunder Compute and Verda need an API key?

Thunder Compute takes an API key or an OAuth sign-in. Verda uses an OAuth sign-in.

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

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

Other comparisons with Thunder Compute or Verda

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