# GPUsMarket vs Replicate Deployments

> Replicate Deployments scores 65.2 (B) 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-replicate-deploy
- Markdown: https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.md (~5,150 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

Replicate Deployments scores 65.2 (B) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. Both do gpu compute.

- GPUsMarket: grade E, 39.6/100, rank #1337 of 1510. Markdown https://www.anchorterminal.com/tools/gpusmarket.md · JSON https://www.anchorterminal.com/api/v1/tools/gpusmarket.json
- Replicate Deployments: grade B, 65.2/100, rank #432 of 1510. Markdown https://www.anchorterminal.com/tools/replicate-deploy.md · JSON https://www.anchorterminal.com/api/v1/tools/replicate-deploy.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.

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

### Replicate Deployments (B)

Good for: Teams already calling Replicate's public models who want their own model behind the same API, MCP server and webhooks.

Ahead on:
- Reliability, 75 against 33
- Schema & documentation, 85 against 52
- Agent ergonomics, 73 against 50
- Security & auth, 40 against 30
- Maintenance & community, 78 against 69
- Transparency & trust, 79 against 50

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

Watch for: Private instances bill set-up and idle time, H100 at $5.49 an hour


## Why the edge

### Reliability: Replicate Deployments +42

- 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.
- Replicate Deployments (75): Replicate incidents post under a Replicate component on cloudflarestatus.com, and replicatestatus.com redirects to that page filtered to Replicate (20). The component's 90-day bars, read on 2 November, show 5 days with incidents, all in September 2026, and none since 28 September. Some third-party models couldn't scale out for 15 hours 41 minutes on 14 and 15 September, a Pruna-specific issue ran 20 hours on 17 September, backend services returned intermittent 500s for 1 hour 54 minutes on 24 September, and hot-swapped Flux models stuck for 17 minutes on 28 September. Each names a subset of models or intermittent errors, so each reads as partial, minor only (20). 600 prediction creates a minute, 3,000 a minute on other endpoints, and 6 a minute without a card, re-read on 2 November (15). A 429 body says when the limit resets ('resets in ~30s') and the error-code page gives retry advice per code, but there's no Retry-After header or idempotency guidance (10 of 15). No SLA found (0). Deployments are GA (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

### Schema & documentation: Replicate Deployments +33

- 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.
- Replicate Deployments (85): Public OpenAPI 3.1.0 at api.replicate.com/openapi.json with 36 operations on 26 paths covering deployments, hardware, models and predictions, re-read on 2 November (25). llms.txt with Markdown pages (10). Operation descriptions in the spec explain purpose with curl examples; deployment docs say when to use a deployment rather than a model version (16). Deployment fields are bounded (`min_instances` 0 to 5, `max_instances` 0 to 20, a 64-character version, a hardware SKU from GET /v1/hardware) (13). Examples throughout and 8 coded errors (E1001 out of memory, E6716 start timeout and others) with fixes; the HTTP error body format isn't described (11). Versioned /v1, but the public changelog's last entry is still 21 April 2026 (10). 25 + 10 + 16 + 13 + 11 + 10 = 85.

### Transparency & trust: Replicate Deployments +29

- GPUsMarket (50): Closed, under Tyga.Cloud licences that are clear on use, but the docs call gpusmarket-host MIT open source while the package says otherwise (10). The privacy policy gives retention periods and names Stripe and MongoDB, while renter data on peer hosts falls outside its controls, which the terms disclaim (15). The terms promise 30 days' notice of material changes, with no deprecation policy or dated notices found (5). Processors partly named, with transfers under SCCs, and no host locations shown in the docs read (6). 10+15+5+6 = 36.
- Replicate Deployments (79): Closed service; Cog is Apache-2.0 (20). API prediction inputs, outputs, files and logs are deleted after one hour by default, web predictions are kept until deleted, and a subprocessor page is published, per the 1 October check, not re-read on 2 November (22). Dated deprecations in the changelog (streaming default in July 2024, spend limits in July 2025) but no written policy (12). Subprocessors listed; data locations not stated in what we read (15). 20 + 22 + 12 + 15 = 69.

### Agent ergonomics: Replicate Deployments +23

- 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.
- Replicate Deployments (73): The MCP server exposes one tool per HTTP operation and has an experimental code mode that collapses them into two tools (search the SDK docs, run TypeScript) (20). List responses page with `next` and `previous` cursor URLs, the predictions list filters by `created_after`, `created_before` and `source`, and the models list sorts, but there is no page size or field selection (15 of 20; was 10, pagination not verified on 1 October). Coded errors with suggested fixes, `detail` messages on HTTP errors (15). No idempotency keys; `Prefer: wait`, a `Cancel-After` header, webhooks and cancel cut polling, and a failed run still bills its active time (8). Sensible defaults (`min_instances` 0 allowed) and official Python and JavaScript clients plus Cog (15). 20 + 15 + 15 + 8 + 15 = 73.

### Security & auth: Replicate Deployments +10

- 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.
- Replicate Deployments (40): Bearer tokens starting `r8_`, several per account, each can be disabled; no scopes or expiry, re-read on 2 November (20). No read-only or per-model token; every token can create, update and delete deployments (0). Returns your own model's output (10). No audit log or per-token usage view found; predictions are listed per account (5). Replicate scans public GitHub for leaked tokens, disables them and emails the owner. replicate.com/.well-known/security.txt answers 404, and no bug bounty or certification was found in the docs we read. OSV lists no advisory for the `replicate` packages, `replicate-mcp` or Cog (5). 20 + 0 + 10 + 5 + 5 = 40.

### Maintenance & community: Replicate Deployments +9

- 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.
- Replicate Deployments (78): Cog, the listing's repository, tagged v0.23.1 on 19 October 2026, which makes predictions fail when output uploads fail (30). Cog tagged v0.22.0 on 13 August, v0.23.0 on 22 September and v0.23.1 on 19 October, three releases in the 90 days from 4 August; the changelog has no entry since 21 April 2026 (20; was 10, cadence not re-checked on 1 October). Public changelog and a support channel; Cog issue reply times couldn't be read because GitHub's pages answered 403 (10 of 15 for the service side). Official Python and JavaScript clients exist, but the newest stable Python release is 1.0.7 (27 May 2025) with 2.0 betas to 18 December 2025, and the JavaScript client's newest tag is 1.4.0 (17 November 2025). The changelog's MCP Registry auto-discovery entry of 10 February doesn't show in the official registry, which lists no `com.replicate` server on 2 November (10 of 15; was 15). Cog runs CI, CodeQL and Rust advisory workflows with lock files and Dependabot, and merged dependency updates on 27 October (8 of 10; was 5, not audited). 30 + 20 + 10 + 10 + 8 = 78.

## Score by category

| Category | Weight | GPUsMarket | Replicate Deployments | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 33 | 75 | Replicate Deployments +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 52 | 85 | Replicate Deployments +33 |
| Agent ergonomics | 13% (16.2 this run) | 50 | 73 | Replicate Deployments +23 |
| Security & auth | 14% (17.5 this run) | 30 | 40 | Replicate Deployments +10 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 69 | 78 | Replicate Deployments +9 |
| Transparency & trust | 7% (8.8 this run) | 50 | 79 | Replicate Deployments +29 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **39.6 · E** | **65.2 · B** | |

## Facts side by side

| Fact | GPUsMarket | Replicate Deployments |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Tyga.Cloud Ltd | Replicate |
| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://api.replicate.com/v1` |
| Transports | stdio, SSE (legacy) | HTTP, SSE (legacy), stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| 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 | Apache-2.0 |
| Tools exposed | 32 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.jyswee/gpusmarket` | not listed |
| Last release | 2026-10-16 | 2026-10-19 |
| Terms last updated | 2026-06-01 | 2026-04-01 |
| Privacy policy last updated | 2026-03-01 | 2026-04-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 | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1 stars, 79 npm/wk | 9.5k stars, 634k npm/wk, 387k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### GPUsMarket

No score change since it was listed.

### Replicate Deployments

- +1.5 on 2 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.

**Replicate Deployments.** OpenAPI file, llms.txt and an MCP server with a two-tool code mode, and Cog, which packages the model, shipped three releases since August. Private instances bill set-up and idle time, H100 at $5.49 an hour, and the changelog has been silent since April 2026.

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

### Replicate Deployments

1. List `GET /v1/hardware` first and use the returned `sku` in the deployment body
2. Set `min_instances` to 0 for bursty work; a warm H100 bills $5.49 an hour whether called or not
3. Send `Prefer: wait` on deployment predictions to block instead of polling
4. Copy outputs within an hour; API prediction data is deleted after that
5. Wait for the reset time in the 429 body before retrying; prediction creates cap at 600 a minute

## Questions

### Which is better for AI agents, GPUsMarket or Replicate Deployments?

Replicate Deployments scores 65.2 (B) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories.

### Do GPUsMarket and Replicate Deployments need an API key?

Both need an API key.

### Can an agent call GPUsMarket and Replicate Deployments without installing anything?

Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Replicate Deployments at https://api.replicate.com/v1.

### Are GPUsMarket and Replicate Deployments open source?

No open-source release is listed for GPUsMarket. Replicate Deployments is open source (Apache-2.0).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gpusmarket-vs-replicate-deploy.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "gpusmarket", "b": "replicate-deploy"}`. From a terminal: `anchor compare gpusmarket replicate-deploy`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpusmarket.json and https://www.anchorterminal.com/api/v1/tools/replicate-deploy.json

## Other comparisons with GPUsMarket or Replicate Deployments

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

---

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