# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/coreweave-vs-verda
- Markdown: https://www.anchorterminal.com/compare/coreweave-vs-verda.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/coreweave-vs-verda.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/coreweave-vs-verda.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- CoreWeave: grade C, 61.5/100, rank #421 of 842. Markdown https://www.anchorterminal.com/tools/coreweave.md · JSON https://www.anchorterminal.com/api/v1/tools/coreweave.json
- Verda: grade B, 62.3/100, rank #396 of 842. Markdown https://www.anchorterminal.com/tools/verda.md · JSON https://www.anchorterminal.com/api/v1/tools/verda.json

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

| Category | Weight | CoreWeave | Verda | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 67 | Verda +17 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 82 | Verda +3 |
| Agent ergonomics | 13% (16.2 this run) | 58 | 63 | Verda +5 |
| Security & auth | 14% (17.5 this run) | 74 | 68 | CoreWeave +6 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 83 | Verda +3 |
| Transparency & trust | 7% (8.8 this run) | 77 | 76 | CoreWeave +1 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **61.5 · C** | **62.3 · B** | |

## Facts side by side

| Fact | CoreWeave | Verda |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | CoreWeave, Inc. | Verda |
| Hosted endpoint | `https://api.coreweave.com` | `https://api.verda.com/v1` |
| Transports | HTTP | HTTP, stdio |
| Auth | Token | OAuth |
| 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 service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0 |
| Tools exposed | 38 | 18 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-02 | 2026-10-07 |
| Terms last updated | 2022-06-30 | 2025-09-30 |
| Privacy policy last updated | 2026-02-24 | no date given |
| 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 | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 10k 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.


## For agents

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

## Other comparisons with CoreWeave or Verda

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