Get an audit

Head to head · Compute gpu · October 2026 research run

CoreWeave vs Verda

Verda and CoreWeave score within a point of each other on agent readiness, 62.3 (B) and 61.5 (C). CoreWeave leads on security & auth. Both do compute gpu.

CoreWeaveCoreWeave, Inc. · HTTP API C61.5/100#421 of 841 VerdaVerda · HTTP API B62.3/100#396 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

  • Security & auth, 74 against 68

Also in its favour

  • No incidents deducted, where Verda 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

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

  • Reliability, 67 against 50
  • Agent ergonomics, 63 against 58

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 runCoreWeaveVerdaEdge
Reliability16%205067Verda +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27982Verda +3
Agent ergonomics13%16.25863Verda +5
Security & auth14%17.57468CoreWeave +6
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88083Verda +3
Transparency & trust7%8.87776CoreWeave +1
Negative events≤150-3
Total61.5 · C62.3 · B

Facts side by side

FactCoreWeaveVerda
KindHTTP APIHTTP API
VendorCoreWeave, Inc.Verda
Hosted endpointhttps://api.coreweave.comhttps://api.verda.com/v1
TransportsHTTPHTTP, stdio
AuthTokenOAuth
PricingPay per usePay per use
x402nono
LicenceProprietary service under CoreWeave's Terms of Service. The Terraform provider 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 exposed3818
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-022026-10-07
Terms last updated2022-06-302025-09-30
Privacy policy last updated2026-02-24no 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 benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone10k PyPI/wk

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.

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

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

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, CoreWeave or Verda?

Verda and CoreWeave score within a point of each other on agent readiness, 62.3 (B) and 61.5 (C). CoreWeave leads on security & auth.

Do CoreWeave and Verda need an API key?

CoreWeave needs an access token. Verda uses an OAuth sign-in.

Can an agent call CoreWeave and Verda without installing anything?

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

Other comparisons with CoreWeave 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