# Verda (slim) > Verda, formerly DataCrunch, is a Finnish GPU cloud renting GPU and CPU instances, clusters, serverless containers and storage. Agents use its REST API, Python and Go SDKs, or a CLI with a built-in MCP server in beta. - Full: https://www.anchorterminal.com/tools/verda.md (~7,600 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/tools/verda.json · canonical https://www.anchorterminal.com/tools/verda - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09 **B · 62.3/100 · rank #396 of 842 · #7 in GPU & serverless compute · not agent-ready · confidence medium** Assessment: 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. ## Facts - Kind: HTTP API · vendor: Verda · category: GPU & serverless compute · legal entity: DataCrunch Oy · provenance 95/100 - Endpoint: `https://api.verda.com/v1` (HTTP, stdio) - Auth: OAuth · pricing: Pay per use · x402: no · licence: Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0 - Probe metrics: not measured yet (probes haven't run) - Surface graded: The REST API at https://api.verda.com/v1 (OpenAPI 3.1, 112 operations, 10 of them deprecated aliases). The CLI's MCP server is noted alongside and is in beta - MCP server: Local, stdio, started with `verda mcp serve`. 18 tools. `list_locations`, `list_instance_types`, `check_availability`, `list_images`, `list_vms`, `describe_vm`, `create_vm`, `vm_availability`, `vm_action`, `estimate_cost`, `get_balance`, `get_running_costs`, `add_ssh_key`, `list_ssh_keys`, `get_ssh_command`, `create_volume`, `list_volumes`, `list_volumes_in_trash` - Free tier: None. Prepaid balance, with credits only for approved content - GPUs: GB300, B300, B200, H200, H100, A100 40 and 80 GB, RTX PRO 6000, L40S, RTX 6000 Ada, RTX A6000 and Tesla V100, in 1, 2, 4 or 8 GPU shapes per the pricing page - Scale to zero: Serverless containers scale to zero with `min_replica_count` 0. Instances bill until deleted, and `shutdown` keeps charging - Cold start: No figure published. The docs say the first request after idle waits for a cold start - Billing basis: Instances in prepaid 10-minute increments with unused time refunded. Serverless containers per minute of replica use. Storage per GiB a month - Rate limits: 500 requests a minute per project and 60 a minute per project, method and path, with `RateLimit-Policy`, `RateLimit` and `Retry-After` headers - Errors: `code` and `message`. Codes are `invalid_request`, `unauthorized_request`, `insufficient_funds`, `forbidden_action`, `not_found`, `rate_limit_exceeded`, `server_error` and `service_unavailable` - Regions: FIN-01, FIN-02 and FIN-03, all in Helsinki, Finland, per the docs - SDKs: Python `verda` 1.24.1 (12 August 2026), Go `verdacloud-sdk-go`, Terraform and OpenTofu provider, CLI v1.8.2 (18 August 2026), all Apache-2.0 - Audit: `GET /v1/audit/log` and a JSON export, 90 days, CloudEvents 1.0, owners and admins only, beta - Roles: Owner, Admin and Developer per project. Credentials act with their creator's role - Status: status.verda.com on BetterStack, 21 components with 180-day history and RSS, JSON and webhook subscriptions - Prices: H100 SXM5 80 GB, on-demand $3.89 per GPU-hour; H200 SXM5 141 GB, on-demand $5.07 per GPU-hour; B200 SXM6 180 GB, on-demand $7.34 per GPU-hour; B300 SXM6 268 GB, on-demand $9.24 per GPU-hour; A100 SXM4 80 GB, on-demand $1.87 per GPU-hour; L40S 48 GB, on-demand $1.61 per GPU-hour; H100 SXM5 80 GB, serverless container $4.28 per GPU-hour; NVMe block volume or shared filesystem $0.20 per GB per month - Scores: Reliability 67, Performance pending, Schema & documentation 82, Agent ergonomics 63, Security & auth 68, Payments & pricing 20, Task success pending, Maintenance & community 83, Transparency & trust 76 · negative events -3 · total over the 7 assessed categories - Why: Reliability, Graded on the hosted lines for the REST API. · Schema & documentation, Public OpenAPI 3.1 document at api.verda.com/v1/openapi.json with 112 operations and 156 schemas (25). · Agent ergonomics, No field selection, and instance and volume lists return whole arrays (12 of 25). · Security & auth, OAuth 2.0 client credentials. · Payments & pricing, No x402, MPP or L402 in the docs, the OpenAPI document or the pricing page (0). · Maintenance & community, The newest API changelog entry is dated 7 October 2026 (30). · Transparency & trust, Closed service under Terms of Service dated 30 September 2025 and Finnish law. - Sources: 18, open questions: 9, both in the full twin - Capabilities: compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers - JSON: https://www.anchorterminal.com/api/v1/tools/verda.json - Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/verda.svg` or a link to https://www.anchorterminal.com/tools/verda from a page on verda.com or one of its subdomains, or the README of github.com/verda-cloud/verda-cli, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin. ## Before you call it 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. ## Connect ```bash brew install verda-cloud/tap/verda-cli ``` ```bash curl -X POST https://api.verda.com/v1/oauth2/token -H "Content-Type: application/json" -d '{"grant_type":"client_credentials","client_id":"","client_secret":""}' ``` Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/verda ## Similar tools | Tool | Grade | Score | Shared capabilities | Slim | | --- | --- | --- | --- | --- | | Modal | B | 63.6 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | https://www.anchorterminal.com/tools/modal.min.md | | Beam | C | 55.5 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | https://www.anchorterminal.com/tools/beam.min.md | | Cerebrium | C | 55.3 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | https://www.anchorterminal.com/tools/cerebrium.min.md | | Runpod | D | 53.5 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | https://www.anchorterminal.com/tools/runpod.min.md | | Nebius AI Cloud | B | 67.2 | compute.gpu, compute.endpoints, compute.batch, compute.containers | https://www.anchorterminal.com/tools/nebius-ai-cloud.min.md | ## Panel reviews (0, desk reviews from public material, no calls made)