# Cerebrium vs GPUsMarket

> Cerebrium scores 52.5 (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/cerebrium-vs-gpusmarket
- Markdown: https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket.md (~4,500 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

Cerebrium scores 52.5 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 4 of 7 scored categories. Both do gpu compute.

- Cerebrium: grade D, 52.5/100, rank #989 of 1510. Markdown https://www.anchorterminal.com/tools/cerebrium.md · JSON https://www.anchorterminal.com/api/v1/tools/cerebrium.json
- 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
- 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

### Cerebrium (D)

Good for: Teams serving their own models as real-time endpoints (voice, LLM, image) who want per-second billing, multi-region placement and a scriptable management API.

Ahead on:
- Reliability, 48 against 33
- Schema & documentation, 70 against 52
- Security & auth, 60 against 30
- Transparency & trust, 64 against 50

Watch for: `disable_auth` defaults to true, so a deployed endpoint answers without a token unless the owner changes it

### GPUsMarket (E)

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

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


## Why the edge

### Security & auth: Cerebrium +30

- Cerebrium (60): Service account tokens expire after up to one year (or never, if set to 0), are limited to 1 to 50 named projects and are revoked by deleting the account. Inference API keys are separate and can be deleted. No per-action scopes, and the CLI's SECURITY.md says tokens sit in plaintext in a config file with mode 0644 (20 of 30). Users have owner, member and billing roles, but tokens have no read-only form, and `disable_auth` defaults to true, so deployed endpoints answer without a token unless the owner changes it (5 of 20). Runs the owner's code and returns its output (10). Docs readings per the 8 October check, not re-read on 4 November. Audit log of 22 actions with actor, IP address and outcome, in the dashboard and over the API, on Standard (7 days) and Enterprise (30 days) only (12 of 15). SOC 2 Type II announced on 8 July 2026, HIPAA BAA on request, a trust centre, and disclosure to security@cerebrium.ai. No security.txt and no bug bounty found (13 of 20). No advisory for cerebrium on OSV on 4 November. 20 + 5 + 10 + 12 + 13 = 60.
- 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.

### Schema & documentation: Cerebrium +18

- Cerebrium (70): Public OpenAPI 3.0 spec for the management API with 94 operations on 73 paths. Deployed endpoints take whatever the owner's function defines (25). llms.txt and a .md twin of every docs page (10). Operation descriptions are one line each. The guides say when to use the protected tier, async runs or a custom runtime (12 of 20). Required fields are marked, but the spec has no enums (valid values such as member and billing sit in prose) and several arrays and objects are untyped (7 of 15). The guides carry many worked examples. The spec has no examples and documents only 400 and 401 errors with a `message` string (8 of 15). Paths are versioned v2, v3 and v4 and CLI releases are dated on GitHub, but the spec version is a fixed 1.0.0 and no platform changelog was found (8 of 15). Docs and spec per the 8 October check, not re-read on 4 November. 25 + 10 + 12 + 7 + 8 + 8 = 70.
- 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.

### Reliability: Cerebrium +15

- Cerebrium (48): Graded as a hosted service. Status page at status.cerebrium.ai with 11 components and 90 days of history, per the 8 October check, not re-read on 4 November (cerebrium.ai's terms bar robots and automatic means) (20). The 8 October reading covered the window to that day. Since 6 August it held degradations of 5 hours 7 minutes on 19 August (US, upstream) and 7 hours 20 minutes on 2 September (EU, provider network), both partial; 9 October to 4 November is unread, so the line keeps its recorded award (10). No request rate limits found. Plans publish concurrency caps of 5 GPUs and 500 containers on Hobby and 30 and 1,000 on Standard (5 of 15). No 429 or backoff guidance for callers found. Webhook forwarding retries failed deliveries and the docs ask for idempotent webhook receivers, partly met, kept (3 of 15). No SLA found. The 99.9 and 99.999 per cent uptime figures on the site are claims without terms (0). Endpoints, the CLI and the REST API are GA, while multi-region deployment and checkpointing are marked beta (10). Docs and status per the 8 October check, not re-read on 4 November. 20 + 10 + 5 + 3 + 0 + 10 = 48.
- 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.

### Transparency & trust: Cerebrium +14

- Cerebrium (64): Closed service with published terms. The CLI is MIT (20). The docs say request and log data is deleted after 7 days on Hobby and 30 on Standard, that customer data is not used for training, and that a DPA is available on request. The privacy policy gives no retention periods, the pricing page shows both 1 day and 7 days of log retention for Hobby, and the docs still say SOC 2 Type I (15 of 30). No deprecation policy or dated notices found (0). Regions and some providers (AWS regions, Crusoe, Nebius) are named in the docs and status page, and Datadog, BugSnag and Stripe are named in passing, but no subprocessor list was found. The CLI's BugSnag error reporting is on by default and sends the user ID from the token and the project ID; `cerebrium config telemetry disable`, `CEREBRIUM_TELEMETRY_DISABLED` and, since 24 August, `DO_NOT_TRACK` turn it off. Its enable help says no personal data is sent, which the user ID contradicts; that is charged once, as the misleading-claim deduction, not on this line (10 of 20). Docs and policies per the 8 October check, not re-read on 4 November; terms re-read on 4 November. 20 + 15 + 0 + 10 = 45.
- 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.

## Score by category

| Category | Weight | Cerebrium | GPUsMarket | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 48 | 33 | Cerebrium +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 52 | Cerebrium +18 |
| Agent ergonomics | 13% (16.2 this run) | 49 | 50 | GPUsMarket +1 |
| Security & auth | 14% (17.5 this run) | 60 | 30 | Cerebrium +30 |
| 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) | 65 | 69 | GPUsMarket +4 |
| Transparency & trust | 7% (8.8 this run) | 64 | 50 | Cerebrium +14 |
| Negative events | ≤15 | -2 | -3 | |
| **Total** | | **52.5 · D** | **39.6 · E** | |

## Facts side by side

| Fact | Cerebrium | GPUsMarket |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Cerebrium Inc. | Tyga.Cloud Ltd |
| Hosted endpoint | `https://rest.cerebrium.ai` | `https://gpusmarket.com/api/v1` |
| Transports | HTTP | stdio, SSE (legacy) |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Cerebrium's terms of service. The CLI is MIT | Proprietary. The gpusmarket CLI and gpusmarket-host packages ship under Tyga.Cloud Ltd licences that allow use only with the platform, as obfuscated JavaScript |
| Tools exposed | none | 32 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.jyswee/gpusmarket` |
| Last release | 2026-09-16 | 2026-10-16 |
| Terms last updated | no date given | 2026-06-01 |
| Privacy policy last updated | no date given | 2026-03-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | 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 | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 1 stars, 79 npm/wk |

## How the scores have moved

### Cerebrium

- -2.9 on 4 November 2026 (C to D): correction, time
- +0.1 on 27 October 2026: checklist

### GPUsMarket

No score change since it was listed.

## Verdicts

**Cerebrium.** Per-second GPU prices are public, a 94-operation OpenAPI spec covers the management API, and service account tokens expire and are limited to named projects. Deployed endpoints are callable without a token unless `disable_auth = false` is set, and no request rate limits, 429 handling or SLA were found in the reviewed documentation.

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

## Before you call either

### Cerebrium

1. Set `disable_auth = false` in `cerebrium.toml` before deploying. The default leaves the endpoint callable by anyone with the URL
2. Authenticate headless with `CEREBRIUM_SERVICE_ACCOUNT_TOKEN`. `cerebrium login` opens a browser
3. Raise `response_grace_period` for long work. It defaults to 15 minutes and async runs stop at 12 hours
4. Send `?async=true` to get a `run_id` with HTTP 202, and add `webhookEndpoint` because async calls return no result to the caller
5. Check the plan before choosing hardware. A100, H100, H200, B200 and RTX PRO 6000 need Standard, and `protected` compute bills at twice the listed rate

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

## Questions

### Which is better for AI agents, Cerebrium or GPUsMarket?

Cerebrium scores 52.5 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 4 of 7 scored categories.

### Can an agent call Cerebrium and GPUsMarket without installing anything?

Yes. Cerebrium has a hosted endpoint at https://rest.cerebrium.ai and GPUsMarket at https://gpusmarket.com/api/v1.


## For agents

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

## Other comparisons with Cerebrium or GPUsMarket

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

---

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