{ "data": { "a": { "slug": "massed-compute", "name": "Massed Compute", "vendor": "Massed Compute", "vendorUrl": "https://massedcompute.com", "kind": "http-api", "category": "gpu-compute", "summary": "Massed Compute is a US GPU cloud that rents NVIDIA GPU virtual machines by the hour from hardware it owns, with bare metal and clusters by quote. Agents use its REST API or a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/massed-compute", "markdownUrl": "https://www.anchorterminal.com/tools/massed-compute.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/massed-compute.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/massed-compute.json", "repo": "https://github.com/Massed-Compute/massed-compute-mcp", "license": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://vm.massedcompute.com/api/v1", "packages": [ { "registry": "npm", "name": "massed-compute-mcp" }, { "registry": "pypi", "name": "massed-compute-mcp" } ], "auth": "mixed", "authNotes": "Self-serve. The owner signs up in a browser, verifies an email address and creates a named API token at vm.massedcompute.com/settings/api, choosing Full access or Read only. The token is shown once, travels as a Bearer header and is revoked from the token table. The same token works for the REST API and the MCP server. MCP clients that send no token get a 401 with an OAuth challenge, and the owner signs in and approves full or read-only access. Grants are listed and revoked under Connected Apps. The older marketplace API on `api.massedcompute.com` issues keys only through support.", "pricing": "usage", "pricingNotes": "No free tier or trial credit was found. The owner adds a card or pays in crypto, makes a first deposit and sets an auto-recharge threshold of at least $5 before any launch. Running VMs are debited every minute at a published hourly rate. On 9 October 2026 a single A30 was $0.35 an hour, an RTX A6000 $0.57, an L40S $0.97, an A100 80 GB $1.35 and an H100 80 GB $2.73. No bandwidth charge per the pricing page. Bare metal, clusters and the marketplace API are by quote (https://vm.massedcompute.com/pricing).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the two OpenAPI files, the MCP server card or the pricing page. The billing docs describe crypto top-ups made by the account owner, which is not a machine payment protocol (checked 2026-10-09).", "endpoints": [] }, "toolCount": 17, "popularity": { "githubStars": 1, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://vm-docs.massedcompute.com", "llmsTxt": "https://massedcompute.com/llms.txt", "openapi": "https://vm-docs.massedcompute.com/redocusaurus/plugin-redoc-0.yaml", "registryName": "io.github.Massed-Compute/mcp", "capabilities": [ "compute.gpu" ], "tags": [ "hosted", "usage-priced", "openapi", "mcp", "oauth", "api-key", "read-only-keys", "node", "python", "card-required", "crypto-payments", "closed-source" ], "lastRelease": "2026-07-24", "graded": true, "anchor": { "graded": true, "score": 42.3, "grade": "E", "agentReady": false, "rank": 896, "ranked": true, "rankOf": 950, "categoryRank": 18, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "8 June 2026. The `instances_list` and `instances_get` MCP tools returned the cleartext VM password although their descriptions said it was redacted. Fixed in `massed-compute-mcp` 1.0.3 and later moved server-side, with rotation advice in the changelog. No GitHub advisory is published. Fixed and documented, so 3 points (https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md).", "9 October 2026. The product page lists SDKs for Go and a Terraform provider, webhooks and per-project quotas. None appears in the docs, the OpenAPI file or the vendor's public GitHub organisation. 2 points (https://massedcompute.com/products/inventory-api/)." ], "verdict": "The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.", "bestFor": "Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.", "strengths": [ "API tokens and OAuth grants come in read-only and full-access tiers, and tokens are revoked one at a time in the console", "A public server card lists all 17 MCP tools with JSON Schema inputs and `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations", "Hourly prices for 23 GPU configurations, from $0.35 for an A30 to $52.80 for eight B300s, are public without a login", "A public OpenAPI 3.0 file covers the 14 REST operations at `https://vm.massedcompute.com/api/v1`", "The sub-processor list names 23 processors with locations, was updated on 10 September 2026 and has an RSS feed for changes" ], "weaknesses": [ "No status page, incident history or security.txt was found on any of the vendor's hosts", "A 429 answer exists but no rate limit figures are published, and the OpenAPI file documents no error response", "`POST /instance/launch` has no idempotency key, so a retried launch can start a second billed VM", "Until a fix dated 8 June 2026, `instances_list` and `instances_get` returned the cleartext VM password although their descriptions said it was redacted", "The product page lists Go and Terraform SDKs and webhooks that the docs, the OpenAPI file and the public GitHub organisation do not show", "A stopped instance is billed at the full hourly rate. Only termination ends billing, and it deletes the data" ], "agentNotes": [ "Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.", "Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.", "Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.", "Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.", "Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.3 } ], "editorialScores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 53 }, "provenanceScore": 68 }, "connect": { "install": "npm install -g massed-compute-mcp", "claudeCode": "claude mcp add --transport http massed-compute https://vm.massedcompute.com/api/mcp --header \"Authorization: Bearer MC_TOKEN\"", "config": { "mcpServers": { "massed-compute": { "headers": { "Authorization": "Bearer MC_TOKEN" }, "type": "http", "url": "https://vm.massedcompute.com/api/mcp" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/massed-compute" }, "area": "models", "unitPrices": [ { "item": "A30 24 GB VM", "unit": "gpu-hour", "usd": 0.35, "note": "Billed per minute" }, { "item": "RTX A5000 24 GB VM", "unit": "gpu-hour", "usd": 0.44, "note": "Billed per minute" }, { "item": "RTX A6000 48 GB VM", "unit": "gpu-hour", "usd": 0.57, "note": "Billed per minute. An alternative configuration is $0.55" }, { "item": "RTX 6000 Ada 48 GB VM", "unit": "gpu-hour", "usd": 0.79, "note": "Billed per minute" }, { "item": "L40 48 GB VM", "unit": "gpu-hour", "usd": 0.86, "note": "Billed per minute" }, { "item": "RTX PRO 4500 Blackwell 32 GB VM", "unit": "gpu-hour", "usd": 0.92, "note": "Billed per minute" }, { "item": "L40S 48 GB VM", "unit": "gpu-hour", "usd": 0.97, "note": "Billed per minute" }, { "item": "A100 80 GB VM", "unit": "gpu-hour", "usd": 1.35, "note": "Billed per minute. SXM4 and DGX variants are $1.38" }, { "item": "RTX PRO 6000 Blackwell 96 GB VM", "unit": "gpu-hour", "usd": 2.19, "note": "Billed per minute" }, { "item": "H100 80 GB VM", "unit": "gpu-hour", "usd": 2.73, "note": "Billed per minute. H100 NVL is $3.11 and H100 SXM5 $3.14" }, { "item": "H200 NVL 141 GB VM", "unit": "gpu-hour", "usd": 3.62, "note": "Billed per minute" }, { "item": "B200 SXM6 VM, 8 GPUs", "unit": "gpu-hour", "usd": 5.43, "note": "Sold only as eight GPUs at $43.46 an hour. Our division, rounded" }, { "item": "B300 SXM6 VM, 8 GPUs", "unit": "gpu-hour", "usd": 6.6, "note": "Sold only as eight GPUs at $52.80 an hour. Our division" } ], "provenance": { "legalEntity": "Massed Compute, Inc.", "domain": "massedcompute.com", "domainRegistered": "2021-10-28", "endpointOnVendorDomain": true, "terms": "https://massedcompute.com/legal/terms-conditions/", "privacy": "https://massedcompute.com/legal/privacy-policy/", "statusPage": "", "changelog": "https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms \u0026 Conditions page is the document the DPA calls the Principal Agreement. Its body is an embedded Termly viewer drawn by script, and we could not read it.", "The End User Licence Agreement, last updated 15 September 2026, names Massed Compute, Inc. of Las Vegas, Nevada, and applies Nevada law. The older docs site's footer says Massed Compute LLC.", "The privacy policy, last updated 22 July 2026, covers the website, a mobile application and the Services in general.", "The REST API and the MCP server answer at vm.massedcompute.com, on the vendor domain.", "/.well-known/security.txt answers 404 on massedcompute.com and on vm.massedcompute.com.", "RDAP for massedcompute.com gives a registration date of 2021-10-28.", "No status page was found on the site, the docs or the pricing page.", "The changelog linked is the MCP wrapper's. No API changelog was found.", "A Data Processing Agreement, last modified 27 March 2026, and a sub-processor list, last updated 10 September 2026, are published." ], "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/massed-compute.json", "live": { "slug": "massed-compute", "probe": { "target": "https://vm.massedcompute.com/api/v1", "method": "get", "lastAt": "2026-10-10T01:37:57.796991169Z", "lastOk": true, "lastStatus": 200, "lastMs": 528, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 566, "p95ms24h": 1577, "samples24h": 102, "samples30d": 102, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "versions": [ { "registry": "github", "name": "Massed-Compute/massed-compute-mcp", "version": "v1.1.0", "released": "2026-07-24", "seenAt": "2026-10-09T17:04:15.605664679Z" }, { "registry": "npm", "name": "massed-compute-mcp", "version": "1.1.0", "seenAt": "2026-10-09T17:04:14.528689429Z" }, { "registry": "pypi", "name": "massed-compute-mcp", "version": "1.1.0", "released": "2026-07-24", "seenAt": "2026-10-09T17:04:15.405015566Z" } ], "githubStars": 1, "npmWeekly": 37, "pypiWeekly": 20, "pages": [ { "url": "https://raw.githubusercontent.com/Massed-Compute/massed-compute-mcp/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:44:33.145231849Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7fa22cb79429" }, { "url": "https://vm.massedcompute.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:47:14.582656601Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fb389d9be37c" }, { "url": "https://massedcompute.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:41:48.306296743Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "71fd70e07907" }, { "url": "https://massedcompute.com/legal/terms-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:41:50.386665594Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0a8bdfcc06c0" } ], "updatedAt": "2026-10-10T01:37:57.796991169Z" } }, "answer": "Verda scores 62.3 (B) on agent readiness against Massed Compute's 42.3 (E), 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": 438, "ranked": true, "rankOf": 950, "categoryRank": 8, "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-10T01:38:12.32758702Z", "lastOk": true, "lastStatus": 401, "lastMs": 109, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 95, "p95ms24h": 183, "samples24h": 186, "samples30d": 186, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.verda.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:23.412851913Z" }, "versions": [ { "registry": "github", "name": "verda-cloud/verda-cli", "version": "v1.8.2", "released": "2026-08-18", "seenAt": "2026-10-09T17:26:59.98781396Z" }, { "registry": "pypi", "name": "verda", "version": "1.24.1", "released": "2026-08-12", "seenAt": "2026-10-09T17:26:59.802905625Z" } ], "githubStars": 16, "pypiWeekly": 11051, "securityTxt": { "url": "https://verda.com/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T11:59:00Z", "checkedAt": "2026-10-09T15:40:21.589254656Z" }, "llmsTxt": { "url": "https://docs.verda.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:58.156667492Z" }, "pages": [ { "url": "https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:41.491907595Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "55b7715fa61b" }, { "url": "https://verda.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:47:09.994986355Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "499766f0baad" }, { "url": "https://verda.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:47:12.653275511Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d9a0799f6aad" }, { "url": "https://verda.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:47:14.170836231Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "69d5f83b2226" } ], "updatedAt": "2026-10-10T01:38:12.32758702Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Massed Compute", "b": "Verda", "name": "Vendor" }, { "a": "https://vm.massedcompute.com/api/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": "$5.43 per GPU-hour", "b": "not published", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper 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": "17", "b": "18", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.Massed-Compute/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-07-24", "b": "2026-10-07", "name": "Last release" }, { "a": "couldn't be read", "b": "2025-09-30", "name": "Terms last updated" }, { "a": "2026-07-22", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1 stars", "b": "10k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Verda scores 62.3 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Massed Compute or Verda?" }, { "answer": "Massed Compute takes an API key or an OAuth sign-in. Verda uses an OAuth sign-in.", "question": "Do Massed Compute and Verda need an API key?" }, { "answer": "Yes. Massed Compute has a hosted endpoint at https://vm.massedcompute.com/api/v1 and Verda at https://api.verda.com/v1.", "question": "Can an agent call Massed Compute and Verda without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.", "slug": "massed-compute", "watchFor": "No status page, incident history or security.txt was found on any of the vendor's hosts" }, { "aheadOn": [ "Reliability, 67 against 20", "Schema \u0026 documentation, 82 against 69", "Agent ergonomics, 63 against 56", "Security \u0026 auth, 68 against 61", "Maintenance \u0026 community, 83 against 51", "Transparency \u0026 trust, 76 against 61" ], "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": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute.json", "title": "Baseten vs Massed Compute", "url": "https://www.anchorterminal.com/compare/baseten-vs-massed-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-massed-compute.json", "title": "Beam vs Massed Compute", "url": "https://www.anchorterminal.com/compare/beam-vs-massed-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-massed-compute.json", "title": "Cerebrium vs Massed Compute", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-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-massed-compute.json", "title": "CoreWeave vs Massed Compute", "url": "https://www.anchorterminal.com/compare/coreweave-vs-massed-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/crusoe-cloud-vs-massed-compute.json", "title": "Crusoe Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.json", "title": "Crusoe Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.json", "title": "Hugging Face Inference Endpoints vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-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-massed-compute.json", "title": "Hyperbolic vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-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-massed-compute.json", "title": "Koyeb vs Massed Compute", "url": "https://www.anchorterminal.com/compare/koyeb-vs-massed-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-massed-compute.json", "title": "Lambda Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/lambda-vs-massed-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/massed-compute-vs-modal.json", "title": "Massed Compute vs Modal", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.json", "title": "Massed Compute vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank.json", "title": "Massed Compute vs Northflank", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.json", "title": "Massed Compute vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod.json", "title": "Massed Compute vs Runpod", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.json", "title": "Massed Compute vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.json", "title": "Massed Compute vs Vast.ai", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai" }, { "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-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-verda.json", "title": "Northflank vs Verda", "url": "https://www.anchorterminal.com/compare/northflank-vs-verda" }, { "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-verda.json", "title": "Runpod vs Verda", "url": "https://www.anchorterminal.com/compare/runpod-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.json", "title": "Thunder Compute vs Verda", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda" }, { "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": 47, "edge": "verda", "key": "reliability", "massed-compute": 20, "name": "Reliability", "verda": 67, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "verda", "key": "schema", "massed-compute": 69, "name": "Schema \u0026 documentation", "verda": 82, "weight": 13 }, { "by": 7, "edge": "verda", "key": "ergonomics", "massed-compute": 56, "name": "Agent ergonomics", "verda": 63, "weight": 13 }, { "by": 7, "edge": "verda", "key": "security", "massed-compute": 61, "name": "Security \u0026 auth", "verda": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "massed-compute": 20, "name": "Payments \u0026 pricing", "verda": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 32, "edge": "verda", "key": "maintenance", "massed-compute": 51, "name": "Maintenance \u0026 community", "verda": 83, "weight": 7 }, { "by": 15, "edge": "verda", "key": "transparency", "massed-compute": 61, "name": "Transparency \u0026 trust", "verda": 76, "weight": 7 } ], "summary": "Verda scores 62.3 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Both do gpu compute.", "verdicts": { "massed-compute": "The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.", "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/massed-compute-vs-verda", "json": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.md", "slim": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.min.md" }, "markdown": "Verda scores 62.3 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Both do gpu compute.\n\n- Massed Compute: grade E, 42.3/100, rank #896 of 950. Markdown https://www.anchorterminal.com/tools/massed-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/massed-compute.json\n- Verda: grade B, 62.3/100, rank #438 of 950. Markdown https://www.anchorterminal.com/tools/verda.md · JSON https://www.anchorterminal.com/api/v1/tools/verda.json\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 167 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### Massed Compute (E)\n\nGood for: Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.\n\nWatch for: No status page, incident history or security.txt was found on any of the vendor's hosts\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- Reliability, 67 against 20\n- Schema \u0026 documentation, 82 against 69\n- Agent ergonomics, 63 against 56\n- Security \u0026 auth, 68 against 61\n- Maintenance \u0026 community, 83 against 51\n- Transparency \u0026 trust, 76 against 61\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 | Massed Compute | Verda | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 67 | Verda +47 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 82 | Verda +13 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 63 | Verda +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 68 | Verda +7 |\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) | 51 | 83 | Verda +32 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 76 | Verda +15 |\n| Negative events | ≤15 | -5 | -3 | |\n| **Total** | | **42.3 · E** | **62.3 · B** | |\n\n## Facts side by side\n\n| Fact | Massed Compute | Verda |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Massed Compute | Verda |\n| Hosted endpoint | `https://vm.massedcompute.com/api/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 gpu compute | $5.43 per GPU-hour | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper 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 | 17 | 18 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.Massed-Compute/mcp` | not listed |\n| Last release | 2026-07-24 | 2026-10-07 |\n| Terms last updated | couldn't be read | 2025-09-30 |\n| Privacy policy last updated | 2026-07-22 | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 1 stars | 10k PyPI/wk |\n\n## Verdicts\n\n**Massed Compute.** The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.\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### Massed Compute\n\n1. Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.\n2. Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.\n3. Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.\n4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.\n5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.\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, Massed Compute or Verda?\n\nVerda scores 62.3 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories.\n\n### Do Massed Compute and Verda need an API key?\n\nMassed Compute takes an API key or an OAuth sign-in. Verda uses an OAuth sign-in.\n\n### Can an agent call Massed Compute and Verda without installing anything?\n\nYes. Massed Compute has a hosted endpoint at https://vm.massedcompute.com/api/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/massed-compute-vs-verda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/massed-compute-vs-verda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"massed-compute\", \"b\": \"verda\"}`. From a terminal: `anchor compare massed-compute verda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/massed-compute.json and https://www.anchorterminal.com/api/v1/tools/verda.json\n\n## Other comparisons with Massed Compute or Verda\n\n- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)\n- [Baseten vs Verda](https://www.anchorterminal.com/compare/baseten-vs-verda.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md)\n- [Cerebrium vs Massed Compute](https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md)\n- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md)\n- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)\n- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md)\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)\n- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.md)\n- [Hugging Face Inference Endpoints vs Massed Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.md)\n- [Hugging Face Inference Endpoints vs Verda](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.md)\n- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)\n- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md)\n- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)\n- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)\n- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)\n- [Massed Compute vs Modal](https://www.anchorterminal.com/compare/massed-compute-vs-modal.md)\n- [Massed Compute vs Nebius AI Cloud](https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.md)\n- [Massed Compute vs Northflank](https://www.anchorterminal.com/compare/massed-compute-vs-northflank.md)\n- [Massed Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.md)\n- [Massed Compute vs Runpod](https://www.anchorterminal.com/compare/massed-compute-vs-runpod.md)\n- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)\n- [Massed Compute vs Vast.ai](https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.md)\n- [Modal vs Verda](https://www.anchorterminal.com/compare/modal-vs-verda.md)\n- [Nebius AI Cloud vs Verda](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.md)\n- [Northflank vs Verda](https://www.anchorterminal.com/compare/northflank-vs-verda.md)\n- [Replicate Deployments vs Verda](https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.md)\n- [Runpod vs Verda](https://www.anchorterminal.com/compare/runpod-vs-verda.md)\n- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.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-10", "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": "Massed Compute vs Verda", "url": "" } ], "description": "Verda scores 62.3 (B) to Massed Compute's 42.3 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Massed Compute E 42.3", "Verda B 62.3", "scores" ], "h1": "Massed Compute vs Verda", "image": "https://www.anchorterminal.com/assets/og/compare-massed-compute-vs-verda.png", "path": "/compare/massed-compute-vs-verda", "published": "2026-10-01", "section": "tools", "title": "Massed Compute vs Verda for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-verda" }, "tokens": { "markdown": 2750, "slim": 780 }, "version": 1 }