{ "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": "Verda scores 53.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing.", "b": { "slug": "verda", "name": "Verda", "vendor": "Verda", "vendorUrl": "https://verda.com", "kind": "http-api", "category": "gpu-compute", "summary": "Verda, formerly DataCrunch, is a Finnish GPU cloud renting GPU and CPU instances, clusters, serverless containers and storage. Agents use its REST API, Python and Go SDKs, or a CLI with a built-in MCP server in beta.", "url": "https://www.anchorterminal.com/tools/verda", "markdownUrl": "https://www.anchorterminal.com/tools/verda.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/verda.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/verda.json", "dns": "verda.grade.anchorterminal.com", "repo": "https://github.com/verda-cloud/verda-cli", "license": "Proprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.verda.com/v1", "packages": [ { "registry": "pypi", "name": "verda" }, { "registry": "go", "name": "github.com/verda-cloud/verdacloud-sdk-go" } ], "auth": "oauth", "authNotes": "Self-serve. A signed-in user creates a Client ID and Client Secret on the console's Credentials page, and the secret is shown once. `POST /v1/oauth2/token` with the client credentials grant returns an access token valid for 3,600 seconds and a refresh token, both with the scope `cloud-api-v1`. Credentials belong to the member who created them and are deleted when that member leaves the project. The CLI and its MCP server read the same pair from `~/.verda/credentials` after `verda auth login`. A few catalogue endpoints such as `GET /v1/instance-types` need no token.", "pricing": "usage", "pricingNotes": "No free tier or trial. Accounts are prepaid by card or bank transfer, and Pay As You Go is charged in prepaid 10-minute increments with the unused part refunded. On-demand prices per GPU an hour on 2 November 2026 include H100 80 GB at $4.841, H200 at $6.313, B200 at $8.958, B300 at $11.46 and A100 80 GB at $2.27, with spot at half, up about 19 to 25 per cent in dollars from 8 October with no notice found. Dollar prices follow the euro list price (H100 €4.333) and move with the exchange rate, so part of the rise may be currency. Reserved terms take 2 to 25 per cent off, per the 8 October check. Serverless containers bill per minute of replica use. Free credits are granted only for approved blog posts or videos (https://verda.com/pricing).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 18, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 10461, "asOf": "2026-10-08" }, "docsUrl": "https://docs.verda.com", "llmsTxt": "https://docs.verda.com/llms.txt", "openapi": "https://api.verda.com/v1/openapi.json", "capabilities": [ "compute.gpu", "compute.serverless", "compute.endpoints", "compute.batch", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "oauth", "python", "go", "terraform", "status-page", "soc2", "europe" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 53.3, "grade": "D", "agentReady": false, "rank": 952, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 83, "payments": 20, "reliability": 60, "schema": 72, "security": 68, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -9, "negativeNotes": [ "2026-03-23, making `location_code` required on `POST /v1/instances`, `POST /v1/clusters` and `POST /v1/volumes`. Requests that had defaulted to FIN-01 began returning 400. The API changelog heads the change 23 March 2026 and records no advance notice. Documented, so 3 points (https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md).", "Released fixes with no advisory, -3. Python SDK `verda` 1.24.1 (12 August 2026) lists under Security a fixed path traversal in which a resource name containing `../` retargeted a call at another endpoint under the SDK's credentials (`containers.delete_deployment('../../v1/instances')` issued `DELETE /v1/instances`), and the API changelog of 20 March 2026 says API tokens \"could access internal endpoints not intended for external use\" before scopes were added. OSV holds no advisory for PyPI `verda` or the Go SDK on 2 November 2026. One folded term (https://github.com/verda-cloud/sdk-python/blob/master/CHANGELOG.md, https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/index.md).", "Unreleased fix, -3. Commit 42f054d in verda-cloud/sdk-python (29 October 2026, \"security: check the inference request path\") says a path built from untrusted input could add query parameters or a fragment to a request that carries the inference key, and that `..;/` and `..%252f` passed the old check. It sits under `[Unreleased]` in the changelog, after 1.25.0 of 23 October (https://github.com/verda-cloud/sdk-python/commit/42f054d)." ], "verdict": "Verda documents its API changes in a dated changelog, publishes hourly GPU prices, and its CLI's MCP server refuses billed or destructive calls without `confirm: true`. Access needs a browser signup and a prepaid balance, credentials carry one scope, instance creation has no idempotency key, and two SDK security fixes in 2026 came without an advisory or release.", "bestFor": "Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP.", "strengths": [ "`llms.txt` files on two hosts and the whole docs corpus as Markdown, with a dated API changelog of 24 entries in 2026", "Official Python and Go SDKs, a Terraform provider and a CLI, each released between 22 and 28 October 2026", "Hourly prices for every GPU type published in USD and EUR without a login, with spot at half the on-demand rate", "Audit log endpoint in CloudEvents 1.0 format covering 90 days, with the caller's IP address and origin on resource events", "The 18-tool MCP server refuses `create_vm`, `create_volume` and destructive `vm_action` calls unless `confirm: true` is passed" ], "weaknesses": [ "No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero", "Cloud API credentials carry one scope, `cloud-api-v1`, with no read-only credential found in the reviewed documentation", "`POST /v1/instances` has no idempotency key, so a retried launch can start a second billed instance", "The MCP server is marked beta and its tools carry no read-only or destructive annotations", "No SLA was found, and the terms give no warranty of uninterrupted availability", "The Python SDK fixed a path traversal in 1.24.1 and an inference-path flaw on 29 October 2026 with no advisory, the second in no release yet" ], "agentNotes": [ "Exchange the client ID and secret at `POST /v1/oauth2/token`, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.", "Send `location_code` on every create call. Requests without it have returned 400 since March 2026.", "Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.", "List instances before retrying a failed launch, because create has no idempotency key.", "Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.3 } ], "editorialScores": { "ergonomics": 63, "maintenance": 83, "payments": 20, "reliability": 60, "schema": 72, "security": 68, "transparency": 57 }, "provenanceScore": 95, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "brew install verda-cloud/tap/verda-cli", "http": "curl -X POST https://api.verda.com/v1/oauth2/token -H \"Content-Type: application/json\" -d '{\"grant_type\":\"client_credentials\",\"client_id\":\"\u003cYOUR_CLIENT_ID\u003e\",\"client_secret\":\"\u003cYOUR_CLIENT_SECRET\u003e\"}'", "config": { "mcpServers": { "verda": { "args": [ "mcp", "serve" ], "command": "verda" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/verda" }, "area": "models", "unitPrices": [ { "item": "H100 SXM5 80 GB, on-demand", "unit": "gpu-hour", "usd": 4.841, "note": "Spot $2.421. Billed in prepaid 10-minute increments" }, { "item": "H200 SXM5 141 GB, on-demand", "unit": "gpu-hour", "usd": 6.313, "note": "Spot $3.157" }, { "item": "B200 SXM6 180 GB, on-demand", "unit": "gpu-hour", "usd": 8.958, "note": "Spot $4.479" }, { "item": "B300 SXM6 268 GB, on-demand", "unit": "gpu-hour", "usd": 11.46, "note": "Spot $5.73" }, { "item": "A100 SXM4 80 GB, on-demand", "unit": "gpu-hour", "usd": 2.27, "note": "Spot $1.135" }, { "item": "L40S 48 GB, on-demand", "unit": "gpu-hour", "usd": 1.92, "note": "Spot $0.96" }, { "item": "H100 SXM5 80 GB, serverless container", "unit": "gpu-hour", "usd": 5.33, "note": "Spot $2.66. Billed per minute of replica use" }, { "item": "NVMe block volume or shared filesystem", "unit": "gb-month", "usd": 0.2, "note": "Per GiB" } ], "provenance": { "legalEntity": "DataCrunch Oy", "domain": "verda.com", "domainRegistered": "1998-05-22", "endpointOnVendorDomain": true, "terms": "https://verda.com/terms-and-conditions", "privacy": "https://verda.com/privacy-policy", "statusPage": "https://status.verda.com", "changelog": "https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Terms of Service, last updated 30 September 2025, name the supplier as Verda (DataCrunch Oy), apply Finnish law and set arbitration in Helsinki. They include the data processing terms.", "The CLI source carries the copyright of Verda Cloud Oy.", "The API answers at api.verda.com, a subdomain of the vendor domain.", "security.txt expires on 31 December 2026, lists security@verda.com and a policy at https://vdp.verda.com.", "RDAP for verda.com gives a registration date of 1998-05-22. The company took the Verda name later, and verda.com/llms.txt says it was previously known as DataCrunch.", "The privacy policy covers the website and the services and shows no readable date." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/verda.json", "live": { "slug": "verda", "probe": { "target": "https://api.verda.com/v1", "method": "get", "lastAt": "2026-11-07T19:22:42.939055171Z", "lastOk": true, "lastStatus": 401, "lastMs": 84, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.93, "p50ms24h": 100, "p95ms24h": 188, "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": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 254 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 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": 247 }, { "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.verda.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:56.698835616Z" }, "versions": [ { "registry": "github", "name": "verda-cloud/verda-cli", "version": "v1.10.0", "released": "2026-11-06", "seenAt": "2026-11-07T00:15:17.154297899Z" }, { "registry": "pypi", "name": "verda", "version": "1.25.0", "released": "2026-10-23", "seenAt": "2026-11-07T00:15:16.973607792Z" } ], "githubStars": 16, "pypiWeekly": 9525, "securityTxt": { "url": "https://verda.com/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T11:59:00Z", "checkedAt": "2026-11-07T16:00:49.972736209Z" }, "llmsTxt": { "url": "https://docs.verda.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:16.894348703Z" }, "domain": { "domain": "verda.com", "registered": "1998-05-22", "source": "https://rdap.verisign.com/com/v1/domain/verda.com", "checkedAt": "2026-11-01T14:13:48.625189825Z" }, "pages": [ { "url": "https://docs.verda.com/welcome-to-verda/release-notes/verda-api-changes/", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:08:35.488323411Z", "changedAt": "2026-11-05T12:32:20.917395122Z", "fingerprint": "edd04ebbd363" }, { "url": "https://verda.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:23:19.050824521Z", "changedAt": "2026-11-07T14:23:19.050824521Z", "fingerprint": "1777e38584d3" }, { "url": "https://verda.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:23:21.35557714Z", "changedAt": "2026-11-07T14:23:21.35557714Z", "fingerprint": "bcf01daa54c0" }, { "url": "https://verda.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:23:23.638199688Z", "changedAt": "2026-11-07T14:23:23.638199688Z", "fingerprint": "95ec6c6c21ba" } ], "github": { "repo": "verda-cloud/verda-cli", "checkedAt": "2026-11-02T09:35:54.540508327Z", "stars": 16, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-28T16:20:14Z", "openIssues": 1, "openPRs": 0, "issuesOpened90d": 1, "issuesClosed90d": 1, "prsMerged90d": 9, "ci": { "branch": "main", "runs": 50, "success": 48, "failure": 2, "other": 0, "latest": "success", "latestAt": "2026-10-28T16:20:17Z" }, "replies": { "sampled": 4, "unanswered": 1, "medianDays": 2.2 } }, "updatedAt": "2026-11-07T19:22:42.939055171Z" } }, "edges": [ { "by": 38, "category": "security", "leads": "verda", "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": "OAuth 2.0 client credentials. Access tokens expire after 3,600 seconds, credentials are deleted when their creator leaves the project, and every token carries the single scope `cloud-api-v1`. No secret travels in a URL (20 of 30). Credentials follow their creator's role of owner, admin or developer, and no read-only credential was found. The MCP server and the CLI's `--agent` mode require explicit confirmation for billed and destructive actions, and deleted volumes sit in trash for 96 hours (10 of 20). Responses are infrastructure metadata, apart from container logs (10). Audit log in the console and at `GET /v1/audit/log`, 90 days in CloudEvents format with IP address and origin, marked beta (14 of 15). security.txt is valid until 31 December 2026 and names a disclosure policy at vdp.verda.com. The home page states SOC 2 Type II and ISO 27001, 27017, 27018 and 27701. The trust centre and the policy page are drawn by script and we couldn't read them, and no bug bounty was found (14 of 20)." }, "scores": { "a": 30, "b": 68 } }, { "by": 27, "category": "reliability", "leads": "verda", "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. BetterStack page at status.verda.com with 21 components, 180-day bars and an RSS feed (20). The feed lists eight incidents from 4 August to 2 November 2026, none posted against the API component and each limited to one product, one location or some customers. Serverless Containers were slow or unavailable for about 9.5 hours on 13 August, the container gateway returned intermittent 500s on 4 September, container uploads failed for about 2 hours on 20 September, a small number of instances, volumes and billing records were affected on 25 September, Serverless Containers degraded during a security update on 9 October, FIN03 services and Google SSO sign-in failed during maintenance on 11 October, the container registry vccr.io was down on 19 October, and FIN-02 lost network connectivity on 23 October. This run reads all of them as partial, minor only (20). api.verda.com, which hosts the API reference with the rate limits, answered robots.txt with 401 on 2 November 2026, so the 8 October readings from its OpenAPI document are struck. The docs' changelog says rate limits apply since 11 March 2026 and points to that reference, with no numbers on a page we can read (0). The official Go SDK's retry middleware backs off on 429 and 5xx, instance actions already in the requested state answer 204 and volume deletion is idempotent per the docs' changelog, and serverless job request IDs answer 409 on a repeat, but instance creation has no idempotency key and Retry-After is documented only on the refused host (10 of 15). No SLA found, and the terms give no warranty of uninterrupted availability (0). The REST API is generally available, while the CLI's MCP server is marked beta (10)." }, "scores": { "a": 33, "b": 60 } }, { "by": 26, "category": "transparency", "leads": "verda", "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 of Service dated 30 September 2025 and Finnish law. The CLI and SDKs are Apache-2.0 (15 of 30). The terms include data processing terms, and the privacy policy has a retention table. Deleted customer data is removed within 96 hours per the privacy policy and clause 10.9.2, while Schedule 3 of the same terms says 72 hours. The privacy policy shows no readable date (20 of 30). No deprecation policy with a notice period. HDD volumes were announced as deprecated in April 2026 before creation was blocked on 21 September (10 of 20). The docs name three data centres in Helsinki, the terms promise 15 days' notice of a new sub-processor, and the privacy policy names Front and Stripe. The sub-processor list is drawn by script and we couldn't read it (12 of 20)." }, "scores": { "a": 50, "b": 76 } }, { "by": 20, "category": "schema", "leads": "verda", "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": "api.verda.com's robots.txt answered 401 on 2 November 2026, so the OpenAPI document and the API reference there weren't read and the 8 October counts taken from them (112 operations, 156 schemas, 104 enums, 756 examples) are struck. The docs' changelog names the OpenAPI specification and its schemas (oneOf for UUID-or-array fields, the 19 March 2026 auth fix), and the Go and Python SDKs carry typed models, but no per-operation reference is readable on an allowed host (20 of 25). `llms.txt` on verda.com and docs.verda.com, every docs page as Markdown and the corpus in `llms-full.txt` (10). Docs guides and changelog entries describe what endpoints do and their billing effects, for example that `shutdown` keeps charging, while the reference descriptions are unread (10 of 20). Required fields and enums are visible only through the SDKs' typed models and validation, such as the Go SDK's limits added in v1.7.0, and the docs ask clients to treat enums as open (8 of 15). The docs corpus carries 62 curl examples and the Python SDK lists seven error codes, while per-operation error responses sit in the unread reference (9 of 15). Versioned in the path, with a dated changelog of 24 entries in 2026, the newest on 7 October (15)." }, "scores": { "a": 52, "b": 72 } }, { "by": 14, "category": "maintenance", "leads": "verda", "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": "Dated sources counted on 2 November. Go SDK `verdacloud-sdk-go` v1.7.0 on 28 October 2026, Python SDK `verda` 1.25.0 on 23 October, CLI v1.9.0 on 22 October, and the newest API changelog entry on 7 October (30). 11 dated API entries from 11 September to 7 October 2026, plus Go SDK v1.4.3, v1.5.0, v1.6.0, v1.6.1, v1.6.2 and v1.7.0, Python SDK 1.24.1 and 1.25.0 and CLI v1.8.1, v1.8.2 and v1.9.0 in the 90 days (20). A public changelog, monthly release notes, email and chat support and a forum. GitHub issues were not read (10 of 15). Current official clients for Python and Go, a Terraform provider and a CLI (15). The CLI repository runs lint, test and security workflows, and the Go SDK added a go fix check on 27 October 2026 (8 of 10)." }, "scores": { "a": 69, "b": 83 } }, { "by": 13, "category": "ergonomics", "leads": "verda", "name": "Agent ergonomics", "reasons": { "a": "API and MCP reading. The README counts 32 MCP tools, and the decoded package includes 16 operator admin tools besides the renter tools, with no toolsets (5). Marketplace search takes `limit`, `offset`, `sort` and filters for GPU, price, VRAM, model, instance and workload type (20). Status codes with a one-line meaning each, no error bodies documented (10). No idempotency key on rent or deploy; stop and destroy return a cost summary (5). Only a Node CLI, though every proxy speaks the Ollama and OpenAI formats so existing SDKs work (10). 5+20+10+5+10 = 50.", "b": "Read from the docs' changelog and the SDKs on 2 November, since the API reference host refuses our reader. No field selection, and instance and volume lists return whole arrays (12 of 25). `page` and `pageSize` with totals in `X-Total-Count` on scripts and journals, a cursor on the audit log, and status, tag and location filters on other lists, but no pagination on instances or volumes (12 of 20). Errors carry a stable `code` and a `message`, and bulk actions return per-item results with 207 (16). Actions that are already in the requested state return 204 and volume deletion is idempotent, but create calls have no idempotency key. The MCP tools require `confirm: true` for billed and destructive calls and carry no read-only or destructive annotations (10 of 20). Official SDKs for Python and Go, a Terraform provider and a CLI. A launch needs an instance type, image, hostname, SSH key and location (13 of 15)." }, "scores": { "a": 50, "b": 63 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Tyga.Cloud Ltd", "b": "Verda", "name": "Vendor" }, { "a": "https://gpusmarket.com/api/v1", "b": "https://api.verda.com/v1", "name": "Hosted endpoint" }, { "a": "stdio, SSE (legacy)", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "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 Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0", "name": "Licence" }, { "a": "32", "b": "18", "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": "not listed", "name": "MCP registry" }, { "a": "2026-10-16", "b": "2026-10-28", "name": "Last release" }, { "a": "2026-06-01", "b": "2025-09-30", "name": "Terms last updated" }, { "a": "2026-03-01", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1 stars, 79 npm/wk", "b": "10k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Verda scores 53.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing.", "question": "Which is better for AI agents, GPUsMarket or Verda?" }, { "answer": "GPUsMarket needs an API key. Verda uses an OAuth sign-in.", "question": "Do GPUsMarket and Verda need an API key?" }, { "answer": "Yes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Verda at https://api.verda.com/v1.", "question": "Can an agent call GPUsMarket and Verda without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 20" ], "also": null, "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, 60 against 33", "Schema \u0026 documentation, 72 against 52", "Agent ergonomics, 63 against 50", "Security \u0026 auth, 68 against 30", "Maintenance \u0026 community, 83 against 69", "Transparency \u0026 trust, 76 against 50" ], "also": null, "goodFor": "Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP.", "slug": "verda", "watchFor": "No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero" } ], "history": { "gpusmarket": null, "verda": [ { "causes": [ "security", "evidence" ], "date": "2026-11-02", "delta": -9, "from": 62.3, "fromGrade": "B", "to": 53.3, "toGrade": "D" } ] }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.json", "title": "Baseten vs GPUsMarket", "url": "https://www.anchorterminal.com/compare/baseten-vs-gpusmarket" }, { "json": "https://www.anchorterminal.com/compare/baseten-vs-verda.json", "title": "Baseten vs Verda", "url": "https://www.anchorterminal.com/compare/baseten-vs-verda" }, { "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-verda.json", "title": "Beam vs Verda", "url": "https://www.anchorterminal.com/compare/beam-vs-verda" }, { "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-verda.json", "title": "Cerebrium vs Verda", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-verda" }, { "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/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-verda.json", "title": "CoreWeave vs Verda", "url": "https://www.anchorterminal.com/compare/coreweave-vs-verda" }, { "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-verda.json", "title": "Crusoe Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda" }, { "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-thunder-compute.json", "title": "GPUsMarket vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.json", "title": "GPUsMarket vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai.json", "title": "GPUsMarket vs Vast.ai", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.json", "title": "Hugging Face Inference Endpoints vs Verda", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda.json", "title": "Hyperbolic vs Verda", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-verda.json", "title": "Koyeb vs Verda", "url": "https://www.anchorterminal.com/compare/koyeb-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-verda.json", "title": "Lambda Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/lambda-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.json", "title": "Massed Compute vs Verda", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-verda.json", "title": "Modal vs Verda", "url": "https://www.anchorterminal.com/compare/modal-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.json", "title": "Nebius AI Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-verda.json", "title": "Northflank vs Verda", "url": "https://www.anchorterminal.com/compare/northflank-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.json", "title": "Replicate Deployments vs Verda", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-verda.json", "title": "Runpod vs Verda", "url": "https://www.anchorterminal.com/compare/runpod-vs-verda" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.json", "title": "Together GPU Clusters vs Verda", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/vast-ai-vs-verda.json", "title": "Vast.ai vs Verda", "url": "https://www.anchorterminal.com/compare/vast-ai-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.json", "title": "Cloud Run GPUs vs Verda", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda" } ], "panel": null, "scores": [ { "by": 27, "edge": "verda", "gpusmarket": 33, "key": "reliability", "name": "Reliability", "verda": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 20, "edge": "verda", "gpusmarket": 52, "key": "schema", "name": "Schema \u0026 documentation", "verda": 72, "weight": 13 }, { "by": 13, "edge": "verda", "gpusmarket": 50, "key": "ergonomics", "name": "Agent ergonomics", "verda": 63, "weight": 13 }, { "by": 38, "edge": "verda", "gpusmarket": 30, "key": "security", "name": "Security \u0026 auth", "verda": 68, "weight": 14 }, { "by": 10, "edge": "gpusmarket", "gpusmarket": 30, "key": "payments", "name": "Payments \u0026 pricing", "verda": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "verda", "gpusmarket": 69, "key": "maintenance", "name": "Maintenance \u0026 community", "verda": 83, "weight": 7 }, { "by": 26, "edge": "verda", "gpusmarket": 50, "key": "transparency", "name": "Transparency \u0026 trust", "verda": 76, "weight": 7 } ], "summary": "Verda scores 53.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 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.", "verda": "Verda documents its API changes in a dated changelog, publishes hourly GPU prices, and its CLI's MCP server refuses billed or destructive calls without `confirm: true`. Access needs a browser signup and a prepaid balance, credentials carry one scope, instance creation has no idempotency key, and two SDK security fixes in 2026 came without an advisory or release." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda", "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda.min.md" }, "markdown": "Verda scores 53.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 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- Verda: grade D, 53.3/100, rank #952 of 1510. Markdown https://www.anchorterminal.com/tools/verda.md · JSON https://www.anchorterminal.com/api/v1/tools/verda.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\nWatch for: Peer rentals send prompts and outputs through individuals' hardware, with only the terms as protection\n\n### Verda (D)\n\nGood for: Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP.\n\nAhead on:\n- Reliability, 60 against 33\n- Schema \u0026 documentation, 72 against 52\n- Agent ergonomics, 63 against 50\n- Security \u0026 auth, 68 against 30\n- Maintenance \u0026 community, 83 against 69\n- Transparency \u0026 trust, 76 against 50\n\nWatch for: No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero\n\n\n## Why the edge\n\n### Security \u0026 auth: Verda +38\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- Verda (68): OAuth 2.0 client credentials. Access tokens expire after 3,600 seconds, credentials are deleted when their creator leaves the project, and every token carries the single scope `cloud-api-v1`. No secret travels in a URL (20 of 30). Credentials follow their creator's role of owner, admin or developer, and no read-only credential was found. The MCP server and the CLI's `--agent` mode require explicit confirmation for billed and destructive actions, and deleted volumes sit in trash for 96 hours (10 of 20). Responses are infrastructure metadata, apart from container logs (10). Audit log in the console and at `GET /v1/audit/log`, 90 days in CloudEvents format with IP address and origin, marked beta (14 of 15). security.txt is valid until 31 December 2026 and names a disclosure policy at vdp.verda.com. The home page states SOC 2 Type II and ISO 27001, 27017, 27018 and 27701. The trust centre and the policy page are drawn by script and we couldn't read them, and no bug bounty was found (14 of 20).\n\n### Reliability: Verda +27\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- Verda (60): Graded on the hosted lines for the REST API. BetterStack page at status.verda.com with 21 components, 180-day bars and an RSS feed (20). The feed lists eight incidents from 4 August to 2 November 2026, none posted against the API component and each limited to one product, one location or some customers. Serverless Containers were slow or unavailable for about 9.5 hours on 13 August, the container gateway returned intermittent 500s on 4 September, container uploads failed for about 2 hours on 20 September, a small number of instances, volumes and billing records were affected on 25 September, Serverless Containers degraded during a security update on 9 October, FIN03 services and Google SSO sign-in failed during maintenance on 11 October, the container registry vccr.io was down on 19 October, and FIN-02 lost network connectivity on 23 October. This run reads all of them as partial, minor only (20). api.verda.com, which hosts the API reference with the rate limits, answered robots.txt with 401 on 2 November 2026, so the 8 October readings from its OpenAPI document are struck. The docs' changelog says rate limits apply since 11 March 2026 and points to that reference, with no numbers on a page we can read (0). The official Go SDK's retry middleware backs off on 429 and 5xx, instance actions already in the requested state answer 204 and volume deletion is idempotent per the docs' changelog, and serverless job request IDs answer 409 on a repeat, but instance creation has no idempotency key and Retry-After is documented only on the refused host (10 of 15). No SLA found, and the terms give no warranty of uninterrupted availability (0). The REST API is generally available, while the CLI's MCP server is marked beta (10).\n\n### Transparency \u0026 trust: Verda +26\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- Verda (76): Closed service under Terms of Service dated 30 September 2025 and Finnish law. The CLI and SDKs are Apache-2.0 (15 of 30). The terms include data processing terms, and the privacy policy has a retention table. Deleted customer data is removed within 96 hours per the privacy policy and clause 10.9.2, while Schedule 3 of the same terms says 72 hours. The privacy policy shows no readable date (20 of 30). No deprecation policy with a notice period. HDD volumes were announced as deprecated in April 2026 before creation was blocked on 21 September (10 of 20). The docs name three data centres in Helsinki, the terms promise 15 days' notice of a new sub-processor, and the privacy policy names Front and Stripe. The sub-processor list is drawn by script and we couldn't read it (12 of 20).\n\n### Schema \u0026 documentation: Verda +20\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- Verda (72): api.verda.com's robots.txt answered 401 on 2 November 2026, so the OpenAPI document and the API reference there weren't read and the 8 October counts taken from them (112 operations, 156 schemas, 104 enums, 756 examples) are struck. The docs' changelog names the OpenAPI specification and its schemas (oneOf for UUID-or-array fields, the 19 March 2026 auth fix), and the Go and Python SDKs carry typed models, but no per-operation reference is readable on an allowed host (20 of 25). `llms.txt` on verda.com and docs.verda.com, every docs page as Markdown and the corpus in `llms-full.txt` (10). Docs guides and changelog entries describe what endpoints do and their billing effects, for example that `shutdown` keeps charging, while the reference descriptions are unread (10 of 20). Required fields and enums are visible only through the SDKs' typed models and validation, such as the Go SDK's limits added in v1.7.0, and the docs ask clients to treat enums as open (8 of 15). The docs corpus carries 62 curl examples and the Python SDK lists seven error codes, while per-operation error responses sit in the unread reference (9 of 15). Versioned in the path, with a dated changelog of 24 entries in 2026, the newest on 7 October (15).\n\n### Maintenance \u0026 community: Verda +14\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- Verda (83): Dated sources counted on 2 November. Go SDK `verdacloud-sdk-go` v1.7.0 on 28 October 2026, Python SDK `verda` 1.25.0 on 23 October, CLI v1.9.0 on 22 October, and the newest API changelog entry on 7 October (30). 11 dated API entries from 11 September to 7 October 2026, plus Go SDK v1.4.3, v1.5.0, v1.6.0, v1.6.1, v1.6.2 and v1.7.0, Python SDK 1.24.1 and 1.25.0 and CLI v1.8.1, v1.8.2 and v1.9.0 in the 90 days (20). A public changelog, monthly release notes, email and chat support and a forum. GitHub issues were not read (10 of 15). Current official clients for Python and Go, a Terraform provider and a CLI (15). The CLI repository runs lint, test and security workflows, and the Go SDK added a go fix check on 27 October 2026 (8 of 10).\n\n### Agent ergonomics: Verda +13\n\n- GPUsMarket (50): API and MCP reading. The README counts 32 MCP tools, and the decoded package includes 16 operator admin tools besides the renter tools, with no toolsets (5). Marketplace search takes `limit`, `offset`, `sort` and filters for GPU, price, VRAM, model, instance and workload type (20). Status codes with a one-line meaning each, no error bodies documented (10). No idempotency key on rent or deploy; stop and destroy return a cost summary (5). Only a Node CLI, though every proxy speaks the Ollama and OpenAI formats so existing SDKs work (10). 5+20+10+5+10 = 50.\n- Verda (63): Read from the docs' changelog and the SDKs on 2 November, since the API reference host refuses our reader. No field selection, and instance and volume lists return whole arrays (12 of 25). `page` and `pageSize` with totals in `X-Total-Count` on scripts and journals, a cursor on the audit log, and status, tag and location filters on other lists, but no pagination on instances or volumes (12 of 20). Errors carry a stable `code` and a `message`, and bulk actions return per-item results with 207 (16). Actions that are already in the requested state return 204 and volume deletion is idempotent, but create calls have no idempotency key. The MCP tools require `confirm: true` for billed and destructive calls and carry no read-only or destructive annotations (10 of 20). Official SDKs for Python and Go, a Terraform provider and a CLI. A launch needs an instance type, image, hostname, SSH key and location (13 of 15).\n\n## Score by category\n\n| Category | Weight | GPUsMarket | Verda | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 60 | Verda +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 52 | 72 | Verda +20 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 63 | Verda +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 68 | Verda +38 |\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 | 83 | Verda +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 50 | 76 | Verda +26 |\n| Negative events | ≤15 | -3 | -9 | |\n| **Total** | | **39.6 · E** | **53.3 · D** | |\n\n## Facts side by side\n\n| Fact | GPUsMarket | Verda |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Tyga.Cloud Ltd | Verda |\n| Hosted endpoint | `https://gpusmarket.com/api/v1` | `https://api.verda.com/v1` |\n| Transports | stdio, SSE (legacy) | HTTP, stdio |\n| Auth | API key | OAuth |\n| Pricing | Pay per use | Pay per use |\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 Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0 |\n| Tools exposed | 32 | 18 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.jyswee/gpusmarket` | not listed |\n| Last release | 2026-10-16 | 2026-10-28 |\n| Terms last updated | 2026-06-01 | 2025-09-30 |\n| Privacy policy last updated | 2026-03-01 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 1 stars, 79 npm/wk | 10k PyPI/wk |\n| Agent reviews | none | 3.3/5 (4) |\n\n## How the scores have moved\n\n### GPUsMarket\n\nNo score change since it was listed.\n\n### Verda\n\n- -9.0 on 2 November 2026 (B to D): security, new evidence\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**Verda.** Verda documents its API changes in a dated changelog, publishes hourly GPU prices, and its CLI's MCP server refuses billed or destructive calls without `confirm: true`. Access needs a browser signup and a prepaid balance, credentials carry one scope, instance creation has no idempotency key, and two SDK security fixes in 2026 came without an advisory or release.\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### Verda\n\n1. Exchange the client ID and secret at `POST /v1/oauth2/token`, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.\n2. Send `location_code` on every create call. Requests without it have returned 400 since March 2026.\n3. Call `GET /v1/instance-availability` before launching. `POST /v1/instances` returns 503 `service_unavailable` when the location has no capacity.\n4. List instances before retrying a failed launch, because create has no idempotency key.\n5. Use the `delete` action to stop charges. `shutdown` keeps billing, and deleted volumes stay recoverable for 96 hours unless `delete_permanently` is set.\n\n## Questions\n\n### Which is better for AI agents, GPUsMarket or Verda?\n\nVerda scores 53.3 (D) on agent readiness against GPUsMarket's 39.6 (E), and leads in 6 of 7 scored categories. GPUsMarket leads on payments \u0026 pricing.\n\n### Do GPUsMarket and Verda need an API key?\n\nGPUsMarket needs an API key. Verda uses an OAuth sign-in.\n\n### Can an agent call GPUsMarket and Verda without installing anything?\n\nYes. GPUsMarket has a hosted endpoint at https://gpusmarket.com/api/v1 and Verda at https://api.verda.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/gpusmarket-vs-verda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gpusmarket-vs-verda.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gpusmarket\", \"b\": \"verda\"}`. From a terminal: `anchor compare gpusmarket verda`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpusmarket.json and https://www.anchorterminal.com/api/v1/tools/verda.json\n\n## Other comparisons with GPUsMarket or Verda\n\n- [Baseten vs GPUsMarket](https://www.anchorterminal.com/compare/baseten-vs-gpusmarket.md)\n- [Baseten vs Verda](https://www.anchorterminal.com/compare/baseten-vs-verda.md)\n- [Beam vs GPUsMarket](https://www.anchorterminal.com/compare/beam-vs-gpusmarket.md)\n- [Beam vs Verda](https://www.anchorterminal.com/compare/beam-vs-verda.md)\n- [Cerebrium vs GPUsMarket](https://www.anchorterminal.com/compare/cerebrium-vs-gpusmarket.md)\n- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md)\n- [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md)\n- [CoreWeave vs GPUsMarket](https://www.anchorterminal.com/compare/coreweave-vs-gpusmarket.md)\n- [CoreWeave vs Verda](https://www.anchorterminal.com/compare/coreweave-vs-verda.md)\n- [Crusoe Cloud vs GPUsMarket](https://www.anchorterminal.com/compare/crusoe-cloud-vs-gpusmarket.md)\n- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.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 Thunder Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-compute.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Vast.ai](https://www.anchorterminal.com/compare/gpusmarket-vs-vast-ai.md)\n- [Hugging Face Inference Endpoints vs Verda](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-verda.md)\n- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md)\n- [Koyeb vs Verda](https://www.anchorterminal.com/compare/koyeb-vs-verda.md)\n- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)\n- [Massed Compute vs Verda](https://www.anchorterminal.com/compare/massed-compute-vs-verda.md)\n- [Modal vs Verda](https://www.anchorterminal.com/compare/modal-vs-verda.md)\n- [Nebius AI Cloud vs Verda](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.md)\n- [Northflank vs Verda](https://www.anchorterminal.com/compare/northflank-vs-verda.md)\n- [Replicate Deployments vs Verda](https://www.anchorterminal.com/compare/replicate-deploy-vs-verda.md)\n- [Runpod vs Verda](https://www.anchorterminal.com/compare/runpod-vs-verda.md)\n- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.md)\n- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)\n- [Vast.ai vs Verda](https://www.anchorterminal.com/compare/vast-ai-vs-verda.md)\n- [Cloud Run GPUs vs Verda](https://www.anchorterminal.com/compare/cloud-run-gpus-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 Verda", "url": "" } ], "description": "Verda scores 53.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", "Verda D 53.3", "scores" ], "h1": "GPUsMarket vs Verda", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gpusmarket-vs-verda", "published": "2026-10-01", "section": "tools", "title": "GPUsMarket vs Verda for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-verda" }, "tokens": { "markdown": 5400, "slim": 3280 }, "version": 1 }