# GPUsMarket vs Lambda Cloud

> 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.

- Canonical: https://www.anchorterminal.com/compare/gpusmarket-vs-lambda
- Markdown: https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.md (~4,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

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 & pricing and maintenance & community. Both do gpu compute.

- 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
- 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
- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md
- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md

## Which one, for what

### GPUsMarket (E)

Good for: Cheap, short GPU rentals for open models behind an Ollama or OpenAI endpoint, where data sensitivity is low.

Ahead on:
- Payments & pricing, 30 against 20
- Maintenance & community, 69 against 5

Also in its favour:
- Runs on your own machine

Watch for: Peer rentals send prompts and outputs through individuals' hardware, with only the terms as protection

### Lambda Cloud (D)

Good 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.

Ahead on:
- Reliability, 55 against 33
- Schema & documentation, 69 against 52
- Agent ergonomics, 63 against 50
- Security & auth, 70 against 30
- Transparency & trust, 60 against 50

Also in its favour:
- No incidents deducted, where GPUsMarket loses 3 points for them

Watch for: No scale to zero, autoscaling or endpoints; an idle VM bills until terminated


## Why the edge

### Maintenance & community: GPUsMarket +64

- 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.
- 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.

### Security & auth: Lambda Cloud +40

- 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.
- 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.

### Reliability: Lambda Cloud +22

- 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.
- 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.

### Schema & documentation: Lambda Cloud +17

- 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.
- 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.

### Agent ergonomics: Lambda Cloud +13

- 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.
- 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.

### Payments & pricing: GPUsMarket +10

- 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.
- 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.

## Score by category

| Category | Weight | GPUsMarket | Lambda Cloud | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 33 | 55 | Lambda Cloud +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 52 | 69 | Lambda Cloud +17 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 63 | Lambda Cloud +13 |
| Security & auth | 14% (17.5 this run) | 30 | 70 | Lambda Cloud +40 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | GPUsMarket +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 69 | 5 | GPUsMarket +64 |
| Transparency & trust | 7% (8.8 this run) | 50 | 60 | Lambda Cloud +10 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **39.6 · E** | **52.9 · D** | |

## Facts side by side

| Fact | GPUsMarket | Lambda Cloud |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Tyga.Cloud Ltd | Lambda |
| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://cloud.lambda.ai/api/v1` |
| Transports | stdio, SSE (legacy) | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | not published | $9.86 per GPU-hour |
| x402 | no | no |
| 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 |
| Tools exposed | 32 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `io.github.jyswee/gpusmarket` | not listed |
| Last release | 2026-10-16 | none |
| Terms last updated | 2026-06-01 | 2025-08-01 |
| Privacy policy last updated | 2026-03-01 | 2026-01-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1 stars, 79 npm/wk | none |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### GPUsMarket

No score change since it was listed.

### Lambda Cloud

- +2.8 on 4 November 2026: product, new evidence
- +0.1 on 27 October 2026: checklist
- -0.1 on 8 October 2026: checklist

## 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 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.

## Before you call either

### GPUsMarket

1. Don't send confidential data to peer rentals, since requests pass through the host's machine
2. Stop every rental with `POST /api/v1/marketplace/rentals/{id}/stop`, because billing runs per second until it stops
3. Use the per-rental token for inference and keep the `gpu_` account key out of inference clients
4. Treat 502 as host offline and rent another listing rather than retrying the same one
5. Ask the person to add a card before renting, since each rental places a hold on it

### Lambda Cloud

1. Call `GET /instance-types` first and read `regions_with_capacity_available` before trying to launch
2. Space launch calls 12 seconds apart; a sixth in a minute returns 429 with `global/rate-limited`, so wait for the Retry-After interval
3. Branch on the error `code`, not the `message` or `suggestion`, which Lambda says may change
4. List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine
5. Terminate the instance in a `finally` block; billing runs by the minute until you do
6. Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring

## Questions

### Which is better for AI agents, GPUsMarket or Lambda Cloud?

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 & pricing and maintenance & community.

### Do GPUsMarket and Lambda Cloud need an API key?

Both need an API key.

### Can an agent call GPUsMarket and Lambda Cloud without installing anything?

Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Lambda Cloud at https://cloud.lambda.ai/api/v1.


## For agents

- 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
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "gpusmarket", "b": "lambda"}`. From a terminal: `anchor compare gpusmarket lambda`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpusmarket.json and https://www.anchorterminal.com/api/v1/tools/lambda.json

## Other comparisons with GPUsMarket or Lambda Cloud

- [Baseten vs GPUsMarket](https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.md)
- [Baseten vs Lambda Cloud](https://www.anchorterminal.com/compare/baseten-vs-lambda.md)
- [Beam vs GPUsMarket](https://www.anchorterminal.com/compare/beam-vs-gpusmarket.md)
- [Beam vs Lambda Cloud](https://www.anchorterminal.com/compare/beam-vs-lambda.md)
- [Cerebrium vs GPUsMarket](https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket.md)
- [Cerebrium vs Lambda Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-lambda.md)
- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)
- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md)
- [CoreWeave vs GPUsMarket](https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.md)
- [CoreWeave vs Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md)
- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)
- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)
- [GPUsMarket vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/gpusmarket-vs-hugging-face-inference-endpoints.md)
- [GPUsMarket vs Hyperbolic](https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic.md)
- [GPUsMarket vs Koyeb](https://www.anchorterminal.com/compare/gpusmarket-vs-koyeb.md)
- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)
- [GPUsMarket vs Modal](https://www.anchorterminal.com/compare/gpusmarket-vs-modal.md)
- [GPUsMarket vs Nebius AI Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud.md)
- [GPUsMarket vs Northflank](https://www.anchorterminal.com/compare/gpusmarket-vs-northflank.md)
- [GPUsMarket vs Replicate Deployments](https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.md)
- [GPUsMarket vs Runpod](https://www.anchorterminal.com/compare/gpusmarket-vs-runpod.md)
- [GPUsMarket vs Thunder Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.md)
- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)
- [GPUsMarket vs Vast.ai](https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai.md)
- [GPUsMarket vs Verda](https://www.anchorterminal.com/compare/gpusmarket-vs-verda.md)
- [Hugging Face Inference Endpoints vs Lambda Cloud](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda.md)
- [Hyperbolic vs Lambda Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-lambda.md)
- [Koyeb vs Lambda Cloud](https://www.anchorterminal.com/compare/koyeb-vs-lambda.md)
- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)
- [Lambda Cloud vs Modal](https://www.anchorterminal.com/compare/lambda-vs-modal.md)
- [Lambda Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud.md)
- [Lambda Cloud vs Northflank](https://www.anchorterminal.com/compare/lambda-vs-northflank.md)
- [Lambda Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.md)
- [Lambda Cloud vs Runpod](https://www.anchorterminal.com/compare/lambda-vs-runpod.md)
- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)
- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)
- [Lambda Cloud vs Vast.ai](https://www.anchorterminal.com/compare/lambda-vs-vast-ai.md)
- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp