Access
Showcase


Try itExperimental
See what an agent can do with CoreWeave before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.coreweave.com/v1beta1/cks/clustersrecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Access connectivity — stories about access connectivity in this arenaAccess connectivityevidence →
Stories about access connectivity in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Capacity availability — stories about capacity availability in this arenaCapacity availabilityevidence →
Stories about capacity availability in this arena
Clusters scale — stories about clusters scale in this arenaClusters scaleevidence →
Stories about clusters scale in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing billing — stories about pricing billing in this arenaPricing billingevidence →
Stories about pricing billing in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycleevidence →
Creating, updating, and tearing down resources across their lifecycle
Serverless endpoints — stories about serverless endpoints in this arenaServerless endpointsevidence →
Stories about serverless endpoints in this arena
Storage data — storing and moving data — persistence, formats, durabilityStorage dataevidence →
Storing and moving data — persistence, formats, durability
Templates images — stories about templates images in this arenaTemplates imagesevidence →
Stories about templates images in this arena
Trust governance — stories about trust governance in this arenaTrust governanceevidence →
Stories about trust governance in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 7 paid · 0 enterprise · 14 not stated in evidence
Follow the green: where the map greys out is where CoreWeave stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Access connectivity — stories about access connectivity in this arenaAccess connectivity
Stories about access connectivity in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓9/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · API sandbox · Official CLI
Subscribe to events via webhooks
—–
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
~6/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
—0/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Capacity availability — stories about capacity availability in this arenaCapacity availability
Stories about capacity availability in this arena
See real-time GPU availability by type and region before I try to provision, instead of discovering stockouts by failure
~5/10
Choose from current-generation datacenter GPUs (H100/H200/B200 class) as well as cheaper previous-generation options
—–
See documented quotas and instance limits and raise them through a defined process
✓8/10
Clusters scale — stories about clusters scale in this arenaClusters scale
Stories about clusters scale in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing billing — stories about pricing billing in this arenaPricing billing
Stories about pricing billing in this arena
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle
Creating, updating, and tearing down resources across their lifecycle
Serverless endpoints — stories about serverless endpoints in this arenaServerless endpoints
Stories about serverless endpoints in this arena
Storage data — storing and moving data — persistence, formats, durabilityStorage data
Storing and moving data — persistence, formats, durability
Templates images — stories about templates images in this arenaTemplates images
Stories about templates images in this arena
Trust governance — stories about trust governance in this arenaTrust governance
Stories about trust governance in this arena
Sorted by importance (agentic first) (high → low) · 54/54 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed⚿ | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed⚿ | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed⚿ | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | 0/10 | ||
Provision a GPU, monitor it, run a workload, and tear it down end to end through documented APIs, CLI, or MCP without a human in the console C Agent ops | ai agent | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 3 | partialpaid | 6/10 | Tprobed⚿ | |
Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cycle C Clusters | ml engineer | Clusters scale — stories about clusters scale in this arenaClusters scale | 3 | partialpaid | 6/10 | Tprobed⚿ | |
Provision an on-demand GPU instance from the console or API and be running code on it within minutes C Provision | developer | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 3 | partialpaid | 6/10 | Tprobed⚿ | |
Attach persistent network storage that survives instance teardown, so datasets and checkpoints outlive any single GPU rental C Storage | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 3 | partial | 5/10 | Cclaimed | |
Rent spot or interruptible GPU capacity at a deep discount with clearly documented preemption semantics G Spot | ml engineer | Pricing billing — stories about pricing billing in this arenaPricing billing | 3 | partialpaid | 4/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 3/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 0/10 | ||
I am billed at per-second or per-minute granularity and only while my instance is actually running G Billing | ml engineer | Pricing billing — stories about pricing billing in this arenaPricing billing | 3 | none | 0/10 | ||
See the published per-GPU-hour price for every GPU type on a public pricing page without talking to sales G Pricing | ml engineer | Pricing billing — stories about pricing billing in this arenaPricing billing | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | 0/10 | ||
SSH into my GPU instance with my own keys and get root-level control of the environment C Ssh | developer | Access connectivity — stories about access connectivity in this arenaAccess connectivity | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Schedule jobs on managed Slurm or Kubernetes instead of building my own scheduler on raw nodes C Orchestration | platform engineer | Clusters scale — stories about clusters scale in this arenaClusters scale | 2 | fullpaid | 8/10 | Cclaimed | |
See documented quotas and instance limits and raise them through a defined process G Quotas | platform engineer | Capacity availability — stories about capacity availability in this arenaCapacity availability | 2 | full | 8/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed⚿ | |
Move data in and out efficiently — S3-compatible endpoints, cloud-storage sync, or documented transfer tooling C Data movement | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | partial | 6/10 | Cclaimed | |
Start, stop, restart, and terminate instances programmatically and keep paying only for what is running C Manage | developer | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 2 | partialpaid | 6/10 | Tprobed⚿ | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
See real-time GPU availability by type and region before I try to provision, instead of discovering stockouts by failure C Availability | ml engineer | Capacity availability — stories about capacity availability in this arenaCapacity availability | 2 | partial | 5/10 | Cclaimed | |
Pull usage and billing breakdowns programmatically to attribute GPU spend by team or workload G Billing | platform engineer | Pricing billing — stories about pricing billing in this arenaPricing billing | 2 | partial | 4/10 | Cclaimed | |
Run my own Docker image or custom machine template with my exact environment C Images | developer | Templates images — stories about templates images in this arenaTemplates images | 2 | partialpaid | 3/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instances C Serverless | developer | Serverless endpoints — stories about serverless endpoints in this arenaServerless endpoints | 2 | none | 0/10 | ||
Query the GPU catalog with live pricing and availability from a public or documented endpoint before committing any spend G Discovery | ai agent | Pricing billing — stories about pricing billing in this arenaPricing billing | 2 | none | 0/10 | ||
Set auto-shutdown timers or spend limits so a forgotten instance can't silently run up a huge bill C Manage | ml engineer | Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleProvisioning lifecycle | 2 | none | 0/10 | ||
Choose from current-generation datacenter GPUs (H100/H200/B200 class) as well as cheaper previous-generation options C Hardware | ml engineer | Capacity availability — stories about capacity availability in this arenaCapacity availability | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Launch from pre-built ML templates (PyTorch, CUDA, vLLM, ComfyUI) instead of assembling an environment from scratch C Templates | developer | Templates images — stories about templates images in this arenaTemplates images | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Verify the provider's security and compliance posture (SOC 2, data handling, datacenter tiers) before putting proprietary models on it C Compliance | platform engineer | Trust governance — stories about trust governance in this arenaTrust governance | 2 | none | untested | none yet | |
Manage team members with roles and scoped API keys so credentials and spend stay controlled G Governance | platform engineer | Trust governance — stories about trust governance in this arenaTrust governance | 1 | partial | 4/10 | Cclaimed | |
Lock in reserved or committed-use discounts for sustained GPU capacity G Pricing | platform engineer | Pricing billing — stories about pricing billing in this arenaPricing billing | 1 | none | 0/10 | ||
Open Jupyter or connect my IDE (VS Code/Cursor) to the instance in one step C Ide | developer | Access connectivity — stories about access connectivity in this arenaAccess connectivity | 1 | none | 0/10 | ||
Expose ports to serve applications from my instance and connect instances over private networking C Networking | developer | Access connectivity — stories about access connectivity in this arenaAccess connectivity | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 42 stories with headroom
What would move CoreWeave’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
CoreWeave's docs only describe fixed Kubernetes Cluster Autoscaler behavior reacting to resource demand, not a general-purpose rules/automation engine where users define custom event-trigger-action logic; no evidence of webhooks, alert-based actions, or configurable automation rules.
Pricing billing — stories about pricing billing in this arenaI am billed at per-second or per-minute granularity and only while my instance is actually running
nonemoves PA Scoreimpact 30
Docs mention pay-as-you-go, on-demand/spot capacity, and billing insights showing usage breakdowns, but no evidence specifies per-second or per-minute billing granularity or confirms billing only occurs while instances are actively running.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
CoreWeave is an infrastructure/GPU cloud provider; the evidence pack contains no privacy policy, data usage terms, or opt-out mechanism regarding AI model training on customer data.
Access connectivity — stories about access connectivity in this arenaSSH into my GPU instance with my own keys and get root-level control of the environment
nonemoves PA Scoreimpact 30
CoreWeave's documented access model is Kubernetes-native (kubeconfig + API tokens via CKS) rather than traditional SSH-with-your-own-keys into a GPU instance; no docs mention SSH key injection, root shell access, or instance-level SSH at all — access is described purely in terms of kubectl/API authentication to clusters running on bare metal without VMs.
Pricing billing — stories about pricing billing in this arenaSee the published per-GPU-hour price for every GPU type on a public pricing page without talking to sales
nonemoves PA Scoreimpact 30
The only pricing-related evidence is a marketing snippet from coreweave.com/pricing touting 'flexibility of great pricing' for on-demand/spot GPUs, but no evidence shows an actual published per-GPU-hour price table or rate card visible without contacting sales.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
CoreWeave's documented interfaces are structured (Cloud Console, Terraform/OpenTofu, REST/gRPC API, kubectl) with no evidence of a natural-language command interface for operating clusters, node pools, or inference deployments.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
CoreWeave's docs describe API access tokens, a Terraform/OpenTofu provider, generated gRPC/Connect clients, and kubectl via kubeconfig, but no evidence of a dedicated official CoreWeave CLI tool exists in the pack.
Showing the top 8 of 42 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 21 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Products docs16 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Perform bulk operations across many items at once
- See real-time GPU availability by type and region before I try to provision, instead of discovering stockouts by failure
- See documented quotas and instance limits and raise them through a defined process
- Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cycle
- Schedule jobs on managed Slurm or Kubernetes instead of building my own scheduler on raw nodes
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Provision a GPU, monitor it, run a workload, and tear it down end to end through documented APIs, CLI, or MCP without a human in the console
- Start, stop, restart, and terminate instances programmatically and keep paying only for what is running
- Provision an on-demand GPU instance from the console or API and be running code on it within minutes
- Move data in and out efficiently — S3-compatible endpoints, cloud-storage sync, or documented transfer tooling
- Attach persistent network storage that survives instance teardown, so datasets and checkpoints outlive any single GPU rental
- Run my own Docker image or custom machine template with my exact environment
Platform docs14 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Perform bulk operations across many items at once
- See real-time GPU availability by type and region before I try to provision, instead of discovering stockouts by failure
- See documented quotas and instance limits and raise them through a defined process
- Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cycle
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Rent spot or interruptible GPU capacity at a deep discount with clearly documented preemption semantics
- Provision a GPU, monitor it, run a workload, and tear it down end to end through documented APIs, CLI, or MCP without a human in the console
- Start, stop, restart, and terminate instances programmatically and keep paying only for what is running
- Provision an on-demand GPU instance from the console or API and be running code on it within minutes
- Move data in and out efficiently — S3-compatible endpoints, cloud-storage sync, or documented transfer tooling
Billing docs5 stories
- Do everything through the API that I can do in the UI
- Pull usage and billing breakdowns programmatically to attribute GPU spend by team or workload
- Provision a GPU, monitor it, run a workload, and tear it down end to end through documented APIs, CLI, or MCP without a human in the console
- Start, stop, restart, and terminate instances programmatically and keep paying only for what is running
- Manage team members with roles and scoped API keys so credentials and spend stay controlled
Security docs5 stories
- Run the product headlessly / in CI for automation
- Export all of my data in open formats and leave
- Provision a GPU, monitor it, run a workload, and tear it down end to end through documented APIs, CLI, or MCP without a human in the console
- Provision an on-demand GPU instance from the console or API and be running code on it within minutes
- Manage team members with roles and scoped API keys so credentials and spend stay controlled
Pricing docs4 stories
- Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cycle
- Rent spot or interruptible GPU capacity at a deep discount with clearly documented preemption semantics
- Start, stop, restart, and terminate instances programmatically and keep paying only for what is running
- Provision an on-demand GPU instance from the console or API and be running code on it within minutes
MCP docs3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.coreweave.com/v1beta1/cks/clustersreproduced$ curl -si https://api.coreweave.com/v1beta1/cks/clusters HTTP/2 401 date: Sat, 05 Sep 2026 03:29:35 GMT content-length: 0 cf-cache-status: DYNAMIC
$curl -s -X POST https://docs.coreweave.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -s -X POST https://docs.coreweave.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
event: message
data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"resources":{"listChanged":true}},"serverInfo":{"name":"CoreWeave Docs","version":"1.0.0"},"instructions":"This Model Context Protocol server provides search and retrieval tools for the CoreWeave Docs site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. If you find a problem with the documentation — a page that is incorrect, outdated, confusing, or
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 13 testable claims verified · 2 contradicted → integrity 0/100
19 distinct capability claims found in CoreWeave’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
7
Unverified
2
Contradicted
10
Undersold
Verified (5)
“Deploy multiple Node Pools in one cluster to run different workload types or scale parts independently”
Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cyclepartialproof ↗
“API to create, list, update, and delete managed Kubernetes clusters”
Drive the product through a documented public APIfullproof ↗
“Official generated clients available for Connect/gRPC/Protobuf across Go, Python, TypeScript, Java, Kotlin, Rust, and Swift”
“Spin up on-demand or spot GPU capacity quickly for burst workloads without long-term commitments”
Provision an on-demand GPU instance from the console or API and be running code on it within minutespartialproof ↗
“Inference API can be called over multiple transport protocols depending on client tooling and performance needs”
Drive the product through a documented public APIfullproof ↗
Unverified (8)
“Spot Node Pools give pay-as-you-go bare-metal compute with no long-term commitment”
Rent spot or interruptible GPU capacity at a deep discount with clearly documented preemption semanticspartialproof ↗
“S3-compatible storage lets you store training data, checkpoints, and weights with direct access to GPU compute”
Move data in and out efficiently — S3-compatible endpoints, cloud-storage sync, or documented transfer toolingpartialproof ↗
“S3-compatible storage lets you store training data, checkpoints, and weights with direct access to GPU compute”
Attach persistent network storage that survives instance teardown, so datasets and checkpoints outlive any single GPU rentalpartialproof ↗
“Run Slurm jobs inside Kubernetes so training and inference share the same cluster's compute resources”
Schedule jobs on managed Slurm or Kubernetes instead of building my own scheduler on raw nodesfullproof ↗
“View quotas, interpret quota errors, and request capacity increases in the Cloud Console”
See documented quotas and instance limits and raise them through a defined processfullproof ↗
“Billing insights show billable resource usage and consumption broken down by resource type”
Pull usage and billing breakdowns programmatically to attribute GPU spend by team or workloadpartialproof ↗
“Capacity Finder in the Cloud Console compares GPU placement availability across zones before provisioning”
See real-time GPU availability by type and region before I try to provision, instead of discovering stockouts by failurepartialproof ↗
“CKS is a managed Kubernetes service that runs clusters on bare metal servers in CoreWeave Cloud”
Schedule jobs on managed Slurm or Kubernetes instead of building my own scheduler on raw nodesfullproof ↗
Contradicted (2)
“API requests are authenticated with a Bearer token access credential”
Issue scoped/least-privilege API credentials for an agentnoneproof ↗
“Inference API gives programmatic control over inference gateways, model deployments, and capacity claims”
Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instancesnoneproof ↗
Undersold (10)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Provision a GPU, monitor it, run a workload, and tear it down end to end through documented APIs, CLI, or MCP without a human in the consolepartialproof ↗
Start, stop, restart, and terminate instances programmatically and keep paying only for what is runningpartialproof ↗
Run my own Docker image or custom machine template with my exact environmentpartialproof ↗
Manage team members with roles and scoped API keys so credentials and spend stay controlledpartialproof ↗
Claims outside our story set (5)
Real capability claims found in CoreWeave’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Create a CKS Kubernetes cluster via the Cloud Console or Terraform”
source ↗“Autoscale Node Pools with the Kubernetes Cluster Autoscaler based on GPU/CPU/memory demand”
source ↗“Terraform provider manages CKS clusters, VPC networking, storage, and inference resources as code”
source ↗“Download a kubeconfig to interact with a cluster via kubectl”
source ↗“CKS runs Kubernetes directly on bare metal nodes with no hypervisor or customer VMs”
source ↗
Pricing signals
- $6.16per GPU-hourpay-as-you-goNVIDIA HGX H100 inference single-GPU price (North America), applicable to CoreWeave inference platform customerssource ↗as of 2026-09-07
- $2.7per GPU-hourpay-as-you-goNVIDIA A100 inference single-GPU price (North America)source ↗as of 2026-09-07
- $49.24per instance-hourpay-as-you-goOn-demand price for 8x NVIDIA HGX H100 instance (North America)source ↗as of 2026-09-07
- $21.6per instance-hourpay-as-you-goOn-demand price for 8x NVIDIA A100 instance (North America)source ↗as of 2026-09-07
- $6.5per instance-hourpay-as-you-goOn-demand price for single-GPU NVIDIA GH200 instance (North America)source ↗as of 2026-09-07
Extracted verbatim from the vendor’s own pricing page — hover a figure for the exact quote.
Business model
Published per-GPU-hour instance pricing billed by usage, with Spot node pools, reserved capacity plans, and large committed enterprise contracts for dedicated clusters.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP 100% · llms.txt 100% (30d, checked every 6h since Sep 8 '26)
