{ "data": { "similar": [ { "grade": "B", "json": "https://www.anchorterminal.com/tools/nebius-ai-cloud.json", "name": "Nebius AI Cloud", "score": 67.2, "shared": [ "compute.gpu", "compute.endpoints", "compute.batch", "compute.containers" ], "slug": "nebius-ai-cloud" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/modal.json", "name": "Modal", "score": 63.6, "shared": [ "compute.gpu", "compute.endpoints", "compute.batch", "compute.containers" ], "slug": "modal" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/verda.json", "name": "Verda", "score": 62.3, "shared": [ "compute.gpu", "compute.endpoints", "compute.batch", "compute.containers" ], "slug": "verda" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/coreweave.json", "name": "CoreWeave", "score": 61.5, "shared": [ "compute.gpu", "compute.containers", "compute.endpoints", "compute.batch" ], "slug": "coreweave" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/northflank.json", "name": "Northflank", "score": 61.3, "shared": [ "compute.gpu", "compute.containers", "compute.batch", "compute.endpoints" ], "slug": "northflank" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/beam.json", "name": "Beam", "score": 55.5, "shared": [ "compute.gpu", "compute.endpoints", "compute.batch", "compute.containers" ], "slug": "beam" } ], "tool": { "slug": "crusoe-cloud", "name": "Crusoe Cloud", "vendor": "Crusoe", "vendorUrl": "https://www.crusoe.ai", "kind": "http-api", "category": "gpu-compute", "summary": "Crusoe Cloud rents NVIDIA and AMD GPU virtual machines with managed Kubernetes and Slurm, and runs hosted model inference, dedicated deployments and LoRA fine-tuning. Resources are managed through a REST API, a CLI, a Terraform provider and a Go client.", "url": "https://www.anchorterminal.com/tools/crusoe-cloud", "markdownUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json", "repo": "https://github.com/crusoecloud/client-go", "license": "Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.cloud.crusoe.ai/v1", "packages": [ { "registry": "go", "name": "github.com/crusoecloud/client-go" }, { "registry": "npm", "name": "@crusoeai/cloud-mcp" } ], "auth": "api-key", "authNotes": "Self-serve. A person signs up in the console with Google, GitHub or an email code, then creates an access key ID and secret key under Security, with an optional alias and expiry. Each request carries `X-Crusoe-Timestamp` and `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`, where the signature is an HMAC-SHA256 of the path, sorted query string, verb and timestamp. Keys inherit the roles of the user who made them (`org-admin`, `org-editor`, `org-reader`, `project-editor`, `project-reader`). Managed AI uses separate Intelligence API keys sent as a Bearer token. Service accounts appear in the API description and the Terraform provider 1.6.0, with no docs page found.", "pricing": "usage", "pricingNotes": "Pay as you go, billed per second for on-demand VMs. Per GPU-hour, H200 $4.29, H100 $3.90, MI300X $3.45, A100 $2.00 to $2.30 and L40S $1.50. GB200, B200, MI355X and all spot prices are contact sales. Compute needs a non-prepaid credit card. $5 of introductory credits cover Serverless Inference and Fine-Tuning without a card. Ingress and egress are free (https://www.crusoe.ai/cloud/pricing).", "priceSummary": "$0.04 / vCPU-hr", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API description or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 41, "popularity": { "githubStars": null, "npmWeekly": 7, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.crusoecloud.com/", "llmsTxt": "https://docs.crusoecloud.com/llms.txt", "openapi": "https://api.crusoecloud.com/v1/openapi.json", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch", "compute.endpoints" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "terraform", "go", "status-page", "soc2", "enterprise" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 63.4, "grade": "B", "agentReady": false, "rank": 396, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 76, "payments": 30, "reliability": 66, "schema": 79, "security": 74, "transparency": 77 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 66, "points": 13.2, "reason": "Graded as a hosted service on the REST API. Statuspage at status.crusoecloud.com with components per region and service (20). The history page shows, since August 2026, one critical incident (shared disks, Object Storage and the container registry unreachable in eu-norway1 for about 3 hours 54 minutes on 29 September), one minor incident (VM and Kubernetes cluster creation in us-east2 for about 7.5 hours on 2 September) and two with no stated impact; July was not on the page read (10). Rate limits carry numbers only for Serverless Inference (500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one); none were found for the infrastructure API, whose MCP server throttles itself to 60 requests a minute (8 of 15). Serverless Inference documents 429 and 503 with exponential backoff and `x-ratelimit-*` headers; no Retry-After, no idempotency keys and no retry guidance for infrastructure writes were found (8 of 15). SLA of 99.5 per cent a month per GPU virtual machine and per persistent disk, with credits of 10, 25 or 100 per cent (10). The v1 API is labelled Latest and the services graded are generally available; the MCP server is in preview (10)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 79, "points": 12.84, "reason": "A Swagger 2.0 description for `/v1` and `/v1alpha5`, linked from the reference page and kept in `crusoecloud/client-go`, and an OpenAPI description for the Intelligence Foundry API (25). `llms.txt` and a Markdown twin of each docs page (10). Every one of the 257 operations in the repository copy has a one-line summary, 74 have a longer description, and fields are described; few say when not to call (11). 64 enums and 208 required lists, though `limit` is typed as a string and instance types and locations are plain strings; the file declares no security scheme (10). 1,231 examples with request and response samples, and 400, 401, 403, 404 and 500 responses with a `code` and `message` body; no error catalogue and 429 appears on one operation (10). Versioned paths, dated Crusoe Updates entries with RSS and Atom feeds, and tagged Go client releases; the updates do not list API changes field by field (13)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 45, "points": 7.31, "reason": "Lists take `limit` or `page_size` on 16 of about 104 list calls, and VM lists filter by id, name, type, location and state; no field selection (12 of 25). Token pagination with next and previous tokens and a `sort` parameter where present; most lists return everything (12). Errors are an HTTP status with `code` and `message`, and long-running calls return an operation with `state` and `result` to poll; no documented list of error codes (10). No idempotency key or safe-retry guidance found; the preview MCP server has read tools only, and its annotations were not read (4). VM create needs a name, type, location and SSH key and installs a monitoring agent by default; the Go client is the only official SDK found, beside a CLI and a Terraform provider, and other languages must code the request signature (7)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 74, "points": 12.95, "reason": "Access key and secret key with optional expiry, deletable in the console or through `/users/tokens`. Requests are signed with HMAC-SHA256 and a timestamp, so no secret is sent and none travels in a URL. Keys inherit their creator's roles and cannot be narrowed further; service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0 (24). `org-reader` and `project-reader` roles give read-only access and the MCP server exposes no write tools; no confirmation step for destructive API calls (14). Returns infrastructure metadata, and the MCP docs warn that it is sent to the assistant and that an agent with a shell can still run the CLI (10). Audit log of 90 days of control-plane actions with actor, IP, surface and result, readable through the API by admins; read events are not logged (13). security.txt valid until 1 March 2027 with no Policy field, ISO 27001, ISO 42001 and SOC 2 Type I and II claimed on the cloud page, customer-managed encryption keys; no bug bounty found, the trust centre was unreadable, and the apt install line sets `[trusted=yes]` (13)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 30, "points": 3.75, "reason": "No machine payment protocol (0). Per-GPU-hour, per-vCPU-hour, per-GiB and per-token prices published without a login, though spot prices and on-demand prices for GB200, B200 and MI355X are contact sales (20). $5 of introductory credits cover Serverless Inference and Serverless Fine-Tuning without a payment method; GPU machines, the product graded here, need a non-prepaid credit card (10 of 20). Signup is a browser flow with Google, GitHub or an emailed code, and the first key is made in the console (0)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 76, "points": 6.65, "reason": "Crusoe Updates entries on 5, 7 and 8 October 2026 and a Terraform provider 1.6.0 changelog entry on 8 October (30). Go client tags v1.0.1 to v1.0.18 and seven Terraform provider tags since 11 July 2026, plus more than 20 dated updates (20). Closed service with a dated changelog and feeds, a support portal, email support and published support tiers; GitHub issue response times were not read (10 of 15). The Go client is current and generated from the API description, with the Terraform provider and CLI beside it; one language only, and the MCP package was not checked against the official registry (10 of 15). A lint workflow in the Terraform provider and GitLab CI configuration in the Go client; results were not read (6)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 77, "points": 6.74, "note": "editorial 64, provenance 90", "reason": "Closed service under Terms of Service version 1.10, effective 10 August 2026, with ten earlier versions kept on the legal page; the Go client and MCP package are MIT (15). The Privacy Notice (version 1.3, 12 March 2026) covers Service Data and the Data Processing and Security Terms (version 1.3, 14 July 2026) cover Customer Data, with deletion on instruction and at the end of the term, and the Intelligence Foundry terms say inputs, outputs and training data are not used to train models without opt-in consent; no retention periods are given in numbers (22). The terms promise 90 days' notice before discontinuing a service or changing a customer-facing API incompatibly, and a deprecation page gives dates such as 8 November 2026 for old CSI drivers, announced 15 September; model deprecations are logged on the day they take effect (17). Seven data centre zones are published; the data processing terms point to a sub-processor list that was not found in the pages read (10)." } ], "assessment": { "date": "2026-10-09", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Lists take `limit` or `page_size` on 16 of about 104 list calls, and VM lists filter by id, name, type, location and state; no field selection (12 of 25). Token pagination with next and previous tokens and a `sort` parameter where present; most lists return everything (12). Errors are an HTTP status with `code` and `message`, and long-running calls return an operation with `state` and `result` to poll; no documented list of error codes (10). No idempotency key or safe-retry guidance found; the preview MCP server has read tools only, and its annotations were not read (4). VM create needs a name, type, location and SSH key and installs a monitoring agent by default; the Go client is the only official SDK found, beside a CLI and a Terraform provider, and other languages must code the request signature (7).", "maintenance": "Crusoe Updates entries on 5, 7 and 8 October 2026 and a Terraform provider 1.6.0 changelog entry on 8 October (30). Go client tags v1.0.1 to v1.0.18 and seven Terraform provider tags since 11 July 2026, plus more than 20 dated updates (20). Closed service with a dated changelog and feeds, a support portal, email support and published support tiers; GitHub issue response times were not read (10 of 15). The Go client is current and generated from the API description, with the Terraform provider and CLI beside it; one language only, and the MCP package was not checked against the official registry (10 of 15). A lint workflow in the Terraform provider and GitLab CI configuration in the Go client; results were not read (6).", "payments": "No machine payment protocol (0). Per-GPU-hour, per-vCPU-hour, per-GiB and per-token prices published without a login, though spot prices and on-demand prices for GB200, B200 and MI355X are contact sales (20). $5 of introductory credits cover Serverless Inference and Serverless Fine-Tuning without a payment method; GPU machines, the product graded here, need a non-prepaid credit card (10 of 20). Signup is a browser flow with Google, GitHub or an emailed code, and the first key is made in the console (0).", "reliability": "Graded as a hosted service on the REST API. Statuspage at status.crusoecloud.com with components per region and service (20). The history page shows, since August 2026, one critical incident (shared disks, Object Storage and the container registry unreachable in eu-norway1 for about 3 hours 54 minutes on 29 September), one minor incident (VM and Kubernetes cluster creation in us-east2 for about 7.5 hours on 2 September) and two with no stated impact; July was not on the page read (10). Rate limits carry numbers only for Serverless Inference (500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one); none were found for the infrastructure API, whose MCP server throttles itself to 60 requests a minute (8 of 15). Serverless Inference documents 429 and 503 with exponential backoff and `x-ratelimit-*` headers; no Retry-After, no idempotency keys and no retry guidance for infrastructure writes were found (8 of 15). SLA of 99.5 per cent a month per GPU virtual machine and per persistent disk, with credits of 10, 25 or 100 per cent (10). The v1 API is labelled Latest and the services graded are generally available; the MCP server is in preview (10).", "schema": "A Swagger 2.0 description for `/v1` and `/v1alpha5`, linked from the reference page and kept in `crusoecloud/client-go`, and an OpenAPI description for the Intelligence Foundry API (25). `llms.txt` and a Markdown twin of each docs page (10). Every one of the 257 operations in the repository copy has a one-line summary, 74 have a longer description, and fields are described; few say when not to call (11). 64 enums and 208 required lists, though `limit` is typed as a string and instance types and locations are plain strings; the file declares no security scheme (10). 1,231 examples with request and response samples, and 400, 401, 403, 404 and 500 responses with a `code` and `message` body; no error catalogue and 429 appears on one operation (10). Versioned paths, dated Crusoe Updates entries with RSS and Atom feeds, and tagged Go client releases; the updates do not list API changes field by field (13).", "security": "Access key and secret key with optional expiry, deletable in the console or through `/users/tokens`. Requests are signed with HMAC-SHA256 and a timestamp, so no secret is sent and none travels in a URL. Keys inherit their creator's roles and cannot be narrowed further; service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0 (24). `org-reader` and `project-reader` roles give read-only access and the MCP server exposes no write tools; no confirmation step for destructive API calls (14). Returns infrastructure metadata, and the MCP docs warn that it is sent to the assistant and that an agent with a shell can still run the CLI (10). Audit log of 90 days of control-plane actions with actor, IP, surface and result, readable through the API by admins; read events are not logged (13). security.txt valid until 1 March 2027 with no Policy field, ISO 27001, ISO 42001 and SOC 2 Type I and II claimed on the cloud page, customer-managed encryption keys; no bug bounty found, the trust centre was unreadable, and the apt install line sets `[trusted=yes]` (13).", "transparency": "Closed service under Terms of Service version 1.10, effective 10 August 2026, with ten earlier versions kept on the legal page; the Go client and MCP package are MIT (15). The Privacy Notice (version 1.3, 12 March 2026) covers Service Data and the Data Processing and Security Terms (version 1.3, 14 July 2026) cover Customer Data, with deletion on instruction and at the end of the term, and the Intelligence Foundry terms say inputs, outputs and training data are not used to train models without opt-in consent; no retention periods are given in numbers (22). The terms promise 90 days' notice before discontinuing a service or changing a customer-facing API incompatibly, and a deprecation page gives dates such as 8 November 2026 for old CSI drivers, announced 15 September; model deprecations are logged on the day they take effect (17). Seven data centre zones are published; the data processing terms point to a sub-processor list that was not found in the pages read (10)." }, "sources": [ { "what": "docs index for agents", "url": "https://docs.crusoecloud.com/llms.txt", "seen": "2026-10-09" }, { "what": "API authentication and base URL", "url": "https://docs.crusoecloud.com/reference/api/", "seen": "2026-10-09" }, { "what": "API reference for v1, rendered page", "url": "https://docs.crusoecloud.com/api/", "seen": "2026-10-09" }, { "what": "Intelligence Foundry API reference, rendered page", "url": "https://docs.crusoecloud.com/api/managed-ai/", "seen": "2026-10-09" }, { "what": "API description file read from the Go client repository, not fetched from the API host", "url": "https://github.com/crusoecloud/client-go", "seen": "2026-10-09" }, { "what": "MCP server docs", "url": "https://docs.crusoecloud.com/reference/mcp-server.md", "seen": "2026-10-09" }, { "what": "API keys", "url": "https://docs.crusoecloud.com/identity-and-security/managing-api-keys.md", "seen": "2026-10-09" }, { "what": "users and roles", "url": "https://docs.crusoecloud.com/identity-and-security/managing-organization-users.md", "seen": "2026-10-09" }, { "what": "audit logs", "url": "https://docs.crusoecloud.com/identity-and-security/audit-logs.md", "seen": "2026-10-09" }, { "what": "account creation and billing", "url": "https://docs.crusoecloud.com/create-an-account.md", "seen": "2026-10-09" }, { "what": "Crusoe Updates", "url": "https://docs.crusoecloud.com/updates", "seen": "2026-10-09" }, { "what": "deprecation notices", "url": "https://docs.crusoecloud.com/resources/deprecation_notices.md", "seen": "2026-10-09" }, { "what": "Serverless Inference rate limits", "url": "https://docs.crusoecloud.com/serverless-inference/rate-limits.md", "seen": "2026-10-09" }, { "what": "Serverless Inference models and deprecations", "url": "https://docs.crusoecloud.com/serverless-inference/available-models.md", "seen": "2026-10-09" }, { "what": "Self-Serve Deployments quickstart", "url": "https://docs.crusoecloud.com/quickstart/self-serve-deployments.md", "seen": "2026-10-09" }, { "what": "VM types, lifecycle and billing", "url": "https://docs.crusoecloud.com/compute/virtual-machines/overview.md", "seen": "2026-10-09" }, { "what": "CLI install", "url": "https://docs.crusoecloud.com/installing-the-cli.md", "seen": "2026-10-09" }, { "what": "quotas", "url": "https://docs.crusoecloud.com/usage-billing/viewing-quotas.md", "seen": "2026-10-09" }, { "what": "spot instances", "url": "https://docs.crusoecloud.com/usage-billing/spot.md", "seen": "2026-10-09" }, { "what": "locations", "url": "https://docs.crusoecloud.com/locations.md", "seen": "2026-10-09" }, { "what": "support channels", "url": "https://docs.crusoecloud.com/resources/support.md", "seen": "2026-10-09" }, { "what": "pricing", "url": "https://www.crusoe.ai/cloud/pricing", "seen": "2026-10-09" }, { "what": "cloud product page, certification claims", "url": "https://www.crusoe.ai/cloud", "seen": "2026-10-09" }, { "what": "security.txt", "url": "https://www.crusoe.ai/.well-known/security.txt", "seen": "2026-10-09" }, { "what": "Terms of Service, version 1.10", "url": "https://legal.crusoe.ai/#terms-of-service", "seen": "2026-10-09" }, { "what": "Crusoe Cloud Platform Privacy Notice, version 1.3", "url": "https://legal.crusoe.ai/#cloud-privacy-policy", "seen": "2026-10-09" }, { "what": "Data Processing and Security Terms, version 1.3", "url": "https://legal.crusoe.ai/#data-processing", "seen": "2026-10-09" }, { "what": "Service Level Agreements, version 8.0", "url": "https://legal.crusoe.ai/#service-level-agreements", "seen": "2026-10-09" }, { "what": "Service Specific Terms, version 5.0", "url": "https://legal.crusoe.ai/#service-specific-terms", "seen": "2026-10-09" }, { "what": "status page", "url": "https://status.crusoecloud.com/", "seen": "2026-10-09" }, { "what": "status history", "url": "https://status.crusoecloud.com/history", "seen": "2026-10-09" }, { "what": "storage incident of 29 September 2026", "url": "https://status.crusoecloud.com/incidents/hp3xb537kdwy", "seen": "2026-10-09" }, { "what": "Terraform provider changelog and tags", "url": "https://github.com/crusoecloud/terraform-provider-crusoe", "seen": "2026-10-09" }, { "what": "CLI repository", "url": "https://github.com/crusoecloud/cli", "seen": "2026-10-09" }, { "what": "MCP package on npm", "url": "https://registry.npmjs.org/@crusoeai/cloud-mcp/latest", "seen": "2026-10-09" }, { "what": "npm weekly downloads", "url": "https://api.npmjs.org/downloads/point/last-week/@crusoeai/cloud-mcp", "seen": "2026-10-09" }, { "what": "RDAP for crusoe.ai", "url": "https://rdap.identitydigital.services/rdap/domain/crusoe.ai", "seen": "2026-10-09" }, { "what": "RDAP for crusoecloud.com", "url": "https://rdap.verisign.com/com/v1/domain/crusoecloud.com", "seen": "2026-10-09" } ], "openQuestions": [ "The lead named only the CLI and the Terraform provider. Crusoe also publishes a REST API with an API description, a Go client and a preview MCP server, and the API is the surface graded.", "unchecked: the trust centre at trust.crusoe.ai is drawn by script, so certifications, the sub-processor list and any penetration test summary were not read. Certifications are taken from the product page as the vendor's claim.", "unchecked: status history for July 2026. The history page read showed August to October only, and robots.txt closes the status API.", "unchecked: the API description at `https://api.crusoecloud.com/v1/openapi.json` was not fetched. The copy in `crusoecloud/client-go` and the rendered reference page were read, and the two differ in operation count (257 and 164).", "unchecked: GitHub issue response times, CI results, repository stars and CLI release dates. Tags in the CLI repository all carry one 2022 commit date.", "unchecked: the tool definitions and annotations of `@crusoeai/cloud-mcp`. Its source is on a GitLab address that was not read, and the package was not downloaded or run. The count of 41 tools comes from the docs page.", "No request rate limits or idempotency keys were found for the infrastructure API. They may exist in pages not read.", "Whether a deprecated Serverless Inference model stops answering on the listed date, and how much notice customers had, was not established. The changelog entries are dated the day of deprecation.", "Service accounts are in the API description and the Terraform provider 1.6.0, with no docs page found, so their scopes and token lifetimes are not established.", "The create-an-account page says billing must be enabled to use managed inference, while the updates and rate-limit pages describe use on introductory credits with no payment method.", "The Service Specific Terms require written consent before benchmark results are published and the Intelligence Foundry terms bar competitive analysis or benchmarking. The Acceptable Use Policy bars disruptive crawling or scraping and testing the services to find limitations. This matters before any Anchor Terminal probe runs.", "`provenance.terms` and `provenance.privacy` are anchors on one 3.5 MB page that holds every legal document and its earlier versions, so the policy reader may need the section picked out by hand.", "`compute.endpoints` rests on Self-Serve Deployments, which serve catalogue models and LoRA adapters, not a customer's own container. `compute.serverless` is left out." ] }, "negative": 0, "verdict": "The v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, spot and B200 prices go through sales, and a storage outage in eu-norway1 lasted about four hours on 29 September 2026.", "bestFor": "Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.", "strengths": [ "Requests are signed with HMAC-SHA256 over the path, query, verb and timestamp, so the secret key never travels with a request.", "The API description is published for `/v1` and `/v1alpha5`, with 1,231 examples, and the docs serve `llms.txt` and a Markdown twin of each page.", "On-demand prices are public and billed per second. H100 is $3.90 and H200 $4.29 a GPU-hour, with no charge for ingress or egress.", "Organisation and project roles include read-only `org-reader` and `project-reader`, and the audit log keeps 90 days of control-plane actions readable through the API.", "The Terms of Service promise 90 days' notice before a service is discontinued or a customer-facing API changes in a backwards-incompatible way." ], "weaknesses": [ "No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.", "No request rate limits were found for the infrastructure API. Numbers are published only for Serverless Inference.", "Spot prices and on-demand prices for GB200, B200 and MI355X are listed as contact sales, and provisioning compute needs a non-prepaid credit card.", "The status page shows a critical storage incident in eu-norway1 on 29 September 2026 (about 3 hours 54 minutes) and a 7.5-hour VM and cluster creation fault in us-east2 on 2 September.", "The Service Specific Terms let customers publish benchmark results only with Crusoe's written consent, and the Intelligence Foundry terms bar competitive analysis or benchmarking. Recorded as a fact, and it matters before any probe is run." ], "agentNotes": [ "Sign every request. Build the payload from path, sorted query string, verb and `X-Crusoe-Timestamp`, HMAC-SHA256 it with the base64url-decoded secret, and send `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`.", "Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.", "Creates, updates and deletes return an operation. Poll the matching operations endpoint for `state`, and list existing resources by name before retrying a create, because no idempotency key was found.", "Managed AI uses separate Intelligence API keys and hosts, `api.inference.crusoecloud.com` for OpenAI-compatible calls and `api.intelligence.crusoecloud.com` for files and fine-tuning jobs.", "Delete a VM and its disks to stop charges. A stopped on-demand VM is not billed for compute, but its 128 GB OS disk still bills at $0.08 a GiB-month." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.4 } ], "editorialScores": { "ergonomics": 45, "maintenance": 76, "payments": 30, "reliability": 66, "schema": 79, "security": 74, "transparency": 64 }, "provenanceScore": 90 }, "connect": { "install": "brew install crusoecloud/cli/crusoe", "http": "curl https://api.cloud.crusoe.ai/v1/capacities -H \"X-Crusoe-Timestamp: \u003cRFC3339 timestamp\u003e\" -H \"Authorization: Bearer \u003cversion:access_key_id:base64_encoded_signature\u003e\"", "claudeCode": "claude mcp add crusoe-cloud -- npx -y @crusoeai/cloud-mcp", "config": { "mcpServers": { "crusoe-cloud": { "args": [ "-y", "@crusoeai/cloud-mcp" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/crusoe-cloud" }, "notable": [ "The API reference page lists 164 operations for v1. The Swagger 2.0 file in `crusoecloud/client-go` (v1.0.18, 1 October 2026) has 257 operations on 170 paths, with service accounts, role bindings, Slurm and Intelligence Foundry deployments among them (https://docs.crusoecloud.com/api/, https://github.com/crusoecloud/client-go)", "The official MCP server `@crusoeai/cloud-mcp` is in preview, runs locally over stdio, reads credentials from `~/.crusoe/config` and has only read tools, with a client-side limit of 60 requests a minute (https://docs.crusoecloud.com/reference/mcp-server)", "Self-Serve Deployments (14 July 2026) create dedicated inference endpoints for catalogue models and LoRA adapters through `/v1/projects/{project_id}/foundry/selfserve/deployments`, billed per GPU-hour until deleted (https://docs.crusoecloud.com/quickstart/self-serve-deployments)", "Introductory credits of $5 cover Serverless Inference and Serverless Fine-Tuning without a payment method. GPU machines need billing enabled with a non-prepaid credit card (https://docs.crusoecloud.com/updates, https://docs.crusoecloud.com/create-an-account)", "Six Serverless Inference models were marked deprecated on 12 September and 2 October 2026, in changelog entries dated the same day and labelled Breaking. Kimi K2.6 had been added on 24 June 2026 (https://docs.crusoecloud.com/serverless-inference/available-models)", "The Service Specific Terms allow benchmark tests but require Crusoe's prior written consent to publish results, and the Intelligence Foundry terms forbid competitive analysis or benchmarking and exceeding rate limits (https://legal.crusoe.ai/#service-specific-terms)", "The Linux install instructions add the apt source with `[trusted=yes]`, which turns off signature checks for that repository. GitHub release assets carry a signed checksum file (https://docs.crusoecloud.com/installing-the-cli, https://github.com/crusoecloud/cli)" ], "area": "models", "details": [ { "label": "Surface graded", "value": "The REST API at `https://api.cloud.crusoe.ai/v1` (Swagger 2.0). The CLI, the Terraform provider and the preview MCP server are noted alongside" }, { "label": "MCP server", "value": "Preview, local, stdio, `npx -y @crusoeai/cloud-mcp` (0.1.6, MIT). 41 read-only tools named in the docs across discovery, compute, storage, networking, Kubernetes, audit logs, quotas and usage. Lists are cut to 50 items by default" }, { "label": "Free tier", "value": "$5 of introductory credits for Serverless Inference and Serverless Fine-Tuning with no payment method. None found for GPU machines" }, { "label": "GPUs", "value": "NVIDIA GB200, B300, B200, H200, H100, A100 and L40S, AMD MI355X and MI300X. L40S and A100 PCIe come in 1 to 10 GPU shapes, the others as 8-GPU or 4-GPU machines (https://docs.crusoecloud.com/compute/virtual-machines/overview)" }, { "label": "Orchestration", "value": "Crusoe Managed Kubernetes at $0.10 a cluster-hour, Managed Slurm, a container registry and instance templates with bulk create" }, { "label": "Scale to zero", "value": "None found. Self-Serve Deployments run a set replica count and bill until deleted. An on-demand VM can be stopped and is then billed only for its disks" }, { "label": "Cold start", "value": "No figure published. A VM in the `Creating` state can take up to a minute per the docs" }, { "label": "Billing basis", "value": "On-demand VMs per second in the running state. Reserved VMs for the whole commitment. Self-Serve Deployments per GPU-hour, Serverless Inference and Fine-Tuning per token. Ingress and egress are free" }, { "label": "Rate limits", "value": "None found for the infrastructure API. Serverless Inference allows 500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one, and returns `x-ratelimit-*` headers" }, { "label": "Errors", "value": "HTTP 400, 401, 403, 404 and 500 with a `code` and `message` body. No error catalogue found" }, { "label": "Pagination", "value": "`limit` with `next_token` and `prev_token`, or `page_size` with `next_page_token`, on 16 list calls. VM lists filter by id, name, type, location and state" }, { "label": "Credentials", "value": "Access key ID and secret key created in the console, with optional alias and expiry, deletable, inheriting the creator's roles. Separate Intelligence API keys for Managed AI. Service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0" }, { "label": "Roles", "value": "`org-admin`, `org-editor`, `org-reader`, `project-editor` and `project-reader`. SSO through OIDC, MFA and SCIM" }, { "label": "Audit", "value": "90 days of control-plane actions at `/organizations/{org_id}/audit-logs`, admins only, no read or list events (https://docs.crusoecloud.com/identity-and-security/audit-logs)" }, { "label": "SLA", "value": "99.5 per cent monthly uptime per GPU virtual machine and per persistent disk volume, with credits of 10, 25 or 100 per cent, claimed within 30 days. Version 8.0, effective 21 July 2026 (https://legal.crusoe.ai/#service-level-agreements)" }, { "label": "Regions", "value": "Seven data centre zones in Texas, Ohio, Nevada, Virginia, Iceland (two) and Norway (https://docs.crusoecloud.com/locations)" }, { "label": "SDKs", "value": "Go `github.com/crusoecloud/client-go` v1.0.18 (1 October 2026, MIT, generated from the API description), Terraform provider 1.6.0 changelog entry of 8 October 2026, and a closed-source CLI" }, { "label": "Certifications", "value": "ISO 27001, ISO 42001 and SOC 2 Type I and II per https://www.crusoe.ai/cloud. The trust centre at trust.crusoe.ai is drawn by script and was not read" }, { "label": "Status", "value": "status.crusoecloud.com on Atlassian Statuspage, with components for GPU machines in six regions, networking, storage, Kubernetes, API, console, container registry and Intelligence Foundry" } ], "unitPrices": [ { "item": "NVIDIA H100 80 GB HGX, on demand", "unit": "gpu-hour", "usd": 3.9, "note": "Billed per second while running. Spot is contact sales" }, { "item": "NVIDIA H200 141 GB HGX, on demand", "unit": "gpu-hour", "usd": 4.29 }, { "item": "NVIDIA A100 80 GB SXM, on demand", "unit": "gpu-hour", "usd": 2.3 }, { "item": "NVIDIA A100 80 GB PCIe, on demand", "unit": "gpu-hour", "usd": 2 }, { "item": "NVIDIA L40S 48 GB, on demand", "unit": "gpu-hour", "usd": 1.5 }, { "item": "AMD MI300X 192 GB, on demand", "unit": "gpu-hour", "usd": 3.45 }, { "item": "NVIDIA H100, Self-Serve Deployment", "unit": "gpu-hour", "usd": 5.5, "note": "Dedicated inference endpoint, billed until deleted. H200 $6.00, B200 $9.65, MI355X $7.40" }, { "item": "General-purpose CPU instance", "unit": "vcpu-hour", "usd": 0.04, "note": "Storage-optimised $0.09" }, { "item": "Persistent disk", "unit": "gb-month", "usd": 0.08, "note": "Per GiB. Shared disks $0.07, Object Storage $0.06" } ], "provenance": { "legalEntity": "Crusoe Technologies LLC", "domain": "crusoe.ai", "domainRegistered": "2019-01-28", "endpointOnVendorDomain": true, "terms": "https://legal.crusoe.ai/#terms-of-service", "privacy": "https://legal.crusoe.ai/#cloud-privacy-policy", "statusPage": "https://status.crusoecloud.com", "changelog": "https://docs.crusoecloud.com/updates", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Crusoe Cloud Platform Terms of Service, version 1.10, effective 10 August 2026, are a contract with Crusoe Technologies LLC and its affiliates. Ten earlier versions are kept on the same page.", "legal.crusoe.ai is one page that holds every legal document and its earlier versions, reached by anchor. The terms and privacy links point at the anchors for the platform terms and the Crusoe Cloud Platform Privacy Notice, not at the separate website terms and website privacy notice.", "The Crusoe Cloud Platform Privacy Notice, version 1.3, effective 12 March 2026, covers Service Data only. Customer Data falls under the Data Processing and Security Terms, version 1.3, effective 14 July 2026.", "The API reference gives `https://api.cloud.crusoe.ai/v1`, under the vendor domain. Other docs pages and the MCP server name `api.crusoecloud.com`, and Managed AI answers at `api.inference.crusoecloud.com` and `api.intelligence.crusoecloud.com`. crusoecloud.com was registered on 14 April 2020 per RDAP and redirects to www.crusoe.ai.", "security.txt at www.crusoe.ai gives security@crusoe.ai and expires on 1 March 2027. It has no Policy field.", "RDAP for crusoe.ai gives a registration date of 2019-01-28. The website footer reads Crusoe, Inc, and the licence files in the CLI and Go client repositories name Crusoe Energy Systems LLC." ], "score": 90, "checks": [ { "check": "Legal entity named", "value": "Crusoe Technologies LLC", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "crusoe.ai, registered 2019-01-28 (7 years)", "points": 11, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "api.cloud.crusoe.ai", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.crusoecloud.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "valid", "points": 10, "max": 10, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://legal.crusoe.ai/#terms-of-service", "state": "unreadable", "reason": "the page holds every legal document of the vendor and its past versions, so the one document the listing means cannot be read apart from the rest", "readAt": "2026-10-09", "points": 7, "max": 10 }, { "kind": "privacy", "url": "https://legal.crusoe.ai/#cloud-privacy-policy", "state": "unreadable", "reason": "the page holds every legal document of the vendor and its past versions, so the one document the listing means cannot be read apart from the rest", "readAt": "2026-10-09", "points": 7, "max": 10 } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.json", "live": { "slug": "crusoe-cloud", "probe": { "target": "https://api.cloud.crusoe.ai/v1", "method": "get", "lastAt": "2026-10-10T02:07:06.368905489Z", "lastOk": true, "lastStatus": 200, "lastMs": 143, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 193, "p95ms24h": 307, "samples24h": 107, "samples30d": 107, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "vendorStatus": { "page": "https://status.crusoecloud.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:05:53.081917255Z" }, "versions": [ { "registry": "npm", "name": "@crusoeai/cloud-mcp", "version": "0.1.6", "seenAt": "2026-10-09T16:48:11.482960233Z" } ], "githubStars": 4, "npmWeekly": 7, "pages": [ { "url": "https://docs.crusoecloud.com/updates", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:05.621891732Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "49f564f8d6cc" }, { "url": "https://www.crusoe.ai/cloud/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:49:22.174984932Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c8964d1b8c97" }, { "url": "https://legal.crusoe.ai/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:41:07.513334155Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "60dd879bf821" } ], "updatedAt": "2026-10-10T02:07:06.368905489Z" } }, "verify": { "accepts": "a page on crusoe.ai or one of its subdomains, or the README of github.com/crusoecloud/client-go", "badgeUrl": "https://www.anchorterminal.com/badges/crusoe-cloud.svg", "body": { "slug": "crusoe-cloud", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/crusoe-cloud", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/crusoe-cloud\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/crusoe-cloud.svg\" alt=\"Crusoe Cloud on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Crusoe Cloud on Anchor Terminal](https://www.anchorterminal.com/badges/crusoe-cloud.svg)](https://www.anchorterminal.com/tools/crusoe-cloud)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/crusoe-cloud\"\u003eCrusoe Cloud on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/crusoe-cloud", "json": "https://www.anchorterminal.com/tools/crusoe-cloud.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/crusoe-cloud.md", "slim": "https://www.anchorterminal.com/tools/crusoe-cloud.min.md" }, "markdown": "## Overview\n\n**Grade B · 63.4/100 · rank #396 of 950 · #6 in GPU \u0026 serverless compute · not agent-ready · confidence medium**\n\n\n## Assessment\n\nThe v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, spot and B200 prices go through sales, and a storage outage in eu-norway1 lasted about four hours on 29 September 2026.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Crusoe (https://www.crusoe.ai) |\n| Kind | HTTP API |\n| Category | GPU \u0026 serverless compute (https://www.anchorterminal.com/categories/gpu-compute) |\n| Transport | HTTP, stdio |\n| Endpoint | `https://api.cloud.crusoe.ai/v1` |\n| Auth | API key · Self-serve. A person signs up in the console with Google, GitHub or an email code, then creates an access key ID and secret key under Security, with an optional alias and expiry. Each request carries `X-Crusoe-Timestamp` and `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`, where the signature is an HMAC-SHA256 of the path, sorted query string, verb and timestamp. Keys inherit the roles of the user who made them (`org-admin`, `org-editor`, `org-reader`, `project-editor`, `project-reader`). Managed AI uses separate Intelligence API keys sent as a Bearer token. Service accounts appear in the API description and the Terraform provider 1.6.0, with no docs page found. |\n| Pricing | Pay per use ($0.04 / vCPU-hr) · Pay as you go, billed per second for on-demand VMs. Per GPU-hour, H200 $4.29, H100 $3.90, MI300X $3.45, A100 $2.00 to $2.30 and L40S $1.50. GB200, B200, MI355X and all spot prices are contact sales. Compute needs a non-prepaid credit card. $5 of introductory credits cover Serverless Inference and Fine-Tuning without a card. Ingress and egress are free (https://www.crusoe.ai/cloud/pricing). |\n| x402 | No · No x402, MPP or L402 in the docs index, the API description or the pricing page (checked 2026-10-09). |\n| Licence | Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository |\n| Tools exposed | 41 |\n| Packages | go: `github.com/crusoecloud/client-go`; npm: `@crusoeai/cloud-mcp` |\n| Source | https://github.com/crusoecloud/client-go |\n| Docs | https://docs.crusoecloud.com/ |\n| llms.txt | https://docs.crusoecloud.com/llms.txt |\n| Last release | 2026-10-08 |\n| npm downloads / week | 7 |\n| Surface graded | The REST API at `https://api.cloud.crusoe.ai/v1` (Swagger 2.0). The CLI, the Terraform provider and the preview MCP server are noted alongside |\n| MCP server | Preview, local, stdio, `npx -y @crusoeai/cloud-mcp` (0.1.6, MIT). 41 read-only tools named in the docs across discovery, compute, storage, networking, Kubernetes, audit logs, quotas and usage. Lists are cut to 50 items by default |\n| Free tier | $5 of introductory credits for Serverless Inference and Serverless Fine-Tuning with no payment method. None found for GPU machines |\n| GPUs | NVIDIA GB200, B300, B200, H200, H100, A100 and L40S, AMD MI355X and MI300X. L40S and A100 PCIe come in 1 to 10 GPU shapes, the others as 8-GPU or 4-GPU machines (https://docs.crusoecloud.com/compute/virtual-machines/overview) |\n| Orchestration | Crusoe Managed Kubernetes at $0.10 a cluster-hour, Managed Slurm, a container registry and instance templates with bulk create |\n| Scale to zero | None found. Self-Serve Deployments run a set replica count and bill until deleted. An on-demand VM can be stopped and is then billed only for its disks |\n| Cold start | No figure published. A VM in the `Creating` state can take up to a minute per the docs |\n| Billing basis | On-demand VMs per second in the running state. Reserved VMs for the whole commitment. Self-Serve Deployments per GPU-hour, Serverless Inference and Fine-Tuning per token. Ingress and egress are free |\n| Rate limits | None found for the infrastructure API. Serverless Inference allows 500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one, and returns `x-ratelimit-*` headers |\n| Errors | HTTP 400, 401, 403, 404 and 500 with a `code` and `message` body. No error catalogue found |\n| Pagination | `limit` with `next_token` and `prev_token`, or `page_size` with `next_page_token`, on 16 list calls. VM lists filter by id, name, type, location and state |\n| Credentials | Access key ID and secret key created in the console, with optional alias and expiry, deletable, inheriting the creator's roles. Separate Intelligence API keys for Managed AI. Service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0 |\n| Roles | `org-admin`, `org-editor`, `org-reader`, `project-editor` and `project-reader`. SSO through OIDC, MFA and SCIM |\n| Audit | 90 days of control-plane actions at `/organizations/{org_id}/audit-logs`, admins only, no read or list events (https://docs.crusoecloud.com/identity-and-security/audit-logs) |\n| SLA | 99.5 per cent monthly uptime per GPU virtual machine and per persistent disk volume, with credits of 10, 25 or 100 per cent, claimed within 30 days. Version 8.0, effective 21 July 2026 (https://legal.crusoe.ai/#service-level-agreements) |\n| Regions | Seven data centre zones in Texas, Ohio, Nevada, Virginia, Iceland (two) and Norway (https://docs.crusoecloud.com/locations) |\n| SDKs | Go `github.com/crusoecloud/client-go` v1.0.18 (1 October 2026, MIT, generated from the API description), Terraform provider 1.6.0 changelog entry of 8 October 2026, and a closed-source CLI |\n| Certifications | ISO 27001, ISO 42001 and SOC 2 Type I and II per https://www.crusoe.ai/cloud. The trust centre at trust.crusoe.ai is drawn by script and was not read |\n| Status | status.crusoecloud.com on Atlassian Statuspage, with components for GPU machines in six regions, networking, storage, Kubernetes, API, console, container registry and Intelligence Foundry |\n| Capabilities | compute.gpu, compute.containers, compute.batch, compute.endpoints |\n| Tags | hosted, usage-priced, openapi, llms-txt, mcp, cli, terraform, go, status-page, soc2, enterprise |\n| JSON | https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 66 | 13.2 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 79 | 12.8 |\n| Agent ergonomics | 13% | 16.2 | 45 | 7.3 |\n| Security \u0026 auth | 14% | 17.5 | 74 | 12.9 |\n| Payments \u0026 pricing | 10% | 12.5 | 30 | 3.8 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 76 | 6.7 |\n| Transparency \u0026 trust (editorial 64, provenance 90) | 7% | 8.8 | 77 | 6.7 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **63.4 → B** |\n\n### Why each score\n\n- Reliability 66: Graded as a hosted service on the REST API. Statuspage at status.crusoecloud.com with components per region and service (20). The history page shows, since August 2026, one critical incident (shared disks, Object Storage and the container registry unreachable in eu-norway1 for about 3 hours 54 minutes on 29 September), one minor incident (VM and Kubernetes cluster creation in us-east2 for about 7.5 hours on 2 September) and two with no stated impact; July was not on the page read (10). Rate limits carry numbers only for Serverless Inference (500,000 tokens and 30 requests a minute per model without a payment method, 2,000,000 and 600 with one); none were found for the infrastructure API, whose MCP server throttles itself to 60 requests a minute (8 of 15). Serverless Inference documents 429 and 503 with exponential backoff and `x-ratelimit-*` headers; no Retry-After, no idempotency keys and no retry guidance for infrastructure writes were found (8 of 15). SLA of 99.5 per cent a month per GPU virtual machine and per persistent disk, with credits of 10, 25 or 100 per cent (10). The v1 API is labelled Latest and the services graded are generally available; the MCP server is in preview (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 79: A Swagger 2.0 description for `/v1` and `/v1alpha5`, linked from the reference page and kept in `crusoecloud/client-go`, and an OpenAPI description for the Intelligence Foundry API (25). `llms.txt` and a Markdown twin of each docs page (10). Every one of the 257 operations in the repository copy has a one-line summary, 74 have a longer description, and fields are described; few say when not to call (11). 64 enums and 208 required lists, though `limit` is typed as a string and instance types and locations are plain strings; the file declares no security scheme (10). 1,231 examples with request and response samples, and 400, 401, 403, 404 and 500 responses with a `code` and `message` body; no error catalogue and 429 appears on one operation (10). Versioned paths, dated Crusoe Updates entries with RSS and Atom feeds, and tagged Go client releases; the updates do not list API changes field by field (13).\n- Agent ergonomics 45: Lists take `limit` or `page_size` on 16 of about 104 list calls, and VM lists filter by id, name, type, location and state; no field selection (12 of 25). Token pagination with next and previous tokens and a `sort` parameter where present; most lists return everything (12). Errors are an HTTP status with `code` and `message`, and long-running calls return an operation with `state` and `result` to poll; no documented list of error codes (10). No idempotency key or safe-retry guidance found; the preview MCP server has read tools only, and its annotations were not read (4). VM create needs a name, type, location and SSH key and installs a monitoring agent by default; the Go client is the only official SDK found, beside a CLI and a Terraform provider, and other languages must code the request signature (7).\n- Security \u0026 auth 74: Access key and secret key with optional expiry, deletable in the console or through `/users/tokens`. Requests are signed with HMAC-SHA256 and a timestamp, so no secret is sent and none travels in a URL. Keys inherit their creator's roles and cannot be narrowed further; service accounts with their own credentials appear in the API description and the Terraform provider 1.6.0 (24). `org-reader` and `project-reader` roles give read-only access and the MCP server exposes no write tools; no confirmation step for destructive API calls (14). Returns infrastructure metadata, and the MCP docs warn that it is sent to the assistant and that an agent with a shell can still run the CLI (10). Audit log of 90 days of control-plane actions with actor, IP, surface and result, readable through the API by admins; read events are not logged (13). security.txt valid until 1 March 2027 with no Policy field, ISO 27001, ISO 42001 and SOC 2 Type I and II claimed on the cloud page, customer-managed encryption keys; no bug bounty found, the trust centre was unreadable, and the apt install line sets `[trusted=yes]` (13).\n- Payments \u0026 pricing 30: No machine payment protocol (0). Per-GPU-hour, per-vCPU-hour, per-GiB and per-token prices published without a login, though spot prices and on-demand prices for GB200, B200 and MI355X are contact sales (20). $5 of introductory credits cover Serverless Inference and Serverless Fine-Tuning without a payment method; GPU machines, the product graded here, need a non-prepaid credit card (10 of 20). Signup is a browser flow with Google, GitHub or an emailed code, and the first key is made in the console (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 76: Crusoe Updates entries on 5, 7 and 8 October 2026 and a Terraform provider 1.6.0 changelog entry on 8 October (30). Go client tags v1.0.1 to v1.0.18 and seven Terraform provider tags since 11 July 2026, plus more than 20 dated updates (20). Closed service with a dated changelog and feeds, a support portal, email support and published support tiers; GitHub issue response times were not read (10 of 15). The Go client is current and generated from the API description, with the Terraform provider and CLI beside it; one language only, and the MCP package was not checked against the official registry (10 of 15). A lint workflow in the Terraform provider and GitLab CI configuration in the Go client; results were not read (6).\n- Transparency \u0026 trust 77: Closed service under Terms of Service version 1.10, effective 10 August 2026, with ten earlier versions kept on the legal page; the Go client and MCP package are MIT (15). The Privacy Notice (version 1.3, 12 March 2026) covers Service Data and the Data Processing and Security Terms (version 1.3, 14 July 2026) cover Customer Data, with deletion on instruction and at the end of the term, and the Intelligence Foundry terms say inputs, outputs and training data are not used to train models without opt-in consent; no retention periods are given in numbers (22). The terms promise 90 days' notice before discontinuing a service or changing a customer-facing API incompatibly, and a deprecation page gives dates such as 8 November 2026 for old CSI drivers, announced 15 September; model deprecations are logged on the day they take effect (17). Seven data centre zones are published; the data processing terms point to a sub-processor list that was not found in the pages read (10).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/crusoe-cloud.md (JSON https://www.anchorterminal.com/fixes/crusoe-cloud.json)\n\n### What we couldn't check\n\n- The lead named only the CLI and the Terraform provider. Crusoe also publishes a REST API with an API description, a Go client and a preview MCP server, and the API is the surface graded.\n- unchecked: the trust centre at trust.crusoe.ai is drawn by script, so certifications, the sub-processor list and any penetration test summary were not read. Certifications are taken from the product page as the vendor's claim.\n- unchecked: status history for July 2026. The history page read showed August to October only, and robots.txt closes the status API.\n- unchecked: the API description at `https://api.crusoecloud.com/v1/openapi.json` was not fetched. The copy in `crusoecloud/client-go` and the rendered reference page were read, and the two differ in operation count (257 and 164).\n- unchecked: GitHub issue response times, CI results, repository stars and CLI release dates. Tags in the CLI repository all carry one 2022 commit date.\n- unchecked: the tool definitions and annotations of `@crusoeai/cloud-mcp`. Its source is on a GitLab address that was not read, and the package was not downloaded or run. The count of 41 tools comes from the docs page.\n- No request rate limits or idempotency keys were found for the infrastructure API. They may exist in pages not read.\n- Whether a deprecated Serverless Inference model stops answering on the listed date, and how much notice customers had, was not established. The changelog entries are dated the day of deprecation.\n- Service accounts are in the API description and the Terraform provider 1.6.0, with no docs page found, so their scopes and token lifetimes are not established.\n- The create-an-account page says billing must be enabled to use managed inference, while the updates and rate-limit pages describe use on introductory credits with no payment method.\n- The Service Specific Terms require written consent before benchmark results are published and the Intelligence Foundry terms bar competitive analysis or benchmarking. The Acceptable Use Policy bars disruptive crawling or scraping and testing the services to find limitations. This matters before any Anchor Terminal probe runs.\n- `provenance.terms` and `provenance.privacy` are anchors on one 3.5 MB page that holds every legal document and its earlier versions, so the policy reader may need the section picked out by hand.\n- `compute.endpoints` rests on Self-Serve Deployments, which serve catalogue models and LoRA adapters, not a customer's own container. `compute.serverless` is left out.\n\n### Sources\n\n- docs index for agents: \u003chttps://docs.crusoecloud.com/llms.txt\u003e (seen 2026-10-09)\n- API authentication and base URL: \u003chttps://docs.crusoecloud.com/reference/api/\u003e (seen 2026-10-09)\n- API reference for v1, rendered page: \u003chttps://docs.crusoecloud.com/api/\u003e (seen 2026-10-09)\n- Intelligence Foundry API reference, rendered page: \u003chttps://docs.crusoecloud.com/api/managed-ai/\u003e (seen 2026-10-09)\n- API description file read from the Go client repository, not fetched from the API host: \u003chttps://github.com/crusoecloud/client-go\u003e (seen 2026-10-09)\n- MCP server docs: \u003chttps://docs.crusoecloud.com/reference/mcp-server.md\u003e (seen 2026-10-09)\n- API keys: \u003chttps://docs.crusoecloud.com/identity-and-security/managing-api-keys.md\u003e (seen 2026-10-09)\n- users and roles: \u003chttps://docs.crusoecloud.com/identity-and-security/managing-organization-users.md\u003e (seen 2026-10-09)\n- audit logs: \u003chttps://docs.crusoecloud.com/identity-and-security/audit-logs.md\u003e (seen 2026-10-09)\n- account creation and billing: \u003chttps://docs.crusoecloud.com/create-an-account.md\u003e (seen 2026-10-09)\n- Crusoe Updates: \u003chttps://docs.crusoecloud.com/updates\u003e (seen 2026-10-09)\n- deprecation notices: \u003chttps://docs.crusoecloud.com/resources/deprecation_notices.md\u003e (seen 2026-10-09)\n- Serverless Inference rate limits: \u003chttps://docs.crusoecloud.com/serverless-inference/rate-limits.md\u003e (seen 2026-10-09)\n- Serverless Inference models and deprecations: \u003chttps://docs.crusoecloud.com/serverless-inference/available-models.md\u003e (seen 2026-10-09)\n- Self-Serve Deployments quickstart: \u003chttps://docs.crusoecloud.com/quickstart/self-serve-deployments.md\u003e (seen 2026-10-09)\n- VM types, lifecycle and billing: \u003chttps://docs.crusoecloud.com/compute/virtual-machines/overview.md\u003e (seen 2026-10-09)\n- CLI install: \u003chttps://docs.crusoecloud.com/installing-the-cli.md\u003e (seen 2026-10-09)\n- quotas: \u003chttps://docs.crusoecloud.com/usage-billing/viewing-quotas.md\u003e (seen 2026-10-09)\n- spot instances: \u003chttps://docs.crusoecloud.com/usage-billing/spot.md\u003e (seen 2026-10-09)\n- locations: \u003chttps://docs.crusoecloud.com/locations.md\u003e (seen 2026-10-09)\n- support channels: \u003chttps://docs.crusoecloud.com/resources/support.md\u003e (seen 2026-10-09)\n- pricing: \u003chttps://www.crusoe.ai/cloud/pricing\u003e (seen 2026-10-09)\n- cloud product page, certification claims: \u003chttps://www.crusoe.ai/cloud\u003e (seen 2026-10-09)\n- security.txt: \u003chttps://www.crusoe.ai/.well-known/security.txt\u003e (seen 2026-10-09)\n- Terms of Service, version 1.10: \u003chttps://legal.crusoe.ai/#terms-of-service\u003e (seen 2026-10-09)\n- Crusoe Cloud Platform Privacy Notice, version 1.3: \u003chttps://legal.crusoe.ai/#cloud-privacy-policy\u003e (seen 2026-10-09)\n- Data Processing and Security Terms, version 1.3: \u003chttps://legal.crusoe.ai/#data-processing\u003e (seen 2026-10-09)\n- Service Level Agreements, version 8.0: \u003chttps://legal.crusoe.ai/#service-level-agreements\u003e (seen 2026-10-09)\n- Service Specific Terms, version 5.0: \u003chttps://legal.crusoe.ai/#service-specific-terms\u003e (seen 2026-10-09)\n- status page: \u003chttps://status.crusoecloud.com/\u003e (seen 2026-10-09)\n- status history: \u003chttps://status.crusoecloud.com/history\u003e (seen 2026-10-09)\n- storage incident of 29 September 2026: \u003chttps://status.crusoecloud.com/incidents/hp3xb537kdwy\u003e (seen 2026-10-09)\n- Terraform provider changelog and tags: \u003chttps://github.com/crusoecloud/terraform-provider-crusoe\u003e (seen 2026-10-09)\n- CLI repository: \u003chttps://github.com/crusoecloud/cli\u003e (seen 2026-10-09)\n- MCP package on npm: \u003chttps://registry.npmjs.org/@crusoeai/cloud-mcp/latest\u003e (seen 2026-10-09)\n- npm weekly downloads: \u003chttps://api.npmjs.org/downloads/point/last-week/@crusoeai/cloud-mcp\u003e (seen 2026-10-09)\n- RDAP for crusoe.ai: \u003chttps://rdap.identitydigital.services/rdap/domain/crusoe.ai\u003e (seen 2026-10-09)\n- RDAP for crusoecloud.com: \u003chttps://rdap.verisign.com/com/v1/domain/crusoecloud.com\u003e (seen 2026-10-09)\n\n## Who's behind it (provenance 90/100, checked 2026-10-09)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Crusoe Technologies LLC | 20/20 |\n| Domain age | crusoe.ai, registered 2019-01-28 (7 years) | 11/15 |\n| Endpoint on the vendor's domain | api.cloud.crusoe.ai | 15/15 |\n| Terms of service | published, but our reader couldn't read it | 7/10 |\n| Privacy policy | published, but our reader couldn't read it | 7/10 |\n| Status page | status.crusoecloud.com | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | valid | 10/10 |\n\nThe Crusoe Cloud Platform Terms of Service, version 1.10, effective 10 August 2026, are a contract with Crusoe Technologies LLC and its affiliates. Ten earlier versions are kept on the same page.\n\nlegal.crusoe.ai is one page that holds every legal document and its earlier versions, reached by anchor. The terms and privacy links point at the anchors for the platform terms and the Crusoe Cloud Platform Privacy Notice, not at the separate website terms and website privacy notice.\n\nThe Crusoe Cloud Platform Privacy Notice, version 1.3, effective 12 March 2026, covers Service Data only. Customer Data falls under the Data Processing and Security Terms, version 1.3, effective 14 July 2026.\n\nThe API reference gives `https://api.cloud.crusoe.ai/v1`, under the vendor domain. Other docs pages and the MCP server name `api.crusoecloud.com`, and Managed AI answers at `api.inference.crusoecloud.com` and `api.intelligence.crusoecloud.com`. crusoecloud.com was registered on 14 April 2020 per RDAP and redirects to www.crusoe.ai.\n\nsecurity.txt at www.crusoe.ai gives security@crusoe.ai and expires on 1 March 2027. It has no Policy field.\n\nRDAP for crusoe.ai gives a registration date of 2019-01-28. The website footer reads Crusoe, Inc, and the licence files in the CLI and Go client repositories name Crusoe Energy Systems LLC.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://legal.crusoe.ai/#terms-of-service), read 2026-10-09. Our reader couldn't read it (the page holds every legal document of the vendor and its past versions, so the one document the listing means cannot be read apart from the rest).\n\n\n**Privacy policy** (https://legal.crusoe.ai/#cloud-privacy-policy), read 2026-10-09. Our reader couldn't read it (the page holds every legal document of the vendor and its past versions, so the one document the listing means cannot be read apart from the rest).\n\n\n## Live (updated 2026-10-10 02:07 UTC)\n\n- Right now: up, HTTP 200, 143 ms, checked 2026-10-10 02:07 UTC (get on `https://api.cloud.crusoe.ai/v1`)\n- Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 193 ms · p95 307 ms\n- Vendor status page: none, All Systems Operational\n- npm `@crusoeai/cloud-mcp` 0.1.6\n- Watching changelog \u003chttps://docs.crusoecloud.com/updates\u003e\n- Watching pricing \u003chttps://www.crusoe.ai/cloud/pricing\u003e\n- Watching terms \u003chttps://legal.crusoe.ai/\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/crusoe-cloud.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| NVIDIA H100 80 GB HGX, on demand | $3.90 | per GPU-hour | Billed per second while running. Spot is contact sales |\n| NVIDIA H200 141 GB HGX, on demand | $4.29 | per GPU-hour | |\n| NVIDIA A100 80 GB SXM, on demand | $2.30 | per GPU-hour | |\n| NVIDIA A100 80 GB PCIe, on demand | $2 | per GPU-hour | |\n| NVIDIA L40S 48 GB, on demand | $1.50 | per GPU-hour | |\n| AMD MI300X 192 GB, on demand | $3.45 | per GPU-hour | |\n| NVIDIA H100, Self-Serve Deployment | $5.50 | per GPU-hour | Dedicated inference endpoint, billed until deleted. H200 $6.00, B200 $9.65, MI355X $7.40 |\n| General-purpose CPU instance | $0.04 | per vCPU-hour | Storage-optimised $0.09 |\n| Persistent disk | $0.08 | per GB per month | Per GiB. Shared disks $0.07, Object Storage $0.06 |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Requests are signed with HMAC-SHA256 over the path, query, verb and timestamp, so the secret key never travels with a request.\n- The API description is published for `/v1` and `/v1alpha5`, with 1,231 examples, and the docs serve `llms.txt` and a Markdown twin of each page.\n- On-demand prices are public and billed per second. H100 is $3.90 and H200 $4.29 a GPU-hour, with no charge for ingress or egress.\n- Organisation and project roles include read-only `org-reader` and `project-reader`, and the audit log keeps 90 days of control-plane actions readable through the API.\n- The Terms of Service promise 90 days' notice before a service is discontinued or a customer-facing API changes in a backwards-incompatible way.\n\n## Weaknesses\n\n- No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.\n- No request rate limits were found for the infrastructure API. Numbers are published only for Serverless Inference.\n- Spot prices and on-demand prices for GB200, B200 and MI355X are listed as contact sales, and provisioning compute needs a non-prepaid credit card.\n- The status page shows a critical storage incident in eu-norway1 on 29 September 2026 (about 3 hours 54 minutes) and a 7.5-hour VM and cluster creation fault in us-east2 on 2 September.\n- The Service Specific Terms let customers publish benchmark results only with Crusoe's written consent, and the Intelligence Foundry terms bar competitive analysis or benchmarking. Recorded as a fact, and it matters before any probe is run.\n\n## Before you call it (notes for agents)\n\n1. Sign every request. Build the payload from path, sorted query string, verb and `X-Crusoe-Timestamp`, HMAC-SHA256 it with the base64url-decoded secret, and send `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`.\n2. Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.\n3. Creates, updates and deletes return an operation. Poll the matching operations endpoint for `state`, and list existing resources by name before retrying a create, because no idempotency key was found.\n4. Managed AI uses separate Intelligence API keys and hosts, `api.inference.crusoecloud.com` for OpenAI-compatible calls and `api.intelligence.crusoecloud.com` for files and fine-tuning jobs.\n5. Delete a VM and its disks to stop charges. A stopped on-demand VM is not billed for compute, but its 128 GB OS disk still bills at $0.08 a GiB-month.\n\n## Connect\n\nInstall:\n\n```bash\nbrew install crusoecloud/cli/crusoe\n```\n\nFirst request:\n\n```bash\ncurl https://api.cloud.crusoe.ai/v1/capacities -H \"X-Crusoe-Timestamp: \u003cRFC3339 timestamp\u003e\" -H \"Authorization: Bearer \u003cversion:access_key_id:base64_encoded_signature\u003e\"\n```\n\nClaude Code:\n\n```bash\nclaude mcp add crusoe-cloud -- npx -y @crusoeai/cloud-mcp\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"crusoe-cloud\": {\n \"args\": [\n \"-y\",\n \"@crusoeai/cloud-mcp\"\n ],\n \"command\": \"npx\"\n }\n }\n}\n```\n\nThrough letme (picks today, calling later): https://letme.dev/crusoe-cloud. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Nebius AI Cloud | B | 67.2 | 259 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/nebius-ai-cloud.md |\n| Modal | B | 63.6 | 382 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/modal.md |\n| Verda | B | 62.3 | 438 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/verda.md |\n| CoreWeave | C | 61.5 | 465 | compute.gpu, compute.containers, compute.endpoints, compute.batch | no | https://www.anchorterminal.com/tools/coreweave.md |\n| Northflank | C | 61.3 | 470 | compute.gpu, compute.containers, compute.batch, compute.endpoints | no | https://www.anchorterminal.com/tools/northflank.md |\n| Beam | C | 55.5 | 654 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/beam.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The API reference page lists 164 operations for v1. The Swagger 2.0 file in `crusoecloud/client-go` (v1.0.18, 1 October 2026) has 257 operations on 170 paths, with service accounts, role bindings, Slurm and Intelligence Foundry deployments among them (source: \u003chttps://docs.crusoecloud.com/api/, https://github.com/crusoecloud/client-go\u003e)\n- The official MCP server `@crusoeai/cloud-mcp` is in preview, runs locally over stdio, reads credentials from `~/.crusoe/config` and has only read tools, with a client-side limit of 60 requests a minute (source: \u003chttps://docs.crusoecloud.com/reference/mcp-server\u003e)\n- Self-Serve Deployments (14 July 2026) create dedicated inference endpoints for catalogue models and LoRA adapters through `/v1/projects/{project_id}/foundry/selfserve/deployments`, billed per GPU-hour until deleted (source: \u003chttps://docs.crusoecloud.com/quickstart/self-serve-deployments\u003e)\n- Introductory credits of $5 cover Serverless Inference and Serverless Fine-Tuning without a payment method. GPU machines need billing enabled with a non-prepaid credit card (source: \u003chttps://docs.crusoecloud.com/updates, https://docs.crusoecloud.com/create-an-account\u003e)\n- Six Serverless Inference models were marked deprecated on 12 September and 2 October 2026, in changelog entries dated the same day and labelled Breaking. Kimi K2.6 had been added on 24 June 2026 (source: \u003chttps://docs.crusoecloud.com/serverless-inference/available-models\u003e)\n- The Service Specific Terms allow benchmark tests but require Crusoe's prior written consent to publish results, and the Intelligence Foundry terms forbid competitive analysis or benchmarking and exceeding rate limits (source: \u003chttps://legal.crusoe.ai/#service-specific-terms\u003e)\n- The Linux install instructions add the apt source with `[trusted=yes]`, which turns off signature checks for that repository. GitHub release assets carry a signed checksum file (source: \u003chttps://docs.crusoecloud.com/installing-the-cli, https://github.com/crusoecloud/cli\u003e)\n\n- #7 of 19 in Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 167 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Compare\n\n- [Baseten vs Crusoe Cloud](https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud.md): B 66.5 vs B 63.4\n- [Beam vs Crusoe Cloud](https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.md): C 55.5 vs B 63.4\n- [Cerebrium vs Crusoe Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.md): C 55.3 vs B 63.4\n- [CoreWeave vs Crusoe Cloud](https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud.md): C 61.5 vs B 63.4\n- [Crusoe Cloud vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints.md): B 63.4 vs B 64.5\n- [Crusoe Cloud vs Hyperbolic](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.md): B 63.4 vs D 48\n- [Crusoe Cloud vs Koyeb](https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.md): B 63.4 vs D 46.5\n- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md): B 63.4 vs D 50\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md): B 63.4 vs E 42.3\n- [Crusoe Cloud vs Modal](https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal.md): B 63.4 vs B 63.6\n- [Crusoe Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.md): B 63.4 vs B 67.2\n- [Crusoe Cloud vs Northflank](https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.md): B 63.4 vs C 61.3\n- [Crusoe Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy.md): B 63.4 vs B 63.6\n- [Crusoe Cloud vs Runpod](https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod.md): B 63.4 vs D 53.5\n- [Crusoe Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.md): B 63.4 vs C 56.1\n- [Crusoe Cloud vs Vast.ai](https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai.md): B 63.4 vs B 62.6\n- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.md): B 63.4 vs B 62.3\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on crusoe.ai or one of its subdomains, or the README of github.com/crusoecloud/client-go. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"crusoe-cloud\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/crusoe-cloud\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/crusoe-cloud.svg\" alt=\"Crusoe Cloud on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Crusoe Cloud on Anchor Terminal](https://www.anchorterminal.com/badges/crusoe-cloud.svg)](https://www.anchorterminal.com/tools/crusoe-cloud)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/crusoe-cloud\"\u003eCrusoe Cloud on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Crusoe Cloud is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/crusoe-cloud-dark.png\n- Light: https://www.anchorterminal.com/assets/share/crusoe-cloud-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "GPU \u0026 serverless compute", "url": "https://www.anchorterminal.com/categories/gpu-compute" }, { "name": "Crusoe Cloud", "url": "" } ], "description": "Crusoe Cloud rents NVIDIA and AMD GPU virtual machines with managed Kubernetes and Slurm, and runs hosted model inference, dedicated deployments and LoRA fine-tuning. Resources are managed through a REST API, a CLI, a Terraform provider and a Go client.", "facts": [ "rank #396 of 950", "API key auth", "0 desk reviews" ], "h1": "Crusoe Cloud", "image": "https://www.anchorterminal.com/assets/og/tools-crusoe-cloud.png", "path": "/tools/crusoe-cloud", "published": "2026-10-01", "section": "tools", "title": "Crusoe Cloud review (2026): pricing, alternatives and grade B", "toc": null, "updated": "2026-10-10", "url": "https://www.anchorterminal.com/tools/crusoe-cloud" }, "tokens": { "markdown": 9200, "slim": 2330 }, "version": 1 }