{ "data": { "a": { "slug": "lambda", "name": "Lambda Cloud", "vendor": "Lambda", "vendorUrl": "https://lambda.ai", "kind": "http-api", "category": "gpu-compute", "summary": "On-demand GPU virtual machines and clusters, with an API for provisioning compute and persistent storage.", "url": "https://www.anchorterminal.com/tools/lambda", "markdownUrl": "https://www.anchorterminal.com/tools/lambda.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lambda.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lambda.json", "transports": [ "http" ], "remoteUrl": "https://cloud.lambda.ai/api/v1", "packages": [], "auth": "api-key", "authNotes": "API key created at cloud.lambda.ai/api-keys and sent as `Authorization: Bearer`. HTTP Basic with the key as the username (`curl -u 'KEY:'`) still works as a legacy option. SSH keys registered in the account are injected into launched instances.", "pricing": "usage", "pricingNotes": "On-demand, per GPU an hour, Tesla V100 16 GB $0.79, A100 40 GB $1.99, A100 80 GB $2.79, H100 SXM 80 GB $3.99, B200 180 GB $6.69. 1-Click Clusters of HGX B200 are quoted per GPU-hour at $9.86 for 16 GPUs, $9.36 for 64 and $8.87 for 256 or more on two-week to one-year commitments. Instances bill in one-minute increments from the moment they pass health checks until you terminate them, invoiced weekly. Filesystems bill per GB used a month in one-hour increments. No free tier (https://lambda.ai/pricing, https://docs.lambda.ai/public-cloud/billing/).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.lambda.ai/public-cloud/on-demand/", "openapi": "https://docs.lambda.ai/api/cloud/spec.json", "capabilities": [ "compute.gpu", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "enterprise" ], "graded": true, "anchor": { "graded": true, "score": 50, "grade": "D", "agentReady": false, "rank": 695, "ranked": true, "rankOf": 842, "categoryRank": 14, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 5, "payments": 20, "reliability": 50, "schema": 69, "security": 60, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.", "bestFor": "Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.", "strengths": [ "H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing", "OpenAPI 3.1 spec with documented error codes, a `suggestion` field and cursor pagination", "Audit events endpoint filterable by time and resource type", "Published rate limits, one request a second and one launch every 12 seconds", "Trust portal with SOC 2 Type 2 and four ISO certifications, and a named subprocessor list" ], "weaknesses": [ "No scale to zero, autoscaling or endpoints; an idle VM bills until terminated", "Ten status incidents in two months, including a two-day regional outage in August 2026", "No changelog, no llms.txt and no official SDK", "API keys have no scopes and launch has no idempotency key", "security.txt expired on 1 June 2026 and no free tier" ], "agentNotes": [ "Call `GET /instance-types` first and read `regions_with_capacity_available` before trying to launch", "Space launch calls 12 seconds apart; a sixth in a minute returns 429 with `global/rate-limited`", "Branch on the error `code`, not the `message` or `suggestion`, which Lambda says may change", "List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine", "Terminate the instance in a `finally` block; billing runs by the minute until you do" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50 } ], "editorialScores": { "ergonomics": 63, "maintenance": 5, "payments": 20, "reliability": 50, "schema": 69, "security": 60, "transparency": 48 }, "provenanceScore": 67 }, "connect": { "http": "curl \"https://cloud.lambda.ai/api/v1/instance-types\" -H \"Authorization: Bearer $LAMBDA_API_KEY\"" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/lambda" }, "area": "models", "unitPrices": [ { "item": "H100 SXM 80 GB", "unit": "gpu-hour", "usd": 3.99, "note": "Billed per minute" }, { "item": "B200 180 GB", "unit": "gpu-hour", "usd": 6.69 }, { "item": "A100 SXM 80 GB", "unit": "gpu-hour", "usd": 2.79 }, { "item": "A100 SXM 40 GB", "unit": "gpu-hour", "usd": 1.99 }, { "item": "Tesla V100 16 GB", "unit": "gpu-hour", "usd": 0.79 }, { "item": "HGX B200 1-Click Cluster, 16 GPUs", "unit": "gpu-hour", "usd": 9.86, "note": "Two-week to one-year commitment; $8.87 at 256 GPUs or more" } ], "provenance": { "legalEntity": "Lambda, Inc.", "domain": "lambda.ai", "domainRegistered": "", "domainNote": "Lambda moved from lambdalabs.com, registered 2008-05-29, to lambda.ai. The .ai registry's RDAP server rate-limited our lookup of the new domain.", "endpointOnVendorDomain": true, "terms": "https://lambda.ai/legal/terms-of-service", "privacy": "https://lambda.ai/legal/privacy-policy", "statusPage": "https://status.lambda.ai", "changelog": "", "securityTxt": "expired", "checked": "2026-09-30", "notes": [ "Terms dated August 2025 and the privacy policy of 1 January 2026 name Lambda, Inc., 2510 Zanker Road, San Jose, California.", "The API runs on cloud.lambda.ai, a subdomain of the vendor domain.", "security.txt expired 2026-06-01 and has no Policy field.", "No public changelog found for the cloud. The OpenAPI spec reports version 1.10.0." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lambda.json", "live": { "slug": "lambda", "probe": { "target": "https://cloud.lambda.ai/api/v1", "method": "get", "lastAt": "2026-10-09T09:26:54.467619436Z", "lastOk": true, "lastStatus": 403, "lastMs": 685, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.95, "p50ms24h": 603, "p95ms24h": 901, "samples24h": 261, "samples30d": 2085, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 101, "ok": 101 } ] }, "vendorStatus": { "page": "https://status.lambda.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:17.021469615Z" }, "securityTxt": { "url": "https://lambda.ai/.well-known/security.txt", "state": "expired", "expires": "2026-06-01T16:00:00Z", "checkedAt": "2026-10-08T15:38:48.494823468Z" }, "domain": { "domain": "lambda.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/lambda.ai", "checkedAt": "2026-10-04T13:04:37.89683091Z" }, "pages": [ { "url": "https://lambda.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:21:12.626677302Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ad7e156559d1" }, { "url": "https://lambda.ai/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:21:08.557293205Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "921eec75dd83" }, { "url": "https://lambda.ai/legal/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:21:10.609958388Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "40e40aee2e7c" } ], "updatedAt": "2026-10-09T09:26:54.467619436Z" } }, "answer": "Verda scores 62.3 (B) on agent readiness against Lambda Cloud's 50 (D), and leads in 5 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": "Lambda", "b": "Verda", "name": "Vendor" }, { "a": "https://cloud.lambda.ai/api/v1", "b": "https://api.verda.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$9.86 per GPU-hour", "b": "not published", "name": "Price for compute gpu" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "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": "none", "b": "18", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-07", "name": "Last release" }, { "a": "2025-08-01", "b": "2025-09-30", "name": "Terms last updated" }, { "a": "2026-01-01", "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": "not found in the text", "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": "none", "b": "10k PyPI/wk", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Verda scores 62.3 (B) on agent readiness against Lambda Cloud's 50 (D), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Lambda Cloud or Verda?" }, { "answer": "Lambda Cloud needs an API key. Verda uses an OAuth sign-in.", "question": "Do Lambda Cloud and Verda need an API key?" }, { "answer": "Yes. Lambda Cloud has a hosted endpoint at https://cloud.lambda.ai/api/v1 and Verda at https://api.verda.com/v1.", "question": "Can an agent call Lambda Cloud and Verda without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Verda loses 3 points for them" ], "goodFor": "Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.", "slug": "lambda", "watchFor": "No scale to zero, autoscaling or endpoints; an idle VM bills until terminated" }, { "aheadOn": [ "Reliability, 67 against 50", "Schema \u0026 documentation, 82 against 69", "Security \u0026 auth, 68 against 60", "Maintenance \u0026 community, 83 against 5", "Transparency \u0026 trust, 76 against 58" ], "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-lambda.json", "title": "Baseten vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/baseten-vs-lambda" }, { "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-lambda.json", "title": "Beam vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/beam-vs-lambda" }, { "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-lambda.json", "title": "Cerebrium vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-lambda" }, { "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-lambda.json", "title": "CoreWeave vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/coreweave-vs-lambda" }, { "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-lambda.json", "title": "Hugging Face Inference Endpoints vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda" }, { "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-lambda.json", "title": "Hyperbolic vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-lambda" }, { "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-lambda.json", "title": "Koyeb vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/koyeb-vs-lambda" }, { "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-modal.json", "title": "Lambda Cloud vs Modal", "url": "https://www.anchorterminal.com/compare/lambda-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud.json", "title": "Lambda Cloud vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-northflank.json", "title": "Lambda Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/lambda-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.json", "title": "Lambda Cloud vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-runpod.json", "title": "Lambda Cloud vs Runpod", "url": "https://www.anchorterminal.com/compare/lambda-vs-runpod" }, { "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-vast-ai.json", "title": "Lambda Cloud vs Vast.ai", "url": "https://www.anchorterminal.com/compare/lambda-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": 17, "edge": "verda", "key": "reliability", "lambda": 50, "name": "Reliability", "verda": 67, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "verda", "key": "schema", "lambda": 69, "name": "Schema \u0026 documentation", "verda": 82, "weight": 13 }, { "by": 0, "edge": "", "key": "ergonomics", "lambda": 63, "name": "Agent ergonomics", "verda": 63, "weight": 13 }, { "by": 8, "edge": "verda", "key": "security", "lambda": 60, "name": "Security \u0026 auth", "verda": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "lambda": 20, "name": "Payments \u0026 pricing", "verda": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 78, "edge": "verda", "key": "maintenance", "lambda": 5, "name": "Maintenance \u0026 community", "verda": 83, "weight": 7 }, { "by": 18, "edge": "verda", "key": "transparency", "lambda": 58, "name": "Transparency \u0026 trust", "verda": 76, "weight": 7 } ], "summary": "Verda scores 62.3 (B) on agent readiness against Lambda Cloud's 50 (D), and leads in 5 of 7 scored categories. Both do compute gpu.", "verdicts": { "lambda": "H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.", "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/lambda-vs-verda", "json": "https://www.anchorterminal.com/compare/lambda-vs-verda.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lambda-vs-verda.md", "slim": "https://www.anchorterminal.com/compare/lambda-vs-verda.min.md" }, "markdown": "Verda scores 62.3 (B) on agent readiness against Lambda Cloud's 50 (D), and leads in 5 of 7 scored categories. Both do compute gpu.\n\n- Lambda Cloud: grade D, 50/100, rank #695 of 842. Markdown https://www.anchorterminal.com/tools/lambda.md · JSON https://www.anchorterminal.com/api/v1/tools/lambda.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### Lambda Cloud (D)\n\nGood for: Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.\n\nAlso in its favour:\n- No incidents deducted, where Verda loses 3 points for them\n\nWatch for: No scale to zero, autoscaling or endpoints; an idle VM bills until terminated\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 50\n- Schema \u0026 documentation, 82 against 69\n- Security \u0026 auth, 68 against 60\n- Maintenance \u0026 community, 83 against 5\n- Transparency \u0026 trust, 76 against 58\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 | Lambda Cloud | Verda | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 67 | Verda +17 |\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) | 63 | 63 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 68 | Verda +8 |\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) | 5 | 83 | Verda +78 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 76 | Verda +18 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **50 · D** | **62.3 · B** | |\n\n## Facts side by side\n\n| Fact | Lambda Cloud | Verda |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Lambda | Verda |\n| Hosted endpoint | `https://cloud.lambda.ai/api/v1` | `https://api.verda.com/v1` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| Price for compute gpu | $9.86 per GPU-hour | not published |\n| x402 | no | no |\n| Licence | none | 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 | none | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-07 |\n| Terms last updated | 2025-08-01 | 2025-09-30 |\n| Privacy policy last updated | 2026-01-01 | 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 | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | none | 10k PyPI/wk |\n| Agent reviews | 3/5 (2) | none |\n\n## Verdicts\n\n**Lambda Cloud.** H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.\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### Lambda Cloud\n\n1. Call `GET /instance-types` first and read `regions_with_capacity_available` before trying to launch\n2. Space launch calls 12 seconds apart; a sixth in a minute returns 429 with `global/rate-limited`\n3. Branch on the error `code`, not the `message` or `suggestion`, which Lambda says may change\n4. List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine\n5. Terminate the instance in a `finally` block; billing runs by the minute until you do\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, Lambda Cloud or Verda?\n\nVerda scores 62.3 (B) on agent readiness against Lambda Cloud's 50 (D), and leads in 5 of 7 scored categories.\n\n### Do Lambda Cloud and Verda need an API key?\n\nLambda Cloud needs an API key. Verda uses an OAuth sign-in.\n\n### Can an agent call Lambda Cloud and Verda without installing anything?\n\nYes. Lambda Cloud has a hosted endpoint at https://cloud.lambda.ai/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/lambda-vs-verda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lambda-vs-verda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lambda\", \"b\": \"verda\"}`. From a terminal: `anchor compare lambda verda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lambda.json and https://www.anchorterminal.com/api/v1/tools/verda.json\n\n## Other comparisons with Lambda Cloud or Verda\n\n- [Baseten vs Lambda Cloud](https://www.anchorterminal.com/compare/baseten-vs-lambda.md)\n- [Baseten vs Verda](https://www.anchorterminal.com/compare/baseten-vs-verda.md)\n- [Beam vs Lambda Cloud](https://www.anchorterminal.com/compare/beam-vs-lambda.md)\n- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md)\n- [Cerebrium vs Lambda Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-lambda.md)\n- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md)\n- [CoreWeave vs Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md)\n- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md)\n- [Hugging Face Inference Endpoints vs Lambda Cloud](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda.md)\n- [Hugging Face Inference Endpoints vs Verda](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.md)\n- [Hyperbolic vs Lambda Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-lambda.md)\n- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md)\n- [Koyeb vs Lambda Cloud](https://www.anchorterminal.com/compare/koyeb-vs-lambda.md)\n- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md)\n- [Lambda Cloud vs Modal](https://www.anchorterminal.com/compare/lambda-vs-modal.md)\n- [Lambda Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud.md)\n- [Lambda Cloud vs Northflank](https://www.anchorterminal.com/compare/lambda-vs-northflank.md)\n- [Lambda Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.md)\n- [Lambda Cloud vs Runpod](https://www.anchorterminal.com/compare/lambda-vs-runpod.md)\n- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)\n- [Lambda Cloud vs Vast.ai](https://www.anchorterminal.com/compare/lambda-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-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": "Lambda Cloud vs Verda", "url": "" } ], "description": "Verda scores 62.3 (B) on agent readiness against Lambda Cloud's 50 (D), and leads in 5 of 7 scored categories. Both do compute gpu. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Lambda Cloud D 50", "Verda B 62.3", "scores" ], "h1": "Lambda Cloud vs Verda", "image": "https://www.anchorterminal.com/assets/og/compare-lambda-vs-verda.png", "path": "/compare/lambda-vs-verda", "published": "2026-10-01", "section": "tools", "title": "Lambda Cloud vs Verda for AI agents, D 50 vs B 62.3 | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/lambda-vs-verda" }, "tokens": { "markdown": 2350, "slim": 630 }, "version": 1 }