{ "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": 1337, "ranked": true, "rankOf": 1510, "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-07T19:22:09.857483355Z", "lastOk": true, "lastStatus": 404, "lastMs": 168, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 159, "p95ms24h": 250, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "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-07T19:22:09.857483355Z" } }, "answer": "Thunder Compute scores 51.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing.", "b": { "slug": "thunder-compute", "name": "Thunder Compute", "vendor": "Thunder Compute", "vendorUrl": "https://www.thundercompute.com", "kind": "http-api", "category": "gpu-compute", "summary": "Thunder Compute is a US GPU cloud renting RTX A6000, L40, A100 and H100 instances by the minute and GPU sandboxes by the second. Agents use its REST API, a hosted MCP server with OAuth, or the `tnr` CLI.", "url": "https://www.anchorterminal.com/tools/thunder-compute", "markdownUrl": "https://www.anchorterminal.com/tools/thunder-compute.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/thunder-compute.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/thunder-compute.json", "dns": "thunder-compute.grade.anchorterminal.com", "repo": "https://github.com/Thunder-Compute/thunder-cli", "license": "Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.thundercompute.com:8443/v1", "packages": [ { "registry": "go", "name": "github.com/Thunder-Compute/thunder-cli" }, { "registry": "pypi", "name": "thunder-sandbox" } ], "auth": "mixed", "authNotes": "Self-serve. The hosted MCP server uses OAuth 2.0 with discovery. The first connection opens a browser to sign in and approve, tokens refresh, and the scopes are `instances:read`, `instances:write`, `snapshots:read`, `snapshots:write`, `sandboxes:read`, `sandboxes:write`, `billing:read` and `org:read`. The REST API takes a named API token as a Bearer header. Tokens are created and revoked one at a time in the console, or with the MCP `create_token` tool, and no token scopes were found. The CLI and the sandbox SDK read `TNR_API_TOKEN` for headless use. Price, specification, availability and template endpoints need no token.", "pricing": "usage", "pricingNotes": "No general free tier. Instances are billed by the minute while they run, paid by saved card or preloaded credit that is non-refundable. Per GPU an hour on 9 October 2026, RTX A6000 is $0.35, L40 $0.79, A100 80 GB $1.09 and H100 $3.20. Sandboxes are billed by the second and need access enabled by the vendor. Students with a US university email get $20 of credit for A6000 and L40 GPUs. Reserved capacity is by quote (https://www.thundercompute.com/pricing).", "priceSummary": "$0.04 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 28, "popularity": { "githubStars": 34, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.thundercompute.com/docs", "llmsTxt": "https://www.thundercompute.com/docs/llms.txt", "openapi": "https://api.thundercompute.com:8443/openapi.json", "registryName": "io.github.Thunder-Compute/thunder-compute", "capabilities": [ "compute.gpu", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "oauth", "api-key", "python", "go", "status-page", "card-required", "closed-source" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 51.3, "grade": "D", "agentReady": false, "rank": 1032, "ranked": true, "rankOf": 1510, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 48, "maintenance": 79, "payments": 20, "reliability": 65, "schema": 70, "security": 51, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -5, "negativeNotes": [ "-3, released fixes of described flaws with no advisory. The CLI's v2.1.0 (16 September 2026) changelog has a Security section that stops \"copying the local CLI authentication credential onto instances during connect\" and stops configuration and API URL overrides \"sending browser login credentials to a different API origin\". v2.0.71 (30 July) made the updater require verified checksums. OSV holds no record for thunder-cli (https://github.com/Thunder-Compute/thunder-cli/blob/main/CHANGELOG.md).", "-2, undisclosed default telemetry. Released CLI builds inject a Sentry DSN at build time, so error reports go to Sentry by default with a user ID derived from a hash of the API token, the machine's HOSTNAME as `instance_id`, OS, architecture and Go version, and tracing is enabled at a 10 per cent sample with request breadcrumbs. No opt-out was found in the CLI, its README or, per the 9 October check, the docs. The v2.2.0 changelog mentions \"released CLI error reports\" without describing them, and Sentry isn't on the sub-processor list (https://github.com/Thunder-Compute/thunder-cli/blob/main/main.go)." ], "verdict": "The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out.", "bestFor": "Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.", "strengths": [ "Hosted MCP server at `https://www.thundercompute.com/mcp` with OAuth and ten scopes that separate read from write for instances, snapshots and sandboxes", "Public OpenAPI 3.1 document with 41 operations, plus `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page", "Per-GPU-hour, per-vCPU-hour and storage prices are public on the pricing page", "Section 28 of the terms, dated 28 September 2026, permits access by AI agents, scripts and SDKs through the account holder's own credentials", "The `tnr` CLI had three code releases between 15 September and 27 October 2026, with a dated changelog" ], "weaknesses": [ "No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability", "`POST /instances/create` has no idempotency key, so a retried launch can start a second billed instance", "Instances cannot be stopped. Pausing means taking a snapshot, deleting the instance and restoring later", "No security.txt or disclosure policy was found, and the SOC 2 Type II claim in `llms.txt` has no report or trust page linked", "The CLI sends error reports to Sentry by default with a hashed token ID, and no opt-out was found", "Credential-handling fixes in CLI v2.1.0 (16 September 2026) shipped with no advisory" ], "agentNotes": [ "Call `GET /v2/status` or the `get_availability` tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.", "List instances before retrying a failed create, because the call has no idempotency key.", "Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.", "To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.", "For headless use set `TNR_API_TOKEN` to a token from the console, and upgrade the CLI to v2.1.0 or later, which stops copying that credential onto instances." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.3 } ], "editorialScores": { "ergonomics": 48, "maintenance": 79, "payments": 20, "reliability": 65, "schema": 70, "security": 51, "transparency": 51 }, "provenanceScore": 80, "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": { "install": "curl -fsSL https://raw.githubusercontent.com/Thunder-Compute/thunder-cli/main/scripts/install.sh | bash", "http": "curl https://api.thundercompute.com:8443/v2/pricing", "claudeCode": "claude mcp add --transport http thunder-compute https://www.thundercompute.com/mcp", "config": { "mcpServers": { "thunder-compute": { "url": "https://www.thundercompute.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/thunder-compute" }, "area": "models", "unitPrices": [ { "item": "RTX A6000 48 GB instance", "unit": "gpu-hour", "usd": 0.35, "note": "Billed per minute. One GPU per instance" }, { "item": "L40 48 GB instance", "unit": "gpu-hour", "usd": 0.79, "note": "Billed per minute" }, { "item": "A100 80 GB instance", "unit": "gpu-hour", "usd": 1.09, "note": "Billed per minute. 4 and 8 GPU shapes cost $1.49 a GPU per the price endpoint" }, { "item": "H100 80 GB instance", "unit": "gpu-hour", "usd": 3.2, "note": "Billed per minute" }, { "item": "H100 80 GB sandbox", "unit": "gpu-hour", "usd": 2.95, "note": "Billed per second, plus vCPU and memory. Access on request" }, { "item": "A100 80 GB sandbox", "unit": "gpu-hour", "usd": 1.95, "note": "Billed per second, plus vCPU and memory. Access on request" }, { "item": "Extra instance vCPU", "unit": "vcpu-hour", "usd": 0.04, "note": "Above the vCPUs included with each GPU" }, { "item": "Sandbox vCPU", "unit": "vcpu-hour", "usd": 0.051, "note": "Memory is $0.016 per GiB an hour" }, { "item": "Instance disk above 100 GB per GPU", "unit": "gb-month", "usd": 0.219, "note": "Billed only while the instance runs" }, { "item": "Snapshot storage", "unit": "gb-month", "usd": 0.05, "note": "Kept until deleted" } ], "provenance": { "legalEntity": "Thunder GPU, Inc.", "domain": "thundercompute.com", "domainRegistered": "2024-02-29", "endpointOnVendorDomain": true, "terms": "https://www.thundercompute.com/terms-and-conditions", "privacy": "https://www.thundercompute.com/privacy-policy", "statusPage": "https://status.thundercompute.com", "changelog": "https://github.com/Thunder-Compute/thunder-cli/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms and Conditions, last updated 28 September 2026, name Thunder GPU, Inc., doing business as Thunder Compute, a Delaware company, and apply Delaware law. They cover the site and the services, with sections on automated access, usage billing and instance data deletion.", "The privacy policy, last updated 28 September 2026, covers the website and the GPU platform, including access by AI agents.", "The API answers at api.thundercompute.com on port 8443, and the MCP server at www.thundercompute.com/mcp, both on the vendor domain.", "/.well-known/security.txt answers 404.", "RDAP for thundercompute.com gives a registration date of 2024-02-29.", "The changelog linked is the CLI's. No API changelog was found.", "A Data Processing Addendum is published in the docs and a sub-processor list on the site, last updated 27 August 2025." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/thunder-compute.json", "live": { "slug": "thunder-compute", "probe": { "target": "https://api.thundercompute.com:8443/v1", "method": "get", "lastAt": "2026-11-07T19:22:39.718670643Z", "lastOk": true, "lastStatus": 404, "lastMs": 238, "authRequired": false, "uptime24h": 100, "uptime30d": 99.89, "p50ms24h": 610, "p95ms24h": 715, "samples24h": 238, "samples30d": 7299, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "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": 252 }, { "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": 244 }, { "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": 247 }, { "date": "2026-10-28", "probes": 250, "ok": 249 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "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": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.thundercompute.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:23:50.038587335Z" }, "versions": [ { "registry": "github", "name": "Thunder-Compute/thunder-cli", "version": "v2.3.0", "released": "2026-11-05", "seenAt": "2026-11-07T00:11:24.374859251Z" }, { "registry": "mcp-registry", "name": "io.github.Thunder-Compute/thunder-compute", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "thunder-sandbox", "version": "0.7.11", "released": "2026-11-04", "seenAt": "2026-11-07T00:11:24.191658707Z" } ], "githubStars": 34, "pypiWeekly": 7292, "securityTxt": { "url": "https://thundercompute.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:02:02.689166619Z" }, "llmsTxt": { "url": "https://www.thundercompute.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:08.029305428Z" }, "domain": { "domain": "thundercompute.com", "registered": "2024-02-29", "source": "https://rdap.verisign.com/com/v1/domain/thundercompute.com", "checkedAt": "2026-11-01T14:19:55.118917218Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/Thunder-Compute/thunder-cli/main/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:19:37.649850655Z", "changedAt": "2026-11-05T13:04:01.9071579Z", "fingerprint": "e59bfd9db845" }, { "url": "https://www.thundercompute.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:35:36.789186909Z", "changedAt": "2026-11-07T14:35:36.789186909Z", "fingerprint": "adbd67a657df" }, { "url": "https://www.thundercompute.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:35:39.012108629Z", "changedAt": "2026-10-23T02:07:42.099244407Z", "fingerprint": "15f556e42b20" }, { "url": "https://www.thundercompute.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:35:41.000439019Z", "changedAt": "2026-10-23T02:07:44.212693674Z", "fingerprint": "bcc6d526ecf3" } ], "mcpTools": { "url": "https://www.thundercompute.com/mcp", "checkedAt": "2026-11-07T01:48:36.126087407Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:36.126087407Z" }, "github": { "repo": "thunder-compute/thunder-cli", "checkedAt": "2026-11-02T09:31:35.915022229Z", "stars": 34, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-27T23:09:19Z", "openIssues": 0, "openPRs": 2, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 12, "unanswered": 0, "medianDays": 2.3 } }, "updatedAt": "2026-11-07T19:23:50.038587335Z" } }, "edges": [ { "by": 32, "category": "reliability", "leads": "thunder-compute", "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": "Graded on the hosted lines for the REST API and the hosted MCP server. Thunder Compute's terms bar robots, scrapers and data-gathering tools on the Services, so its site, status page and API host weren't requested on 4 November and the readings below are per the 9 October check, not re-read on 4 November. Status page on incident.io at status.thundercompute.com with Website, API and Instances components and monthly history (20). No incidents listed for July to 9 October 2026. The rest of the window is unread and not credited, so the line keeps its recorded award (30). No rate limits with numbers were found in the docs or the OpenAPI document (0). No 429 or retry guidance in the docs. The CLI source reads a `Retry-After` header on errors, adding a duplicate SSH key is a no-op and port updates are atomic, but instance creation has no idempotency key (5 of 15, a partial value kept and flagged). No SLA found, and the terms say availability is not guaranteed (0). The API and MCP server carry no beta label (10). 20+30+0+5+0+10 = 65." }, "scores": { "a": 33, "b": 65 } }, { "by": 21, "category": "security", "leads": "thunder-compute", "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": "The MCP server uses OAuth 2.0 with discovery, refresh tokens and ten scopes that separate read from write for instances, snapshots and sandboxes. The REST API uses named API tokens that are created and revoked one at a time, with no scopes found. No secret travels in a URL (25 of 30). Read scopes exist, and the CLI requires `--yes` to delete without a prompt. No confirmation step for `delete_instance` or `delete_snapshot` was found in the MCP docs, and both are described as irreversible (8 of 20). Responses are infrastructure metadata, except `run_command` output and sandbox logs, with no guidance found on untrusted output (8 of 15). `GET /tokens` returns creation and last-used times and sandbox logs are listed by API. No audit log was found (4 of 15). No security.txt, disclosure policy or bug bounty was found. `llms.txt` states SOC 2 Type II and GDPR compliance with no report or trust page linked, and the DPA promises an audit summary on written request and incident notice within 72 hours (6 of 20). The site readings are per the 9 October check, not re-read on 4 November. 25+8+8+4+6 = 51." }, "scores": { "a": 30, "b": 51 } }, { "by": 18, "category": "schema", "leads": "thunder-compute", "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": "Public OpenAPI 3.1 document at api.thundercompute.com:8443/openapi.json with 41 operations and 72 schemas (25). `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page (10). 28 of 41 operations have a description. Instance operations state side effects such as the private key being returned once, while most sandbox operations have a summary only (12 of 20). Required fields are marked, but the document has six enums, `gpu_type` and `template` are free strings and the instance list is a map keyed by ID (8 of 15). 12 examples and one error schema with `code`, `error` and `message`. Most operations document 400, 401 and 500, and none documents 429 (9 of 15). `/v1` and `/v2` paths, with legacy endpoints and the `mode` field marked as retained or deprecated. No API changelog was found. The CLI has a dated one (6 of 15). No published copy of the MCP tool definitions was found, so they were not read. All of this is per the 9 October check, not re-read on 4 November. 25+10+12+8+9+6 = 70." }, "scores": { "a": 52, "b": 70 } }, { "by": 16, "category": "transparency", "leads": "thunder-compute", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service under Terms and Conditions dated 28 September 2026 and Delaware law. The CLI is MIT. The OpenAPI document names Apache 2.0 and a placeholder terms address (15 of 30). The privacy policy of 28 September 2026 says instance data is not used to train AI models, the terms say instance data may be deleted 60 days after the account was last active, and a DPA is published. The sub-processor list names Firebase for sign-in while the MCP docs name Stytch, and the FAQ says instances are EC2 while the list names Azure (18 of 30). No deprecation policy. The terms allow changes without notice, and the billing docs say rates can change without notice. Legacy endpoints are marked as retained for compatibility (6 of 20). Five sub-processors with locations are listed and the DPA sets 10 business days' notice of changes. The list is dated 27 August 2025 and omits Stytch and Sentry, which the MCP docs and the CLI source name (12 of 20). The site readings are per the 9 October check, not re-read on 4 November. 15+18+6+12 = 51." }, "scores": { "a": 50, "b": 66 } }, { "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 x402, MPP or L402 in the docs, the OpenAPI document or the pricing page (0). Per-GPU-hour, per-vCPU-hour and storage prices are public on the pricing page (20). No general free tier or trial. A $20 credit is limited to students with a US university email, and the MCP quickstart asks for a payment method before connecting (0). Signup and the first OAuth consent happen in a browser. `create_token` issues API tokens only after that sign-in (0). Per the 9 October check, not re-read on 4 November. 0+20+0+0 = 20." }, "scores": { "a": 30, "b": 20 } }, { "by": 10, "category": "maintenance", "leads": "thunder-compute", "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": "The newest CLI release is v2.2.0 of 27 October 2026, which adds `tnr report` and SSH and interface fixes (30). Three CLI releases in the 90 days from 6 August, v2.0.72 (15 September), v2.1.0 (16 September) and v2.2.0, each changing code (20). A dated CLI changelog, a support address and a Discord server the docs say the founders answer. No API changelog. GitHub issues weren't re-read (github.com refused), so 10 of 15 per the 9 October check. Listed in the official MCP registry as `io.github.Thunder-Compute/thunder-compute` per the 9 October check, and the CLI and the `thunder-sandbox` SDK are current (13 of 15). The CLI repository has tests, a lint configuration and release checksum verification, and still no CI workflow (`.github` holds only `copilot-instructions.md`) (6 of 10). 30+20+10+13+6 = 79." }, "scores": { "a": 69, "b": 79 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Tyga.Cloud Ltd", "b": "Thunder Compute", "name": "Vendor" }, { "a": "https://gpusmarket.com/api/v1", "b": "https://api.thundercompute.com:8443/v1", "name": "Hosted endpoint" }, { "a": "stdio, SSE (legacy)", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$0.219 per GB per month", "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": "Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT", "name": "Licence" }, { "a": "32", "b": "28", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.jyswee/gpusmarket", "b": "io.github.Thunder-Compute/thunder-compute", "name": "MCP registry" }, { "a": "2026-10-16", "b": "2026-10-27", "name": "Last release" }, { "a": "2026-06-01", "b": "2026-09-28", "name": "Terms last updated" }, { "a": "2026-03-01", "b": "2026-09-28", "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": "yes", "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": "34 stars", "name": "Popularity" } ], "faq": [ { "answer": "Thunder Compute scores 51.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing.", "question": "Which is better for AI agents, GPUsMarket or Thunder Compute?" }, { "answer": "GPUsMarket needs an API key. Thunder Compute takes an API key or an OAuth sign-in.", "question": "Do GPUsMarket and Thunder Compute need an API key?" }, { "answer": "Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Thunder Compute at https://api.thundercompute.com:8443/v1.", "question": "Can an agent call GPUsMarket and Thunder Compute without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 20" ], "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, 65 against 33", "Schema \u0026 documentation, 70 against 52", "Security \u0026 auth, 51 against 30", "Maintenance \u0026 community, 79 against 69", "Transparency \u0026 trust, 66 against 50" ], "also": null, "goodFor": "Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.", "slug": "thunder-compute", "watchFor": "No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability" } ], "history": { "gpusmarket": null, "thunder-compute": [ { "causes": [ "event" ], "date": "2026-11-04", "delta": -5, "from": 56.3, "fromGrade": "C", "to": 51.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 56.1, "fromGrade": "C", "to": 56.3, "toGrade": "C" } ] }, "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-thunder-compute.json", "title": "Baseten vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/baseten-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Beam vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/beam-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Cerebrium vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Cloud Run GPUs vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "CoreWeave vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Crusoe Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute" }, { "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-lambda.json", "title": "GPUsMarket vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda" }, { "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-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-thunder-compute.json", "title": "Hugging Face Inference Endpoints vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.json", "title": "Hyperbolic vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.json", "title": "Koyeb vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute" }, { "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/massed-compute-vs-thunder-compute.json", "title": "Massed Compute vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-thunder-compute.json", "title": "Modal vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/modal-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.json", "title": "Nebius AI Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.json", "title": "Northflank vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.json", "title": "Replicate Deployments vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.json", "title": "Runpod vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/runpod-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.json", "title": "Thunder Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.json", "title": "Thunder Compute vs Vast.ai", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.json", "title": "Thunder Compute vs Verda", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda" } ], "panel": null, "scores": [ { "by": 32, "edge": "thunder-compute", "gpusmarket": 33, "key": "reliability", "name": "Reliability", "thunder-compute": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "thunder-compute", "gpusmarket": 52, "key": "schema", "name": "Schema \u0026 documentation", "thunder-compute": 70, "weight": 13 }, { "by": 2, "edge": "gpusmarket", "gpusmarket": 50, "key": "ergonomics", "name": "Agent ergonomics", "thunder-compute": 48, "weight": 13 }, { "by": 21, "edge": "thunder-compute", "gpusmarket": 30, "key": "security", "name": "Security \u0026 auth", "thunder-compute": 51, "weight": 14 }, { "by": 10, "edge": "gpusmarket", "gpusmarket": 30, "key": "payments", "name": "Payments \u0026 pricing", "thunder-compute": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 10, "edge": "thunder-compute", "gpusmarket": 69, "key": "maintenance", "name": "Maintenance \u0026 community", "thunder-compute": 79, "weight": 7 }, { "by": 16, "edge": "thunder-compute", "gpusmarket": 50, "key": "transparency", "name": "Transparency \u0026 trust", "thunder-compute": 66, "weight": 7 } ], "summary": "Thunder Compute scores 51.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing. 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.", "thunder-compute": "The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute", "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.min.md" }, "markdown": "Thunder Compute scores 51.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing. Both do gpu compute.\n\n- 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\n- Thunder Compute: grade D, 51.3/100, rank #1032 of 1510. Markdown https://www.anchorterminal.com/tools/thunder-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/thunder-compute.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\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### Thunder Compute (D)\n\nGood for: Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.\n\nAhead on:\n- Reliability, 65 against 33\n- Schema \u0026 documentation, 70 against 52\n- Security \u0026 auth, 51 against 30\n- Maintenance \u0026 community, 79 against 69\n- Transparency \u0026 trust, 66 against 50\n\nWatch for: No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability\n\n\n## Why the edge\n\n### Reliability: Thunder Compute +32\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- Thunder Compute (65): Graded on the hosted lines for the REST API and the hosted MCP server. Thunder Compute's terms bar robots, scrapers and data-gathering tools on the Services, so its site, status page and API host weren't requested on 4 November and the readings below are per the 9 October check, not re-read on 4 November. Status page on incident.io at status.thundercompute.com with Website, API and Instances components and monthly history (20). No incidents listed for July to 9 October 2026. The rest of the window is unread and not credited, so the line keeps its recorded award (30). No rate limits with numbers were found in the docs or the OpenAPI document (0). No 429 or retry guidance in the docs. The CLI source reads a `Retry-After` header on errors, adding a duplicate SSH key is a no-op and port updates are atomic, but instance creation has no idempotency key (5 of 15, a partial value kept and flagged). No SLA found, and the terms say availability is not guaranteed (0). The API and MCP server carry no beta label (10). 20+30+0+5+0+10 = 65.\n\n### Security \u0026 auth: Thunder Compute +21\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- Thunder Compute (51): The MCP server uses OAuth 2.0 with discovery, refresh tokens and ten scopes that separate read from write for instances, snapshots and sandboxes. The REST API uses named API tokens that are created and revoked one at a time, with no scopes found. No secret travels in a URL (25 of 30). Read scopes exist, and the CLI requires `--yes` to delete without a prompt. No confirmation step for `delete_instance` or `delete_snapshot` was found in the MCP docs, and both are described as irreversible (8 of 20). Responses are infrastructure metadata, except `run_command` output and sandbox logs, with no guidance found on untrusted output (8 of 15). `GET /tokens` returns creation and last-used times and sandbox logs are listed by API. No audit log was found (4 of 15). No security.txt, disclosure policy or bug bounty was found. `llms.txt` states SOC 2 Type II and GDPR compliance with no report or trust page linked, and the DPA promises an audit summary on written request and incident notice within 72 hours (6 of 20). The site readings are per the 9 October check, not re-read on 4 November. 25+8+8+4+6 = 51.\n\n### Schema \u0026 documentation: Thunder Compute +18\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- Thunder Compute (70): Public OpenAPI 3.1 document at api.thundercompute.com:8443/openapi.json with 41 operations and 72 schemas (25). `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page (10). 28 of 41 operations have a description. Instance operations state side effects such as the private key being returned once, while most sandbox operations have a summary only (12 of 20). Required fields are marked, but the document has six enums, `gpu_type` and `template` are free strings and the instance list is a map keyed by ID (8 of 15). 12 examples and one error schema with `code`, `error` and `message`. Most operations document 400, 401 and 500, and none documents 429 (9 of 15). `/v1` and `/v2` paths, with legacy endpoints and the `mode` field marked as retained or deprecated. No API changelog was found. The CLI has a dated one (6 of 15). No published copy of the MCP tool definitions was found, so they were not read. All of this is per the 9 October check, not re-read on 4 November. 25+10+12+8+9+6 = 70.\n\n### Transparency \u0026 trust: Thunder Compute +16\n\n- 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.\n- Thunder Compute (66): Closed service under Terms and Conditions dated 28 September 2026 and Delaware law. The CLI is MIT. The OpenAPI document names Apache 2.0 and a placeholder terms address (15 of 30). The privacy policy of 28 September 2026 says instance data is not used to train AI models, the terms say instance data may be deleted 60 days after the account was last active, and a DPA is published. The sub-processor list names Firebase for sign-in while the MCP docs name Stytch, and the FAQ says instances are EC2 while the list names Azure (18 of 30). No deprecation policy. The terms allow changes without notice, and the billing docs say rates can change without notice. Legacy endpoints are marked as retained for compatibility (6 of 20). Five sub-processors with locations are listed and the DPA sets 10 business days' notice of changes. The list is dated 27 August 2025 and omits Stytch and Sentry, which the MCP docs and the CLI source name (12 of 20). The site readings are per the 9 October check, not re-read on 4 November. 15+18+6+12 = 51.\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- Thunder Compute (20): No x402, MPP or L402 in the docs, the OpenAPI document or the pricing page (0). Per-GPU-hour, per-vCPU-hour and storage prices are public on the pricing page (20). No general free tier or trial. A $20 credit is limited to students with a US university email, and the MCP quickstart asks for a payment method before connecting (0). Signup and the first OAuth consent happen in a browser. `create_token` issues API tokens only after that sign-in (0). Per the 9 October check, not re-read on 4 November. 0+20+0+0 = 20.\n\n### Maintenance \u0026 community: Thunder Compute +10\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- Thunder Compute (79): The newest CLI release is v2.2.0 of 27 October 2026, which adds `tnr report` and SSH and interface fixes (30). Three CLI releases in the 90 days from 6 August, v2.0.72 (15 September), v2.1.0 (16 September) and v2.2.0, each changing code (20). A dated CLI changelog, a support address and a Discord server the docs say the founders answer. No API changelog. GitHub issues weren't re-read (github.com refused), so 10 of 15 per the 9 October check. Listed in the official MCP registry as `io.github.Thunder-Compute/thunder-compute` per the 9 October check, and the CLI and the `thunder-sandbox` SDK are current (13 of 15). The CLI repository has tests, a lint configuration and release checksum verification, and still no CI workflow (`.github` holds only `copilot-instructions.md`) (6 of 10). 30+20+10+13+6 = 79.\n\n## Score by category\n\n| Category | Weight | GPUsMarket | Thunder Compute | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 65 | Thunder Compute +32 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 52 | 70 | Thunder Compute +18 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 48 | GPUsMarket +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 51 | Thunder Compute +21 |\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 | 79 | Thunder Compute +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 50 | 66 | Thunder Compute +16 |\n| Negative events | ≤15 | -3 | -5 | |\n| **Total** | | **39.6 · E** | **51.3 · D** | |\n\n## Facts side by side\n\n| Fact | GPUsMarket | Thunder Compute |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Tyga.Cloud Ltd | Thunder Compute |\n| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://api.thundercompute.com:8443/v1` |\n| Transports | stdio, SSE (legacy) | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | not published | $0.219 per GB per month |\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 | Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT |\n| Tools exposed | 32 | 28 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.jyswee/gpusmarket` | `io.github.Thunder-Compute/thunder-compute` |\n| Last release | 2026-10-16 | 2026-10-27 |\n| Terms last updated | 2026-06-01 | 2026-09-28 |\n| Privacy policy last updated | 2026-03-01 | 2026-09-28 |\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 | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 1 stars, 79 npm/wk | 34 stars |\n\n## How the scores have moved\n\n### GPUsMarket\n\nNo score change since it was listed.\n\n### Thunder Compute\n\n- -5.0 on 4 November 2026 (C to D): negative event\n- +0.2 on 27 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**Thunder Compute.** The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out.\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### Thunder Compute\n\n1. Call `GET /v2/status` or the `get_availability` tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.\n2. List instances before retrying a failed create, because the call has no idempotency key.\n3. Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.\n4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.\n5. For headless use set `TNR_API_TOKEN` to a token from the console, and upgrade the CLI to v2.1.0 or later, which stops copying that credential onto instances.\n\n## Questions\n\n### Which is better for AI agents, GPUsMarket or Thunder Compute?\n\nThunder Compute scores 51.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 5 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing.\n\n### Do GPUsMarket and Thunder Compute need an API key?\n\nGPUsMarket needs an API key. Thunder Compute takes an API key or an OAuth sign-in.\n\n### Can an agent call GPUsMarket and Thunder Compute without installing anything?\n\nYes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Thunder Compute at https://api.thundercompute.com:8443/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gpusmarket\", \"b\": \"thunder-compute\"}`. From a terminal: `anchor compare gpusmarket thunder-compute`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpusmarket.json and https://www.anchorterminal.com/api/v1/tools/thunder-compute.json\n\n## Other comparisons with GPUsMarket or Thunder Compute\n\n- [Baseten vs GPUsMarket](https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.md)\n- [Baseten vs Thunder Compute](https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.md)\n- [Beam vs GPUsMarket](https://www.anchorterminal.com/compare/beam-vs-gpusmarket.md)\n- [Beam vs Thunder Compute](https://www.anchorterminal.com/compare/beam-vs-thunder-compute.md)\n- [Cerebrium vs GPUsMarket](https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket.md)\n- [Cerebrium vs Thunder Compute](https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.md)\n- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)\n- [Cloud Run GPUs vs Thunder Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.md)\n- [CoreWeave vs GPUsMarket](https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.md)\n- [CoreWeave vs Thunder Compute](https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.md)\n- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)\n- [Crusoe Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.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 Lambda Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.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 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 Thunder Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-compute.md)\n- [Hyperbolic vs Thunder Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.md)\n- [Koyeb vs Thunder Compute](https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.md)\n- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)\n- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)\n- [Modal vs Thunder Compute](https://www.anchorterminal.com/compare/modal-vs-thunder-compute.md)\n- [Nebius AI Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.md)\n- [Northflank vs Thunder Compute](https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.md)\n- [Replicate Deployments vs Thunder Compute](https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.md)\n- [Runpod vs Thunder Compute](https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.md)\n- [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md)\n- [Thunder Compute vs Vast.ai](https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.md)\n- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-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 Thunder Compute", "url": "" } ], "description": "Thunder Compute scores 51.3 (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", "Thunder Compute D 51.3", "scores" ], "h1": "GPUsMarket vs Thunder Compute", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gpusmarket-vs-thunder-compute", "published": "2026-10-01", "section": "tools", "title": "GPUsMarket vs Thunder Compute for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute" }, "tokens": { "markdown": 5350, "slim": 3080 }, "version": 1 }