{ "data": { "a": { "slug": "gpusmarket", "name": "GPUsMarket", "vendor": "Tyga.Cloud Ltd", "vendorUrl": "https://gpusmarket.com", "kind": "http-api", "category": "gpu-compute", "summary": "GPUsMarket is a peer-to-peer GPU marketplace from Tyga.Cloud Ltd. Agents rent hosts' NVIDIA GPUs and Macs, or on-demand cloud GPUs, as Ollama and OpenAI-compatible endpoints billed per second, through a REST API, CLI and MCP server.", "url": "https://www.anchorterminal.com/tools/gpusmarket", "markdownUrl": "https://www.anchorterminal.com/tools/gpusmarket.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/gpusmarket.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/gpusmarket.json", "dns": "gpusmarket.grade.anchorterminal.com", "repo": "https://github.com/jyswee/gpusmarket", "license": "Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript", "transports": [ "stdio", "sse" ], "remoteUrl": "https://gpusmarket.com/api/v1", "packages": [ { "registry": "npm", "name": "gpusmarket" }, { "registry": "npm", "name": "gpusmarket-host" } ], "auth": "api-key", "authNotes": "An account key (`gpu_` prefix) from `POST /api/signup` with an email, or from Settings in the web app, covers searching, renting and stopping. Each rental returns its own token for the Ollama or OpenAI-compatible proxy on that rental, and GPU pools take `pool_` keys. No scopes, expiry or rotation documented. Renting places a hold on a saved card.", "pricing": "usage", "pricingNotes": "Per second at each listing's hourly price, from $0.08 an hour (RTX 3060) on the home page, with a $0.50 minimum per rental. Hosts can also bill per request and per token; image, audio and video listings bill per unit. A $10 to $100 card hold is placed per rental. No subscription or prepaid credit; fees are non-refundable.", "priceSummary": "$0.50 / tx", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the docs or the terms (checked 2026-11-06). Payment is a Stripe card hold settled when a rental stops.", "endpoints": [] }, "toolCount": 32, "popularity": { "githubStars": 1, "npmWeekly": 79, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://gpusmarket.com/docs", "llmsTxt": "https://gpusmarket.com/llms.txt", "registryName": "io.github.jyswee/gpusmarket", "capabilities": [ "compute.gpu", "compute.endpoints", "compute.containers" ], "tags": [ "hosted", "usage", "per-second", "mcp", "mcp-registry", "llms-txt", "cli", "ollama", "openai-compatible", "peer-to-peer", "card-hold", "uk" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 39.6, "grade": "E", "agentReady": false, "rank": 1318, "ranked": true, "rankOf": 1486, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 69, "payments": 30, "reliability": 33, "schema": 52, "security": 30, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": -3, "negativeNotes": [ "2026-11-06. The docs' Open Source section lists gpusmarket-host, the package hosts install with `npx gpusmarket-host`, under the MIT licence, while version 1.6.0 on npm (8 October 2026) declares `SEE LICENSE IN LICENSE`, ships a proprietary Tyga.Cloud Ltd licence and is built with javascript-obfuscator. A misleading licence claim on the vendor's own page, 3 points. https://gpusmarket.com/docs, https://registry.npmjs.org/gpusmarket-host" ], "verdict": "An agent can sign up with one API call, search priced GPUs without a key, rent a peer or cloud GPU as an Ollama or OpenAI-compatible endpoint and stop it, billed per second. Prompts on peer rentals pass through individuals' machines, the CLI is obfuscated, and there is no status page, security policy or free tier.", "bestFor": "Cheap, short GPU rentals for open models behind an Ollama or OpenAI endpoint, where data sensitivity is low.", "strengths": [ "Sign-up and key issue in one API call, and search and GPU prices need no key", "Per-second billing from $0.08 an hour, with a $0.50 minimum per rental", "Every rental speaks both the Ollama and OpenAI formats, and pools spread load across rentals", "llms.txt is a complete API reference with rate limits and error codes", "Listed in the official MCP registry under a verified GitHub namespace" ], "weaknesses": [ "Peer rentals send prompts and outputs through individuals' hardware, with only the terms as protection", "The CLI and host packages are obfuscated, and the docs call the host package MIT while it is proprietary", "No status page, SLA, security.txt or disclosure policy", "Account keys have no scopes or expiry, and renting needs a saved card", "No OpenAPI document or public changelog" ], "agentNotes": [ "Don't send confidential data to peer rentals, since requests pass through the host's machine", "Stop every rental with `POST /api/v1/marketplace/rentals/{id}/stop`, because billing runs per second until it stops", "Use the per-rental token for inference and keep the `gpu_` account key out of inference clients", "Treat 502 as host offline and rent another listing rather than retrying the same one", "Ask the person to add a card before renting, since each rental places a hold on it" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 39.6 } ], "editorialScores": { "ergonomics": 50, "maintenance": 69, "payments": 30, "reliability": 33, "schema": 52, "security": 30, "transparency": 36 }, "provenanceScore": 63, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g gpusmarket", "http": "curl \"https://gpusmarket.com/api/v1/marketplace/search?gpu=RTX%204090\u0026maxPrice=1.00\"", "claudeCode": "claude mcp add gpusmarket -- gpusmarket mcp-serve" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/gpusmarket" }, "area": "models", "unitPrices": [ { "item": "RTX 3060, lowest listed", "unit": "gpu-hour", "usd": 0.08, "note": "home page, billed per second" }, { "item": "RTX 4090", "unit": "gpu-hour", "usd": 0.35, "note": "home page example; the docs' cloud deploy example shows $0.51" }, { "item": "Minimum per rental", "unit": "tx", "usd": 0.5, "note": "charged when metered usage is lower" } ], "provenance": { "legalEntity": "Tyga.Cloud Ltd", "domain": "gpusmarket.com", "domainRegistered": "2025-03-24", "endpointOnVendorDomain": true, "terms": "https://gpusmarket.com/terms", "privacy": "https://gpusmarket.com/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms (v2.0, June 2026) and privacy policy (March 2026) name Tyga.Cloud Ltd, company 14643275, registered in England and Wales, as operator and data controller.", "Companies House lists Kay Sujittree Somsuk and Joseph Wee as directors and secretaries of Tyga.Cloud Ltd.", "gpusmarket.com/robots.txt allows public pages and disallows /api/, /host/, /renter/, /settings/ and /webhooks/. The terms contain no clause on automated access.", "RDAP gives gpusmarket.com a registration date of 24 March 2025.", "/.well-known/security.txt returns 404. No status page or changelog page found.", "The terms promise 30 days' notice of material changes and give no availability guarantee." ], "score": 63 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/gpusmarket.json", "live": { "slug": "gpusmarket", "probe": { "target": "https://gpusmarket.com/api/v1", "method": "get", "lastAt": "2026-11-07T18:20:28.490737341Z", "lastOk": true, "lastStatus": 404, "lastMs": 192, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 157, "p95ms24h": 245, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.github.jyswee/gpusmarket", "version": "2.4.16", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "gpusmarket", "version": "2.5.1", "seenAt": "2026-11-06T23:30:34.572543077Z" }, { "registry": "npm", "name": "gpusmarket-host", "version": "1.6.0", "seenAt": "2026-11-06T23:30:35.110678472Z" } ], "githubStars": 1, "npmWeekly": 79, "securityTxt": { "url": "https://gpusmarket.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:37.738841214Z" }, "llmsTxt": { "url": "https://gpusmarket.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:37.836383448Z" }, "pages": [ { "url": "https://gpusmarket.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:10:35.479026672Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "dcad60427e70" }, { "url": "https://gpusmarket.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:10:37.570489363Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7d54e59bcd38" } ], "updatedAt": "2026-11-07T18:20:28.490737341Z" } }, "answer": "Lambda Cloud scores 52.9 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "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", "dns": "lambda.grade.anchorterminal.com", "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.com/public-cloud/on-demand/", "openapi": "https://docs.lambda.com/api/cloud/spec.json", "capabilities": [ "compute.gpu", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "enterprise" ], "graded": true, "anchor": { "graded": true, "score": 52.9, "grade": "D", "agentReady": false, "rank": 963, "ranked": true, "rankOf": 1486, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 5, "payments": 20, "reliability": 55, "schema": 69, "security": 70, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "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, with Retry-After on a 429", "Role-based access with service identities and a read-only role, and a trust portal with SOC 2 Type 2 and four ISO certifications" ], "weaknesses": [ "No scale to zero, autoscaling or endpoints; an idle VM bills until terminated", "Seven readable status incidents since August 2026, among them a two-day outage in one region", "No changelog, no llms.txt and no official SDK", "Launch has no idempotency key, and API keys have no documented rotation or expiry", "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`, so wait for the Retry-After interval", "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", "Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.9 } ], "editorialScores": { "ergonomics": 63, "maintenance": 5, "payments": 20, "reliability": 55, "schema": 69, "security": 70, "transparency": 48 }, "provenanceScore": 71, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "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-11-04", "notes": [ "Terms dated August 2025 and the privacy policy of 1 January 2026 name Lambda, Inc., 2510 Zanker Road, San Jose, California (privacy policy per the 1 October 2026 check).", "The API runs on cloud.lambda.ai, a subdomain of the vendor domain. The docs moved from docs.lambda.ai to docs.lambda.com, which docs.lambda.ai now redirects to.", "security.txt expired 2026-06-01 and has no Policy field (read 4 November 2026).", "No public changelog found for the cloud. The OpenAPI spec reports version 1.10.0." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lambda.json", "live": { "slug": "lambda", "probe": { "target": "https://cloud.lambda.ai/api/v1", "method": "get", "lastAt": "2026-11-07T18:20:34.210342176Z", "lastOk": true, "lastStatus": 403, "lastMs": 1104, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.8, "p50ms24h": 750, "p95ms24h": 1112, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 236 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ], "outages": [ { "start": "2026-10-31T04:40:34.538053708Z", "end": "2026-10-31T05:43:37.088836787Z", "note": "EOF" } ] }, "vendorStatus": { "page": "https://status.lambda.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:19.765696346Z" }, "securityTxt": { "url": "https://lambda.ai/.well-known/security.txt", "state": "expired", "expires": "2026-06-01T16:00:00Z", "checkedAt": "2026-11-07T16:01:42.94704571Z" }, "domain": { "domain": "lambda.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/lambda.ai", "checkedAt": "2026-11-01T14:13:00.056712497Z" }, "pages": [ { "url": "https://lambda.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:12:19.409114908Z", "changedAt": "2026-11-07T14:12:19.409114908Z", "fingerprint": "43d2243dd65b" }, { "url": "https://lambda.ai/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:12:14.343180344Z", "changedAt": "2026-11-07T14:12:14.343180344Z", "fingerprint": "d0e1f9cb081a" }, { "url": "https://lambda.ai/legal/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:12:16.798534055Z", "changedAt": "2026-11-07T14:12:16.798534055Z", "fingerprint": "2d5b17c47588" } ], "updatedAt": "2026-11-07T18:21:19.765696346Z" } }, "edges": [ { "by": 64, "category": "maintenance", "leads": "gpusmarket", "name": "Maintenance \u0026 community", "reasons": { "a": "gpusmarket 2.5.1 on 16 October 2026, 21 days before this check (30). Releases 2.4.18 to 2.5.1 between 17 August and 16 October, and gpusmarket-host 1.5.3 and 1.6.0 (20). Support by chat widget; the repository, which holds only a README, server.json and a licence, has no open issues and one star (5). Published in the official MCP registry under the verified io.github.jyswee namespace, though the newest registry version, 2.4.16, trails npm (12). No dependencies, but an obfuscated build and no public CI (2). 30+20+5+12+2 = 69.", "b": "No changelog or release notes found, and the docs pages carry no dates, so we couldn't date the last API change. The spec still reads 1.10.0 although it gained identity, group, role and workspace paths since 1 October (0). No dated changes in the last 90 days found (0). Closed service with a status page that posts updates and a support-ticket API, but no changelog (5 of 15). No official SDK (0). No packages to assess (0). 0 + 0 + 5 + 0 + 0 = 5." }, "scores": { "a": 69, "b": 5 } }, { "by": 40, "category": "security", "leads": "lambda", "name": "Security \u0026 auth", "reasons": { "a": "Account keys are all-powerful within the account, with no scopes, expiry or rotation documented, but each rental gets its own proxy token (15). The per-rental token limits inference access to one rental; no read-only key or confirmation for destructive calls (6). Peer rentals send prompts and outputs through individuals' machines, protected only by the terms, with no prompt-injection or untrusted-host guidance (2). Per-rental usage stats of requests, tokens and cost (5). No security.txt, disclosure policy, bug bounty or certification; a DPO address for breaches. The CLI and host packages are obfuscated, so they can't be audited (2). 15+6+2+5+2 = 30.", "b": "Plain API keys, revocable, sent as Bearer or, as a legacy option, HTTP Basic in the header. Keys now belong to user or service identities whose permissions come from role assignments, but no rotation or expiry is documented (20). Role-based access control with predefined account and workspace roles, including a read-only Instance Reader and a terminate-only role, and service identities for automation; no confirmation step for destructive calls (15). Returns infrastructure metadata, no third-party content (10). An audit events endpoint lists API key and resource changes with time and type filters (15). Trust portal lists SOC 2 Type 2, ISO 27001, 27017, 27701 and 22301 and a pentest report; security.txt names security@lambda.ai but expired on 1 June 2026; no bug bounty found (10). 20 + 15 + 10 + 15 + 10 = 70." }, "scores": { "a": 30, "b": 70 } }, { "by": 22, "category": "reliability", "leads": "lambda", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. No status page found; listing health is shown per listing only (0). No incident history to read (5). Rate limits published, 60 requests a minute per rental and 10 sign-ups an hour per IP (15). 429 is documented, but no Retry-After, backoff or idempotency guidance (3). The terms give no availability guarantee and put host outages on hosts (0). No beta label on the API (10). 0+5+15+3+0+10 = 33.", "b": "incident.io page at status.lambda.ai with components (Cloud API, Network, Virtual Machines, Storage and others) and an RSS feed (20). The feed holds only its ten latest items, back to updates of 17 August 2026, and the page lists only incidents linked to components, so 6 to 17 August is partly unread. What is readable since 6 August touches one region or one function each, so partial and minor by this run's reading: us-south-2 instances unreachable 15 to 17 August, us-midwest-2 networking and performance (opened 3 August, resolved 25 August), API key viewing and creation 10 September, us-south-3 resources 23 September, us-west-1 launches 12 October and us-east-3 launches for 1 hour 10 minutes on 28 October; the 31 October DNS fault hit the lambda.ai website, not the API. The 27 July and 29 to 30 July majors have left the window, but a partly unread window gives no credit, so the line keeps its recorded 0. Rate limits published, one request a second and one launch every 12 seconds (15). The spec's `global/rate-limited` error says to wait for the Retry-After interval and retry, with no idempotency key or safe-retry guidance for launch (10). No SLA found (0). The Cloud API is GA (10). 20 + 0 + 15 + 10 + 0 + 10 = 55." }, "scores": { "a": 33, "b": 55 } }, { "by": 17, "category": "schema", "leads": "lambda", "name": "Schema \u0026 documentation", "reasons": { "a": "API and MCP reading. No OpenAPI or other machine-readable contract was found, and the MCP tool schemas couldn't be read because the published package is obfuscated; the repository's history says 2.4.7 added output schemas to all 32 tools, which is the vendor's claim (8). llms.txt as a complete API reference (10). llms.txt says when to use peer or cloud rentals, the proxy or the relay, and which workload each listing type serves (12). Parameters are listed by name without types, enums or required markers, apart from instance and workload types (6). curl examples for each flow, an error code list and a sample deploy response (11). npm versions, but no public changelog (5). 8+10+12+6+11+5 = 52.", "b": "OpenAPI 3.1 spec, version 1.10.0, linked from the API reference as a download, now 48 paths including identities, groups, roles and workspaces (25). No llms.txt (docs.lambda.com/llms.txt returns 404) and no Markdown twins (0). Operations are described with preconditions, for example a filesystem must be unmounted before deletion, but few say when not to call them (14). Required fields are marked; instance type names and statuses are plain strings rather than enums (10). Examples on requests and responses, and 400, 401, 403, 404, 409, 429 and 503 documented with a `code`, `message` and `suggestion` (15). The spec is versioned and flags `/file-systems` as deprecated, but there's no public changelog or release notes, and the identity and role paths arrived without a version change (5). 25 + 0 + 14 + 10 + 15 + 5 = 69." }, "scores": { "a": 52, "b": 69 } }, { "by": 13, "category": "ergonomics", "leads": "lambda", "name": "Agent ergonomics", "reasons": { "a": "API and MCP reading. The README counts 32 MCP tools, and the decoded package includes 16 operator admin tools besides the renter tools, with no toolsets (5). Marketplace search takes `limit`, `offset`, `sort` and filters for GPU, price, VRAM, model, instance and workload type (20). Status codes with a one-line meaning each, no error bodies documented (10). No idempotency key on rent or deploy; stop and destroy return a cost summary (5). Only a Node CLI, though every proxy speaks the Ollama and OpenAI formats so existing SDKs work (10). 5+20+10+5+10 = 50.", "b": "Responses wrap a `data` payload and lists use `page_token`; no field selection (15). Cursor pagination, and audit events filter by start, end and resource type (18). Errors carry a stable `code`, a `suggestion` and a `request_id`, and the docs tell clients to branch on `code` (20). No idempotency keys and nothing on safe retries for launch; 409 signals conflicts (5). Launch needs region, instance type and SSH key names, and there's no official SDK (5). 15 + 18 + 20 + 5 + 5 = 63." }, "scores": { "a": 50, "b": 63 } }, { "by": 10, "category": "payments", "leads": "gpusmarket", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Hourly prices for every listing and GPU type are public through the unauthenticated search and types endpoints, with a $0.50 minimum (20). No free tier; a card hold is placed on every rental (0). Sign-up and key issue are one API call with no browser, but renting needs a saved, verified card, which the docs don't show being added without a person (10). 0+20+0+10 = 30.", "b": "No machine payment protocol (0). Per-GPU hourly prices published without a login (20). No free tier or trial (0). Signup is a browser flow with billing details (0). 0 + 20 + 0 + 0 = 20." }, "scores": { "a": 30, "b": 20 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Tyga.Cloud Ltd", "b": "Lambda", "name": "Vendor" }, { "a": "https://gpusmarket.com/api/v1", "b": "https://cloud.lambda.ai/api/v1", "name": "Hosted endpoint" }, { "a": "stdio, SSE (legacy)", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$9.86 per GPU-hour", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript", "b": "none", "name": "Licence" }, { "a": "32", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "io.github.jyswee/gpusmarket", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-16", "b": "none", "name": "Last release" }, { "a": "2026-06-01", "b": "2025-08-01", "name": "Terms last updated" }, { "a": "2026-03-01", "b": "2026-01-01", "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": "not found in the text", "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": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1 stars, 79 npm/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Lambda Cloud scores 52.9 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, GPUsMarket or Lambda Cloud?" }, { "answer": "Both need an API key.", "question": "Do GPUsMarket and Lambda Cloud need an API key?" }, { "answer": "Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Lambda Cloud at https://cloud.lambda.ai/api/v1.", "question": "Can an agent call GPUsMarket and Lambda Cloud without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 69 against 5" ], "also": [ "Runs on your own machine" ], "goodFor": "Cheap, short GPU rentals for open models behind an Ollama or OpenAI endpoint, where data sensitivity is low.", "slug": "gpusmarket", "watchFor": "Peer rentals send prompts and outputs through individuals' hardware, with only the terms as protection" }, { "aheadOn": [ "Reliability, 55 against 33", "Schema \u0026 documentation, 69 against 52", "Agent ergonomics, 63 against 50", "Security \u0026 auth, 70 against 30", "Transparency \u0026 trust, 60 against 50" ], "also": [ "No incidents deducted, where GPUsMarket 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" } ], "history": { "gpusmarket": null, "lambda": [ { "causes": [ "product", "evidence" ], "date": "2026-11-04", "delta": 2.8, "from": 50.1, "fromGrade": "D", "to": 52.9, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50, "fromGrade": "D", "to": 50.1, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.1, "from": 50.1, "fromGrade": "D", "to": 50, "toGrade": "D" } ] }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.json", "title": "Baseten vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/baseten-vs-gpusmarket" }, { "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/beam-vs-gpusmarket.json", "title": "Beam vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/beam-vs-gpusmarket" }, { "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/cerebrium-vs-gpusmarket.json", "title": "Cerebrium vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket" }, { "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/cloud-run-gpus-vs-gpusmarket.json", "title": "Cloud Run GPUs vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.json", "title": "Cloud Run GPUs vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.json", "title": "CoreWeave vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket" }, { "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/crusoe-cloud-vs-gpusmarket.json", "title": "Crusoe Cloud vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.json", "title": "Crusoe Cloud vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-hugging-face-inference-endpoints.json", "title": "GPUsMarket vs Hugging Face Inference Endpoints", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-hugging-face-inference-endpoints" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic.json", "title": "GPUsMarket vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-koyeb.json", "title": "GPUsMarket vs Koyeb", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-koyeb" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.json", "title": "GPUsMarket vs Massed Compute", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-modal.json", "title": "GPUsMarket vs Modal", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud.json", "title": "GPUsMarket vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-northflank.json", "title": "GPUsMarket vs Northflank", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.json", "title": "GPUsMarket vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-runpod.json", "title": "GPUsMarket vs Runpod", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.json", "title": "GPUsMarket vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.json", "title": "GPUsMarket vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai.json", "title": "GPUsMarket vs Vast.ai", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda.json", "title": "GPUsMarket vs Verda", "url": "https://www.anchorterminal.com/compare/gpusmarket-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/hyperbolic-vs-lambda.json", "title": "Hyperbolic vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-lambda" }, { "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/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-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-together-gpu-clusters.json", "title": "Lambda Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters" }, { "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/lambda-vs-verda.json", "title": "Lambda Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/lambda-vs-verda" } ], "panel": null, "scores": [ { "by": 22, "edge": "lambda", "gpusmarket": 33, "key": "reliability", "lambda": 55, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 17, "edge": "lambda", "gpusmarket": 52, "key": "schema", "lambda": 69, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 13, "edge": "lambda", "gpusmarket": 50, "key": "ergonomics", "lambda": 63, "name": "Agent ergonomics", "weight": 13 }, { "by": 40, "edge": "lambda", "gpusmarket": 30, "key": "security", "lambda": 70, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "edge": "gpusmarket", "gpusmarket": 30, "key": "payments", "lambda": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 64, "edge": "gpusmarket", "gpusmarket": 69, "key": "maintenance", "lambda": 5, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "lambda", "gpusmarket": 50, "key": "transparency", "lambda": 60, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lambda Cloud scores 52.9 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing and maintenance \u0026 community. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "gpusmarket": "An agent can sign up with one API call, search priced GPUs without a key, rent a peer or cloud GPU as an Ollama or OpenAI-compatible endpoint and stop it, billed per second. Prompts on peer rentals pass through individuals' machines, the CLI is obfuscated, and there is no status page, security policy or free tier.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda", "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.min.md" }, "markdown": "Lambda Cloud scores 52.9 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing and maintenance \u0026 community. Both do gpu compute.\n\n- GPUsMarket: grade E, 39.6/100, rank #1318 of 1486. Markdown https://www.anchorterminal.com/tools/gpusmarket.md · JSON https://www.anchorterminal.com/api/v1/tools/gpusmarket.json\n- Lambda Cloud: grade D, 52.9/100, rank #963 of 1486. Markdown https://www.anchorterminal.com/tools/lambda.md · JSON https://www.anchorterminal.com/api/v1/tools/lambda.json\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### GPUsMarket (E)\n\nGood for: Cheap, short GPU rentals for open models behind an Ollama or OpenAI endpoint, where data sensitivity is low.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 69 against 5\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Peer rentals send prompts and outputs through individuals' hardware, with only the terms as protection\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\nAhead on:\n- Reliability, 55 against 33\n- Schema \u0026 documentation, 69 against 52\n- Agent ergonomics, 63 against 50\n- Security \u0026 auth, 70 against 30\n- Transparency \u0026 trust, 60 against 50\n\nAlso in its favour:\n- No incidents deducted, where GPUsMarket loses 3 points for them\n\nWatch for: No scale to zero, autoscaling or endpoints; an idle VM bills until terminated\n\n\n## Why the edge\n\n### Maintenance \u0026 community: GPUsMarket +64\n\n- GPUsMarket (69): gpusmarket 2.5.1 on 16 October 2026, 21 days before this check (30). Releases 2.4.18 to 2.5.1 between 17 August and 16 October, and gpusmarket-host 1.5.3 and 1.6.0 (20). Support by chat widget; the repository, which holds only a README, server.json and a licence, has no open issues and one star (5). Published in the official MCP registry under the verified io.github.jyswee namespace, though the newest registry version, 2.4.16, trails npm (12). No dependencies, but an obfuscated build and no public CI (2). 30+20+5+12+2 = 69.\n- Lambda Cloud (5): No changelog or release notes found, and the docs pages carry no dates, so we couldn't date the last API change. The spec still reads 1.10.0 although it gained identity, group, role and workspace paths since 1 October (0). No dated changes in the last 90 days found (0). Closed service with a status page that posts updates and a support-ticket API, but no changelog (5 of 15). No official SDK (0). No packages to assess (0). 0 + 0 + 5 + 0 + 0 = 5.\n\n### Security \u0026 auth: Lambda Cloud +40\n\n- GPUsMarket (30): Account keys are all-powerful within the account, with no scopes, expiry or rotation documented, but each rental gets its own proxy token (15). The per-rental token limits inference access to one rental; no read-only key or confirmation for destructive calls (6). Peer rentals send prompts and outputs through individuals' machines, protected only by the terms, with no prompt-injection or untrusted-host guidance (2). Per-rental usage stats of requests, tokens and cost (5). No security.txt, disclosure policy, bug bounty or certification; a DPO address for breaches. The CLI and host packages are obfuscated, so they can't be audited (2). 15+6+2+5+2 = 30.\n- Lambda Cloud (70): Plain API keys, revocable, sent as Bearer or, as a legacy option, HTTP Basic in the header. Keys now belong to user or service identities whose permissions come from role assignments, but no rotation or expiry is documented (20). Role-based access control with predefined account and workspace roles, including a read-only Instance Reader and a terminate-only role, and service identities for automation; no confirmation step for destructive calls (15). Returns infrastructure metadata, no third-party content (10). An audit events endpoint lists API key and resource changes with time and type filters (15). Trust portal lists SOC 2 Type 2, ISO 27001, 27017, 27701 and 22301 and a pentest report; security.txt names security@lambda.ai but expired on 1 June 2026; no bug bounty found (10). 20 + 15 + 10 + 15 + 10 = 70.\n\n### Reliability: Lambda Cloud +22\n\n- GPUsMarket (33): Read with the hosted lines. No status page found; listing health is shown per listing only (0). No incident history to read (5). Rate limits published, 60 requests a minute per rental and 10 sign-ups an hour per IP (15). 429 is documented, but no Retry-After, backoff or idempotency guidance (3). The terms give no availability guarantee and put host outages on hosts (0). No beta label on the API (10). 0+5+15+3+0+10 = 33.\n- Lambda Cloud (55): incident.io page at status.lambda.ai with components (Cloud API, Network, Virtual Machines, Storage and others) and an RSS feed (20). The feed holds only its ten latest items, back to updates of 17 August 2026, and the page lists only incidents linked to components, so 6 to 17 August is partly unread. What is readable since 6 August touches one region or one function each, so partial and minor by this run's reading: us-south-2 instances unreachable 15 to 17 August, us-midwest-2 networking and performance (opened 3 August, resolved 25 August), API key viewing and creation 10 September, us-south-3 resources 23 September, us-west-1 launches 12 October and us-east-3 launches for 1 hour 10 minutes on 28 October; the 31 October DNS fault hit the lambda.ai website, not the API. The 27 July and 29 to 30 July majors have left the window, but a partly unread window gives no credit, so the line keeps its recorded 0. Rate limits published, one request a second and one launch every 12 seconds (15). The spec's `global/rate-limited` error says to wait for the Retry-After interval and retry, with no idempotency key or safe-retry guidance for launch (10). No SLA found (0). The Cloud API is GA (10). 20 + 0 + 15 + 10 + 0 + 10 = 55.\n\n### Schema \u0026 documentation: Lambda Cloud +17\n\n- GPUsMarket (52): API and MCP reading. No OpenAPI or other machine-readable contract was found, and the MCP tool schemas couldn't be read because the published package is obfuscated; the repository's history says 2.4.7 added output schemas to all 32 tools, which is the vendor's claim (8). llms.txt as a complete API reference (10). llms.txt says when to use peer or cloud rentals, the proxy or the relay, and which workload each listing type serves (12). Parameters are listed by name without types, enums or required markers, apart from instance and workload types (6). curl examples for each flow, an error code list and a sample deploy response (11). npm versions, but no public changelog (5). 8+10+12+6+11+5 = 52.\n- Lambda Cloud (69): OpenAPI 3.1 spec, version 1.10.0, linked from the API reference as a download, now 48 paths including identities, groups, roles and workspaces (25). No llms.txt (docs.lambda.com/llms.txt returns 404) and no Markdown twins (0). Operations are described with preconditions, for example a filesystem must be unmounted before deletion, but few say when not to call them (14). Required fields are marked; instance type names and statuses are plain strings rather than enums (10). Examples on requests and responses, and 400, 401, 403, 404, 409, 429 and 503 documented with a `code`, `message` and `suggestion` (15). The spec is versioned and flags `/file-systems` as deprecated, but there's no public changelog or release notes, and the identity and role paths arrived without a version change (5). 25 + 0 + 14 + 10 + 15 + 5 = 69.\n\n### Agent ergonomics: Lambda Cloud +13\n\n- GPUsMarket (50): API and MCP reading. The README counts 32 MCP tools, and the decoded package includes 16 operator admin tools besides the renter tools, with no toolsets (5). Marketplace search takes `limit`, `offset`, `sort` and filters for GPU, price, VRAM, model, instance and workload type (20). Status codes with a one-line meaning each, no error bodies documented (10). No idempotency key on rent or deploy; stop and destroy return a cost summary (5). Only a Node CLI, though every proxy speaks the Ollama and OpenAI formats so existing SDKs work (10). 5+20+10+5+10 = 50.\n- Lambda Cloud (63): Responses wrap a `data` payload and lists use `page_token`; no field selection (15). Cursor pagination, and audit events filter by start, end and resource type (18). Errors carry a stable `code`, a `suggestion` and a `request_id`, and the docs tell clients to branch on `code` (20). No idempotency keys and nothing on safe retries for launch; 409 signals conflicts (5). Launch needs region, instance type and SSH key names, and there's no official SDK (5). 15 + 18 + 20 + 5 + 5 = 63.\n\n### Payments \u0026 pricing: GPUsMarket +10\n\n- GPUsMarket (30): No x402, MPP or L402 (0). Hourly prices for every listing and GPU type are public through the unauthenticated search and types endpoints, with a $0.50 minimum (20). No free tier; a card hold is placed on every rental (0). Sign-up and key issue are one API call with no browser, but renting needs a saved, verified card, which the docs don't show being added without a person (10). 0+20+0+10 = 30.\n- Lambda Cloud (20): No machine payment protocol (0). Per-GPU hourly prices published without a login (20). No free tier or trial (0). Signup is a browser flow with billing details (0). 0 + 20 + 0 + 0 = 20.\n\n## Score by category\n\n| Category | Weight | GPUsMarket | Lambda Cloud | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 55 | Lambda Cloud +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 52 | 69 | Lambda Cloud +17 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 63 | Lambda Cloud +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 70 | Lambda Cloud +40 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | GPUsMarket +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 5 | GPUsMarket +64 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 50 | 60 | Lambda Cloud +10 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **39.6 · E** | **52.9 · D** | |\n\n## Facts side by side\n\n| Fact | GPUsMarket | Lambda Cloud |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Tyga.Cloud Ltd | Lambda |\n| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://cloud.lambda.ai/api/v1` |\n| Transports | stdio, SSE (legacy) | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | not published | $9.86 per GPU-hour |\n| x402 | no | no |\n| Licence | Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript | none |\n| Tools exposed | 32 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| MCP registry | `io.github.jyswee/gpusmarket` | not listed |\n| Last release | 2026-10-16 | none |\n| Terms last updated | 2026-06-01 | 2025-08-01 |\n| Privacy policy last updated | 2026-03-01 | 2026-01-01 |\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 | not found in the text | 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 | not found in the text | yes |\n| Popularity | 1 stars, 79 npm/wk | none |\n| Agent reviews | none | 3/5 (2) |\n\n## How the scores have moved\n\n### GPUsMarket\n\nNo score change since it was listed.\n\n### Lambda Cloud\n\n- +2.8 on 4 November 2026: product, new evidence\n- +0.1 on 27 October 2026: checklist\n- -0.1 on 8 October 2026: checklist\n\n## Verdicts\n\n**GPUsMarket.** An agent can sign up with one API call, search priced GPUs without a key, rent a peer or cloud GPU as an Ollama or OpenAI-compatible endpoint and stop it, billed per second. Prompts on peer rentals pass through individuals' machines, the CLI is obfuscated, and there is no status page, security policy or free tier.\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## Before you call either\n\n### GPUsMarket\n\n1. Don't send confidential data to peer rentals, since requests pass through the host's machine\n2. Stop every rental with `POST /api/v1/marketplace/rentals/{id}/stop`, because billing runs per second until it stops\n3. Use the per-rental token for inference and keep the `gpu_` account key out of inference clients\n4. Treat 502 as host offline and rent another listing rather than retrying the same one\n5. Ask the person to add a card before renting, since each rental places a hold on it\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`, so wait for the Retry-After interval\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\n6. Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring\n\n## Questions\n\n### Which is better for AI agents, GPUsMarket or Lambda Cloud?\n\nLambda Cloud scores 52.9 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do GPUsMarket and Lambda Cloud need an API key?\n\nBoth need an API key.\n\n### Can an agent call GPUsMarket and Lambda Cloud without installing anything?\n\nYes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Lambda Cloud at https://cloud.lambda.ai/api/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gpusmarket\", \"b\": \"lambda\"}`. From a terminal: `anchor compare gpusmarket lambda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpusmarket.json and https://www.anchorterminal.com/api/v1/tools/lambda.json\n\n## Other comparisons with GPUsMarket or Lambda Cloud\n\n- [Baseten vs GPUsMarket](https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.md)\n- [Baseten vs Lambda Cloud](https://www.anchorterminal.com/compare/baseten-vs-lambda.md)\n- [Beam vs GPUsMarket](https://www.anchorterminal.com/compare/beam-vs-gpusmarket.md)\n- [Beam vs Lambda Cloud](https://www.anchorterminal.com/compare/beam-vs-lambda.md)\n- [Cerebrium vs GPUsMarket](https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket.md)\n- [Cerebrium vs Lambda Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-lambda.md)\n- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)\n- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md)\n- [CoreWeave vs GPUsMarket](https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.md)\n- [CoreWeave vs Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md)\n- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)\n- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)\n- [GPUsMarket vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/gpusmarket-vs-hugging-face-inference-endpoints.md)\n- [GPUsMarket vs Hyperbolic](https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic.md)\n- [GPUsMarket vs Koyeb](https://www.anchorterminal.com/compare/gpusmarket-vs-koyeb.md)\n- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)\n- [GPUsMarket vs Modal](https://www.anchorterminal.com/compare/gpusmarket-vs-modal.md)\n- [GPUsMarket vs Nebius AI Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud.md)\n- [GPUsMarket vs Northflank](https://www.anchorterminal.com/compare/gpusmarket-vs-northflank.md)\n- [GPUsMarket vs Replicate Deployments](https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.md)\n- [GPUsMarket vs Runpod](https://www.anchorterminal.com/compare/gpusmarket-vs-runpod.md)\n- [GPUsMarket vs Thunder Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Vast.ai](https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai.md)\n- [GPUsMarket vs Verda](https://www.anchorterminal.com/compare/gpusmarket-vs-verda.md)\n- [Hugging Face Inference Endpoints vs Lambda Cloud](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda.md)\n- [Hyperbolic vs Lambda Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-lambda.md)\n- [Koyeb vs Lambda Cloud](https://www.anchorterminal.com/compare/koyeb-vs-lambda.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.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 Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Vast.ai](https://www.anchorterminal.com/compare/lambda-vs-vast-ai.md)\n- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "GPUsMarket vs Lambda Cloud", "url": "" } ], "description": "Lambda Cloud scores 52.9 (D) to GPUsMarket's 39.6 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "GPUsMarket E 39.6", "Lambda Cloud D 52.9", "scores" ], "h1": "GPUsMarket vs Lambda Cloud", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gpusmarket-vs-lambda", "published": "2026-10-01", "section": "tools", "title": "GPUsMarket vs Lambda Cloud for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda" }, "tokens": { "markdown": 4800, "slim": 2680 }, "version": 1 }