{ "data": { "a": { "slug": "thunder-compute", "name": "Thunder Compute", "vendor": "Thunder Compute", "vendorUrl": "https://www.thundercompute.com", "kind": "http-api", "category": "gpu-compute", "summary": "Thunder Compute is a US GPU cloud renting RTX A6000, L40, A100 and H100 instances by the minute and GPU sandboxes by the second. Agents use its REST API, a hosted MCP server with OAuth, or the `tnr` CLI.", "url": "https://www.anchorterminal.com/tools/thunder-compute", "markdownUrl": "https://www.anchorterminal.com/tools/thunder-compute.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/thunder-compute.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/thunder-compute.json", "repo": "https://github.com/Thunder-Compute/thunder-cli", "license": "Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.thundercompute.com:8443/v1", "packages": [ { "registry": "go", "name": "github.com/Thunder-Compute/thunder-cli" }, { "registry": "pypi", "name": "thunder-sandbox" } ], "auth": "mixed", "authNotes": "Self-serve. The hosted MCP server uses OAuth 2.0 with discovery. The first connection opens a browser to sign in and approve, tokens refresh, and the scopes are `instances:read`, `instances:write`, `snapshots:read`, `snapshots:write`, `sandboxes:read`, `sandboxes:write`, `billing:read` and `org:read`. The REST API takes a named API token as a Bearer header. Tokens are created and revoked one at a time in the console, or with the MCP `create_token` tool, and no token scopes were found. The CLI and the sandbox SDK read `TNR_API_TOKEN` for headless use. Price, specification, availability and template endpoints need no token.", "pricing": "usage", "pricingNotes": "No general free tier. Instances are billed by the minute while they run, paid by saved card or preloaded credit that is non-refundable. Per GPU an hour on 9 October 2026, RTX A6000 is $0.35, L40 $0.79, A100 80 GB $1.09 and H100 $3.20. Sandboxes are billed by the second and need access enabled by the vendor. Students with a US university email get $20 of credit for A6000 and L40 GPUs. Reserved capacity is by quote (https://www.thundercompute.com/pricing).", "priceSummary": "$0.04 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 28, "popularity": { "githubStars": 34, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.thundercompute.com/docs", "llmsTxt": "https://www.thundercompute.com/docs/llms.txt", "openapi": "https://api.thundercompute.com:8443/openapi.json", "registryName": "io.github.Thunder-Compute/thunder-compute", "capabilities": [ "compute.gpu", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "oauth", "api-key", "python", "go", "status-page", "card-required", "closed-source" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 56.1, "grade": "C", "agentReady": false, "rank": 576, "ranked": true, "rankOf": 842, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 48, "maintenance": 79, "payments": 20, "reliability": 65, "schema": 70, "security": 51, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Hosted MCP server at `https://www.thundercompute.com/mcp` with OAuth and ten scopes that separate read from write for instances, snapshots and sandboxes", "Public OpenAPI 3.1 document with 41 operations, plus `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page", "`GET /v2/pricing`, `GET /v2/specs` and `GET /v2/status` return prices, configurations and live availability without a token", "Section 28 of the terms, dated 28 September 2026, permits access by AI agents, scripts and SDKs through the account holder's own credentials", "The status page lists no incidents for July to October 2026 on its Website, API and Instances components" ], "weaknesses": [ "No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability", "`POST /instances/create` has no idempotency key, so a retried launch can start a second billed instance", "Instances cannot be stopped. Pausing means taking a snapshot, deleting the instance and restoring later", "No general free tier. The $20 credit is limited to students with a US university email", "No security.txt or disclosure policy was found, and the SOC 2 Type II claim in `llms.txt` has no report or trust page linked", "The sub-processor list, last updated 27 August 2025, names Firebase for sign-in while the MCP docs name Stytch" ], "agentNotes": [ "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.", "List instances before retrying a failed create, because the call has no idempotency key.", "Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.", "To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.", "For headless use set `TNR_API_TOKEN` to a token from the console. The MCP server needs a browser sign-in on first connection." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.1 } ], "editorialScores": { "ergonomics": 48, "maintenance": 79, "payments": 20, "reliability": 65, "schema": 70, "security": 51, "transparency": 51 }, "provenanceScore": 77 }, "connect": { "install": "curl -fsSL https://raw.githubusercontent.com/Thunder-Compute/thunder-cli/main/scripts/install.sh | bash", "http": "curl https://api.thundercompute.com:8443/v2/pricing", "claudeCode": "claude mcp add --transport http thunder-compute https://www.thundercompute.com/mcp", "config": { "mcpServers": { "thunder-compute": { "url": "https://www.thundercompute.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/thunder-compute" }, "area": "models", "unitPrices": [ { "item": "RTX A6000 48 GB instance", "unit": "gpu-hour", "usd": 0.35, "note": "Billed per minute. One GPU per instance" }, { "item": "L40 48 GB instance", "unit": "gpu-hour", "usd": 0.79, "note": "Billed per minute" }, { "item": "A100 80 GB instance", "unit": "gpu-hour", "usd": 1.09, "note": "Billed per minute. 4 and 8 GPU shapes cost $1.49 a GPU per the price endpoint" }, { "item": "H100 80 GB instance", "unit": "gpu-hour", "usd": 3.2, "note": "Billed per minute" }, { "item": "H100 80 GB sandbox", "unit": "gpu-hour", "usd": 2.95, "note": "Billed per second, plus vCPU and memory. Access on request" }, { "item": "A100 80 GB sandbox", "unit": "gpu-hour", "usd": 1.95, "note": "Billed per second, plus vCPU and memory. Access on request" }, { "item": "Extra instance vCPU", "unit": "vcpu-hour", "usd": 0.04, "note": "Above the vCPUs included with each GPU" }, { "item": "Sandbox vCPU", "unit": "vcpu-hour", "usd": 0.051, "note": "Memory is $0.016 per GiB an hour" }, { "item": "Instance disk above 100 GB per GPU", "unit": "gb-month", "usd": 0.219, "note": "Billed only while the instance runs" }, { "item": "Snapshot storage", "unit": "gb-month", "usd": 0.05, "note": "Kept until deleted" } ], "provenance": { "legalEntity": "Thunder GPU, Inc.", "domain": "thundercompute.com", "domainRegistered": "2024-02-29", "endpointOnVendorDomain": true, "terms": "https://www.thundercompute.com/terms-and-conditions", "privacy": "https://www.thundercompute.com/privacy-policy", "statusPage": "https://status.thundercompute.com", "changelog": "https://github.com/Thunder-Compute/thunder-cli/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms and Conditions, last updated 28 September 2026, name Thunder GPU, Inc., doing business as Thunder Compute, a Delaware company, and apply Delaware law. They cover the site and the services, with sections on automated access, usage billing and instance data deletion.", "The privacy policy, last updated 28 September 2026, covers the website and the GPU platform, including access by AI agents.", "The API answers at api.thundercompute.com on port 8443, and the MCP server at www.thundercompute.com/mcp, both on the vendor domain.", "/.well-known/security.txt answers 404.", "RDAP for thundercompute.com gives a registration date of 2024-02-29.", "The changelog linked is the CLI's. No API changelog was found.", "A Data Processing Addendum is published in the docs and a sub-processor list on the site, last updated 27 August 2025." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/thunder-compute.json", "live": { "slug": "thunder-compute", "probe": { "target": "https://api.thundercompute.com:8443/v1", "method": "get", "lastAt": "2026-10-09T09:27:07.340219077Z", "lastOk": true, "lastStatus": 404, "lastMs": 219, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 619, "p95ms24h": 717, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 20 } ] }, "vendorStatus": { "page": "https://status.thundercompute.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:35.789610874Z" }, "updatedAt": "2026-10-09T09:27:07.340219077Z" } }, "answer": "Verda scores 62.3 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 6 of 7 scored categories.", "b": { "slug": "verda", "name": "Verda", "vendor": "Verda", "vendorUrl": "https://verda.com", "kind": "http-api", "category": "gpu-compute", "summary": "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.", "url": "https://www.anchorterminal.com/tools/verda", "markdownUrl": "https://www.anchorterminal.com/tools/verda.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/verda.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/verda.json", "repo": "https://github.com/verda-cloud/verda-cli", "license": "Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.verda.com/v1", "packages": [ { "registry": "pypi", "name": "verda" }, { "registry": "go", "name": "github.com/verda-cloud/verdacloud-sdk-go" } ], "auth": "oauth", "authNotes": "Self-serve. A signed-in user creates a Client ID and Client Secret on the console's Credentials page, and the secret is shown once. `POST /v1/oauth2/token` with the client credentials grant returns an access token valid for 3,600 seconds and a refresh token, both with the scope `cloud-api-v1`. Credentials belong to the member who created them and are deleted when that member leaves the project. The CLI and its MCP server read the same pair from `~/.verda/credentials` after `verda auth login`. A few catalogue endpoints such as `GET /v1/instance-types` need no token.", "pricing": "usage", "pricingNotes": "No free tier or trial. Accounts are prepaid by card or bank transfer, and Pay As You Go is charged in prepaid 10-minute increments with the unused part refunded. On-demand prices per GPU an hour on 8 October 2026 include H100 80 GB at $3.89, H200 at $5.07, B200 at $7.34 and A100 80 GB at $1.87, with spot at about half. Reserved terms take 2 to 25 per cent off. Serverless containers bill per minute of replica use. Free credits are granted only for approved blog posts or videos (https://verda.com/pricing).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 10461, "asOf": "2026-10-08" }, "docsUrl": "https://docs.verda.com", "llmsTxt": "https://docs.verda.com/llms.txt", "openapi": "https://api.verda.com/v1/openapi.json", "capabilities": [ "compute.gpu", "compute.serverless", "compute.endpoints", "compute.batch", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "oauth", "python", "go", "terraform", "status-page", "soc2", "europe" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 62.3, "grade": "B", "agentReady": false, "rank": 396, "ranked": true, "rankOf": 842, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 83, "payments": 20, "reliability": 67, "schema": 82, "security": 68, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -3, "negativeNotes": [ "2026-03-19, making `location_code` required on `POST /v1/instances`, `POST /v1/clusters` and `POST /v1/volumes`. Requests that had defaulted to FIN-01 began returning 400. The API changelog dates the change 19 March and the docs 23 March, and neither records advance notice. Documented, so 3 points (https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md)." ], "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI 3.1 document with 112 operations and 156 schemas, plus `llms.txt` files on three hosts and the whole docs corpus as Markdown", "Rate limits of 500 requests a minute per project and 60 per endpoint, with `RateLimit` headers and `Retry-After` on 429", "API changelog with 11 dated entries between 11 September and 7 October 2026", "Audit log endpoint in CloudEvents 1.0 format covering 90 days, with the caller's IP address and origin on resource events", "The 18-tool MCP server refuses `create_vm`, `create_volume` and destructive `vm_action` calls unless `confirm: true` is passed" ], "weaknesses": [ "No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero", "Cloud API credentials carry one scope, `cloud-api-v1`, with no read-only credential found in the reviewed documentation", "`POST /v1/instances` has no idempotency key, so a retried launch can start a second billed instance", "The MCP server is marked beta and its tools carry no read-only or destructive annotations", "On 30 December 2025 a storage migration overwrote part of a shared filesystem in FIN-03, and Verda reported irreversible data loss for some customers", "No SLA was found, and the terms give no warranty of uninterrupted availability" ], "agentNotes": [ "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.", "Send `location_code` on every create call. Requests without it have returned 400 since March 2026.", "Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.", "List instances before retrying a failed launch, because create has no idempotency key.", "Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.3 } ], "editorialScores": { "ergonomics": 63, "maintenance": 83, "payments": 20, "reliability": 67, "schema": 82, "security": 68, "transparency": 57 }, "provenanceScore": 95 }, "connect": { "install": "brew install verda-cloud/tap/verda-cli", "http": "curl -X POST https://api.verda.com/v1/oauth2/token -H \"Content-Type: application/json\" -d '{\"grant_type\":\"client_credentials\",\"client_id\":\"\u003cYOUR_CLIENT_ID\u003e\",\"client_secret\":\"\u003cYOUR_CLIENT_SECRET\u003e\"}'", "config": { "mcpServers": { "verda": { "args": [ "mcp", "serve" ], "command": "verda" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/verda" }, "area": "models", "unitPrices": [ { "item": "H100 SXM5 80 GB, on-demand", "unit": "gpu-hour", "usd": 3.89, "note": "Spot $1.95. Billed in prepaid 10-minute increments" }, { "item": "H200 SXM5 141 GB, on-demand", "unit": "gpu-hour", "usd": 5.07, "note": "Spot $2.54" }, { "item": "B200 SXM6 180 GB, on-demand", "unit": "gpu-hour", "usd": 7.34, "note": "Spot $3.67" }, { "item": "B300 SXM6 268 GB, on-demand", "unit": "gpu-hour", "usd": 9.24, "note": "Spot $4.62" }, { "item": "A100 SXM4 80 GB, on-demand", "unit": "gpu-hour", "usd": 1.87, "note": "Spot $0.935" }, { "item": "L40S 48 GB, on-demand", "unit": "gpu-hour", "usd": 1.61, "note": "Spot $0.803" }, { "item": "H100 SXM5 80 GB, serverless container", "unit": "gpu-hour", "usd": 4.28, "note": "Spot $2.14. Billed per minute of replica use" }, { "item": "NVMe block volume or shared filesystem", "unit": "gb-month", "usd": 0.2, "note": "Per GiB" } ], "provenance": { "legalEntity": "DataCrunch Oy", "domain": "verda.com", "domainRegistered": "1998-05-22", "endpointOnVendorDomain": true, "terms": "https://verda.com/terms-and-conditions", "privacy": "https://verda.com/privacy-policy", "statusPage": "https://status.verda.com", "changelog": "https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Terms of Service, last updated 30 September 2025, name the supplier as Verda (DataCrunch Oy), apply Finnish law and set arbitration in Helsinki. They include the data processing terms.", "The CLI source carries the copyright of Verda Cloud Oy.", "The API answers at api.verda.com, a subdomain of the vendor domain.", "security.txt expires on 31 December 2026, lists security@verda.com and a policy at https://vdp.verda.com.", "RDAP for verda.com gives a registration date of 1998-05-22. The company took the Verda name later, and verda.com/llms.txt says it was previously known as DataCrunch.", "The privacy policy covers the website and the services and shows no readable date." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/verda.json", "live": { "slug": "verda", "probe": { "target": "https://api.verda.com/v1", "method": "get", "lastAt": "2026-10-09T09:27:09.210083957Z", "lastOk": true, "lastStatus": 401, "lastMs": 82, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 84, "p95ms24h": 151, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 20 } ] }, "vendorStatus": { "page": "https://status.verda.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:39.142949931Z" }, "updatedAt": "2026-10-09T09:27:09.210083957Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Thunder Compute", "b": "Verda", "name": "Vendor" }, { "a": "https://api.thundercompute.com:8443/v1", "b": "https://api.verda.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.219 per GB per month", "b": "not published", "name": "Price for compute gpu" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT", "b": "Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0", "name": "Licence" }, { "a": "28", "b": "18", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.Thunder-Compute/thunder-compute", "b": "not listed", "name": "MCP registry" }, { "a": "2026-09-16", "b": "2026-10-07", "name": "Last release" }, { "a": "2026-09-28", "b": "2025-09-30", "name": "Terms last updated" }, { "a": "2026-09-28", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "34 stars", "b": "10k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Verda scores 62.3 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Thunder Compute or Verda?" }, { "answer": "Thunder Compute takes an API key or an OAuth sign-in. Verda uses an OAuth sign-in.", "question": "Do Thunder Compute and Verda need an API key?" }, { "answer": "Yes. Thunder Compute has a hosted endpoint at https://api.thundercompute.com:8443/v1 and Verda at https://api.verda.com/v1.", "question": "Can an agent call Thunder Compute and Verda without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Verda loses 3 points for them" ], "goodFor": "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.", "slug": "thunder-compute", "watchFor": "No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability" }, { "aheadOn": [ "Schema \u0026 documentation, 82 against 70", "Agent ergonomics, 63 against 48", "Security \u0026 auth, 68 against 51", "Transparency \u0026 trust, 76 against 64" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "verda", "watchFor": "No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero" } ], "job": { "capability": "compute.gpu", "name": "Compute gpu" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.json", "title": "Baseten vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/baseten-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/baseten-vs-verda.json", "title": "Baseten vs Verda", "url": "https://www.anchorterminal.com/compare/baseten-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-thunder-compute.json", "title": "Beam vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/beam-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-verda.json", "title": "Beam vs Verda", "url": "https://www.anchorterminal.com/compare/beam-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.json", "title": "Cerebrium vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-verda.json", "title": "Cerebrium vs Verda", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.json", "title": "CoreWeave vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-verda.json", "title": "CoreWeave vs Verda", "url": "https://www.anchorterminal.com/compare/coreweave-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute.json", "title": "Hugging Face Inference Endpoints vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.json", "title": "Hugging Face Inference Endpoints vs Verda", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.json", "title": "Hyperbolic vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda.json", "title": "Hyperbolic vs Verda", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.json", "title": "Koyeb vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-verda.json", "title": "Koyeb vs Verda", "url": "https://www.anchorterminal.com/compare/koyeb-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.json", "title": "Lambda Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/lambda-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-verda.json", "title": "Lambda Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/lambda-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-thunder-compute.json", "title": "Modal vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/modal-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-verda.json", "title": "Modal vs Verda", "url": "https://www.anchorterminal.com/compare/modal-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.json", "title": "Nebius AI Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.json", "title": "Nebius AI Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.json", "title": "Northflank vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-verda.json", "title": "Northflank vs Verda", "url": "https://www.anchorterminal.com/compare/northflank-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.json", "title": "Replicate Deployments vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.json", "title": "Replicate Deployments vs Verda", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.json", "title": "Runpod vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/runpod-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-verda.json", "title": "Runpod vs Verda", "url": "https://www.anchorterminal.com/compare/runpod-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.json", "title": "Thunder Compute vs Vast.ai", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/vast-ai-vs-verda.json", "title": "Vast.ai vs Verda", "url": "https://www.anchorterminal.com/compare/vast-ai-vs-verda" } ], "scores": [ { "by": 2, "edge": "verda", "key": "reliability", "name": "Reliability", "thunder-compute": 65, "verda": 67, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 12, "edge": "verda", "key": "schema", "name": "Schema \u0026 documentation", "thunder-compute": 70, "verda": 82, "weight": 13 }, { "by": 15, "edge": "verda", "key": "ergonomics", "name": "Agent ergonomics", "thunder-compute": 48, "verda": 63, "weight": 13 }, { "by": 17, "edge": "verda", "key": "security", "name": "Security \u0026 auth", "thunder-compute": 51, "verda": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "thunder-compute": 20, "verda": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "verda", "key": "maintenance", "name": "Maintenance \u0026 community", "thunder-compute": 79, "verda": 83, "weight": 7 }, { "by": 12, "edge": "verda", "key": "transparency", "name": "Transparency \u0026 trust", "thunder-compute": 64, "verda": 76, "weight": 7 } ], "summary": "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda", "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.md", "slim": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.min.md" }, "markdown": "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.\n\n- Thunder Compute: grade C, 56.1/100, rank #576 of 842. Markdown https://www.anchorterminal.com/tools/thunder-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/thunder-compute.json\n- 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\n\n## Which one, for what\n\n### Thunder Compute (C)\n\nGood 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.\n\nAlso in its favour:\n- No incidents deducted, where Verda loses 3 points for them\n\nWatch for: No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability\n\n### Verda (B)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 70\n- Agent ergonomics, 63 against 48\n- Security \u0026 auth, 68 against 51\n- Transparency \u0026 trust, 76 against 64\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero\n\n\n## Score by category\n\n| Category | Weight | Thunder Compute | Verda | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 67 | Verda +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 82 | Verda +12 |\n| Agent ergonomics | 13% (16.2 this run) | 48 | 63 | Verda +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 68 | Verda +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 79 | 83 | Verda +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 76 | Verda +12 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **56.1 · C** | **62.3 · B** | |\n\n## Facts side by side\n\n| Fact | Thunder Compute | Verda |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Thunder Compute | Verda |\n| Hosted endpoint | `https://api.thundercompute.com:8443/v1` | `https://api.verda.com/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP, stdio |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| Price for compute gpu | $0.219 per GB per month | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI 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 |\n| Tools exposed | 28 | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.Thunder-Compute/thunder-compute` | not listed |\n| Last release | 2026-09-16 | 2026-10-07 |\n| Terms last updated | 2026-09-28 | 2025-09-30 |\n| Privacy policy last updated | 2026-09-28 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 34 stars | 10k PyPI/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Thunder Compute\n\n1. 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.\n2. List instances before retrying a failed create, because the call has no idempotency key.\n3. Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.\n4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.\n5. For headless use set `TNR_API_TOKEN` to a token from the console. The MCP server needs a browser sign-in on first connection.\n\n### Verda\n\n1. 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.\n2. Send `location_code` on every create call. Requests without it have returned 400 since March 2026.\n3. Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.\n4. List instances before retrying a failed launch, because create has no idempotency key.\n5. Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set.\n\n## Questions\n\n### Which is better for AI agents, Thunder Compute or Verda?\n\nVerda scores 62.3 (B) on agent readiness against Thunder Compute's 56.1 (C), and leads in 6 of 7 scored categories.\n\n### Do Thunder Compute and Verda need an API key?\n\nThunder Compute takes an API key or an OAuth sign-in. Verda uses an OAuth sign-in.\n\n### Can an agent call Thunder Compute and Verda without installing anything?\n\nYes. Thunder Compute has a hosted endpoint at https://api.thundercompute.com:8443/v1 and Verda at https://api.verda.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/thunder-compute-vs-verda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/thunder-compute-vs-verda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"thunder-compute\", \"b\": \"verda\"}`. From a terminal: `anchor compare thunder-compute verda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/thunder-compute.json and https://www.anchorterminal.com/api/v1/tools/verda.json\n\n## Other comparisons with Thunder Compute or Verda\n\n- [Baseten vs Thunder Compute](https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.md)\n- [Baseten vs Verda](https://www.anchorterminal.com/compare/baseten-vs-verda.md)\n- [Beam vs Thunder Compute](https://www.anchorterminal.com/compare/beam-vs-thunder-compute.md)\n- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md)\n- [Cerebrium vs Thunder Compute](https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.md)\n- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md)\n- [CoreWeave vs Thunder Compute](https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.md)\n- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md)\n- [Hugging Face Inference Endpoints vs Thunder Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute.md)\n- [Hugging Face Inference Endpoints vs Verda](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.md)\n- [Hyperbolic vs Thunder Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.md)\n- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md)\n- [Koyeb vs Thunder Compute](https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.md)\n- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md)\n- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)\n- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)\n- [Modal vs Thunder Compute](https://www.anchorterminal.com/compare/modal-vs-thunder-compute.md)\n- [Modal vs Verda](https://www.anchorterminal.com/compare/modal-vs-verda.md)\n- [Nebius AI Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.md)\n- [Nebius AI Cloud vs Verda](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.md)\n- [Northflank vs Thunder Compute](https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.md)\n- [Northflank vs Verda](https://www.anchorterminal.com/compare/northflank-vs-verda.md)\n- [Replicate Deployments vs Thunder Compute](https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.md)\n- [Replicate Deployments vs Verda](https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.md)\n- [Runpod vs Thunder Compute](https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.md)\n- [Runpod vs Verda](https://www.anchorterminal.com/compare/runpod-vs-verda.md)\n- [Thunder Compute vs Vast.ai](https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.md)\n- [Vast.ai vs Verda](https://www.anchorterminal.com/compare/vast-ai-vs-verda.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Thunder Compute vs Verda", "url": "" } ], "description": "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. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Thunder Compute C 56.1", "Verda B 62.3", "scores" ], "h1": "Thunder Compute vs Verda", "image": "https://www.anchorterminal.com/assets/og/compare-thunder-compute-vs-verda.png", "path": "/compare/thunder-compute-vs-verda", "published": "2026-10-01", "section": "tools", "title": "Thunder Compute vs Verda for AI agents, C 56.1 vs B 62.3", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda" }, "tokens": { "markdown": 2550, "slim": 680 }, "version": 1 }