Install
Showcase


Try itExperimental
See what an agent can do with Runpod before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$runpodctl --helprecorded 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: 4 free · 13 paid · 0 enterprise · 14 not stated in evidence
Follow the green: where the map greys out is where Runpod 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 · Versioning policy · API sandbox
Subscribe to events via webhooks
—–
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
~5/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
—0/10
Operate the product with natural-language commands
✓8/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
~4/10
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
—0/10
Choose from current-generation datacenter GPUs (H100/H200/B200 class) as well as cheaper previous-generation options
~4/10
See documented quotas and instance limits and raise them through a defined process
—0/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
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 | full | 9/10 | Tprobed⚿ | |
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 | |
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 | none | 0/10 | ||
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 | untested | none yet | |
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 | fullfree | 9/10 | Tprobed | |
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 | fullfree | 9/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | fullfree | 9/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/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 | fullpaid | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
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 | partial | 5/10 | Tprobed | |
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 | partialpaid | 4/10 | Tprobed | |
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 | ⚿ | |
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 | 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 | |
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 | |
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 | untested | none yet | |
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 | fullpaid | 9/10 | Cclaimed | |
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 | full | 8/10 | Cclaimed | |
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 | fullpaid | 8/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 | fullpaid | 8/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 | fullpaid | 7/10 | Cclaimed | |
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 | full | 7/10 | Xcommunity | |
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 | 5/10 | Cclaimed | |
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 | partial | 5/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 | ||
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 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 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 | n/a | 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 | full | 9/10 | Xcommunity | |
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 | fullpaid | 9/10 | Tprobed | |
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 | fullpaid | 8/10 | Cclaimed | |
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 | fullfree | 8/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 | fullpaid | 8/10 | Xcommunity | |
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 | 7/10 | Tprobed⚿ | |
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 | partial | 5/10 | Xcommunity | |
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 | partialpaid | 4/10 | Xcommunity | |
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 | partial | 4/10 | Tprobed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 3/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
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 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | 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 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 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 | |
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 | fullpaid | 8/10 | Xcommunity | |
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 | fullpaid | 7/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 | partialpaid | 6/10 | Cclaimed | |
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 | 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 30 stories with headroom
What would move Runpod’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.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
Runpod's evidence describes MCP servers and 'agent skills' that let EXTERNAL coding agents (Claude, Cursor, etc.) control Runpod resources — the reverse of an assistant built into Runpod's own product for users to delegate tasks to.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Evidence shows only a single fixed automatic behavior (auto-pay reloading balance below a threshold) and autoscaling to zero, neither of which constitutes a user-definable rules/event-trigger system.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Runpod's core product is a hosted GPU cloud/marketplace; while the CLI (runpodctl) is open source, there is no evidence of a self-hostable version of the actual compute-orchestration platform, control plane, or marketplace that a user could run on their own infrastructure.
Pricing billing — stories about pricing billing in this arenaRent spot or interruptible GPU capacity at a deep discount with clearly documented preemption semantics
nonemoves PA Scoreimpact 30
The evidence pack covers Runpod's on-demand Pods, Serverless per-second pricing, Community/Secure Cloud tiers, and long-term commitment discounts, but nowhere documents a spot/interruptible/preemptible GPU tier or any preemption semantics (e.g., notice period, reclaim behavior, discount percentage).
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Runpod documents API-key and OAuth ("Sign in with Runpod") authentication for its REST API and MCP servers, but no evidence describes scoped, role-based, or least-privilege API key creation (e.g., read-only or resource-limited keys) that a user could issue specifically for an agent.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
No evidence of webhook subscription/event notification support anywhere in the docs pack — Runpod offers REST API, CLI, MCP servers, and SSH access, but nothing about outbound event webhooks for job/pod status changes.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Runpod documents a versioned REST API (v1) with a live OpenAPI spec, but no evidence in the pack describes any deprecation policy, versioning changelog, or migration/support-window commitments for API versions — only a `/runpod:migrate rest` agent command is mentioned, which is a migration tool, not a policy.
Provisioning lifecycle — creating, updating, and tearing down resources across their lifecycleSet auto-shutdown timers or spend limits so a forgotten instance can't silently run up a huge bill
nonemoves PA Scoreimpact 20
The evidence pack shows Runpod billing is pay-per-second and includes an 'auto-pay' feature that reloads balance when low (the opposite of a spend cap), but there is no mention anywhere of auto-shutdown timers, idle-timeout limits, max-runtime settings, or spend/budget caps that would stop a forgotten Pod from accumulating charges.
Showing the top 8 of 30 — 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 map13 surfaces · 31 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Pods docs15 stories
- Open Jupyter or connect my IDE (VS Code/Cursor) to the instance in one step
- Expose ports to serve applications from my instance and connect instances over private networking
- SSH into my GPU instance with my own keys and get root-level control of the environment
- Run the product headlessly / in CI for automation
- I am billed at per-second or per-minute granularity and only while my instance is actually running
- Lock in reserved or committed-use discounts for sustained GPU capacity
- See the published per-GPU-hour price for every GPU type on a public pricing page without talking to sales
- Choose where my data is stored (region/residency)
- 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
- Run my own Docker image or custom machine template with my exact environment
- Launch from pre-built ML templates (PyTorch, CUDA, vLLM, ComfyUI) instead of assembling an environment from scratch
- Verify the provider's security and compliance posture (SOC 2, data handling, datacenter tiers) before putting proprietary models on it
API reference13 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Query the GPU catalog with live pricing and availability from a public or documented endpoint before committing any spend
- 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
- Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instances
Runpodctl docs10 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Build against official SDKs
- Set up automations that run autonomously in the background
- 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
Get started docs9 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Do everything through the API that I can do in the UI
- 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
- Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instances
Hacker News9 stories
- Open Jupyter or connect my IDE (VS Code/Cursor) to the instance in one step
- SSH into my GPU instance with my own keys and get root-level control of the environment
- Choose from current-generation datacenter GPUs (H100/H200/B200 class) as well as cheaper previous-generation options
- Do everything through the API that I can do in the UI
- 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
- Run my own Docker image or custom machine template with my exact environment
- Launch from pre-built ML templates (PyTorch, CUDA, vLLM, ComfyUI) instead of assembling an environment from scratch
- Verify the provider's security and compliance posture (SOC 2, data handling, datacenter tiers) before putting proprietary models on it
Pricing docs5 stories
- Choose from current-generation datacenter GPUs (H100/H200/B200 class) as well as cheaper previous-generation options
- Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cycle
- Query the GPU catalog with live pricing and availability from a public or documented endpoint before committing any spend
- See the published per-GPU-hour price for every GPU type on a public pricing page without talking to sales
- Choose where my data is stored (region/residency)
Serverless docs4 stories
- Set up automations that run autonomously in the background
- I am billed at per-second or per-minute granularity and only while my instance is actually running
- Start, stop, restart, and terminate instances programmatically and keep paying only for what is running
- Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instances
Storage docs4 stories
- Drive the product through a documented public API
- Export all of my data in open formats and leave
- 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
OpenAPI spec3 stories
Instant clusters docs2 stories
References docs2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$runpodctl --helpreproduced$ runpodctl --help runpodctl - manage your ai system. getting started: 1. get your api [redacted] at https://www.runpod.io/console/user/settings 2. run: runpodctl doctor (will prompt for [redacted] and save it) or: export RUNPOD_API_[redacted]=your-[redacted] resources: pod manage gpu pods serverless manage serverless endpoints (alias: sls) template manage templates (alias: tpl) hub browse the runpod hub model manage model repository network-volume manage network volumes (alias: nv) registry manage container registry auth (alias: reg) info: user show account info and balance (alias: me) gpu list available gpu types datacenter list datacenters and availability (alias: dc) billing view billing history utilities: doctor diagnose and fix cli issues ssh manage ssh [redacted]s and connections send/receive transfer files to/from pods deprecated get, create, remove, start, stop, exec, project, config, get models Usage: runpodctl [command] Available Commands: billing view billing history completion install shell completion datacenter list datacenters doctor diagnose and fix cli issues gpu list available gpu types help help about any command hub browse the runpod hub model manage model repository network-volume manage network volumes pod manage gpu pods receive receive files or folders registry manage container registry auth send send files or folders serverless manage serverless endpoints ssh manage ssh [redacted]s and connections template manage templates update update runpodctl cli user show account info version print the version Flags: -h, --help help for runpodctl -o, --output string output format (json, yaml) (default "json") -v, --version print the version of runpodctl Use "runpodctl [command] --help" for more information about a command.
$runpodctl version # installed via `brew install runpod/runpodctl/runpodctl`reproduced$ runpodctl version # installed via `brew install runpod/runpodctl/runpodctl` runpodctl 2.12.0-51ca7f0
$curl -s -X POST https://docs.runpod.io/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -s -X POST https://docs.runpod.io/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":"Runpod Documentation","version":"1.0.0"},"instructions":"This Model Context Protocol server provides search and retrieval tools for the Runpod Documentation 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. This server also exposes resources containing additional skill guidance; read the relev
$curl -si -X POST https://mcp.getrunpod.io/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://mcp.getrunpod.io/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401
access-control-allow-origin: *
access-control-expose-headers: Mcp-Session-Id, Content-Type, WWW-Authenticate
cache-control: public, max-age=0, must-revalidate
content-type: application/json
date: Sat, 05 Sep 2026 03:29:33 GMT
server: Vercel
strict-transport-security: max-age=63072000
www-authenticate: Bearer realm="mcp", resource_metadata="https://mcp.getrunpod.io/.well-known/oauth-protected-resource"
x-vercel-cache: MISS
x-vercel-id: sfo1::iad1::4s42v-1788578973759-2f686190d22f
{"error":"Missing or invalid Authorization header. Provide a Bearer [redacted]."}
$curl -s https://rest.runpod.io/v1/openapi.json | head -c 300 && curl -si https://rest.runpod.io/v1/podsreproduced$ curl -s https://rest.runpod.io/v1/openapi.json | head -c 300 && curl -si https://rest.runpod.io/v1/pods
{
"openapi": "3.0.3",
"info": {
"title": "Runpod API",
"description": "Public Rest API for managing Runpod programmatically.",
"version": "0.1.0",
"contact": {
"name": "help",
"url": "https://contact.runpod.io/hc/requests/new",
"email": "help@runpod.io"
}
HTTP/2 401
date: Sat, 05 Sep 2026 03:29:34 GMT
content-type: application/json
content-length: 0
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
12 of 20 testable claims verified · 1 contradicted → integrity 50/100
31 distinct capability claims found in Runpod’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
12
Verified
7
Unverified
1
Contradicted
12
Undersold
Verified (17)
“Guides users through creating an account and deploying their first GPU to run code remotely”
Provision an on-demand GPU instance from the console or API and be running code on it within minutesfullproof ↗
“Provides two official MCP servers that connect AI tools and coding agents directly to Runpod”
“Open-source CLI lets you manage Pods, Serverless endpoints, templates, volumes and models from your local machine”
“SSH gives secure, reliable full shell access to a running Pod for long-running processes”
SSH into my GPU instance with my own keys and get root-level control of the environmentfullproof ↗
“REST API v1 gives programmatic access to all Runpod compute resources for integration into apps and automation”
Drive the product through a documented public APIfullproof ↗
“Pre-built templates (e.g. PyTorch) skip manual dependency/environment setup and launch ready-to-go instantly”
Launch from pre-built ML templates (PyTorch, CUDA, vLLM, ComfyUI) instead of assembling an environment from scratchfullproof ↗
“Agents can create Pods, deploy Serverless endpoints, transfer files, or deploy code via natural-language instructions”
Operate the product with natural-language commandsfullproof ↗
“Deployed Pods can be accessed via SSH, web proxy, JupyterLab, or VS Code/Cursor for different workflows”
Open Jupyter or connect my IDE (VS Code/Cursor) to the instance in one stepfullproof ↗
“CLI lets you run Python functions on remote GPUs directly from your local terminal”
“CLI lets you run Python functions on remote GPUs directly from your local terminal”
Run the product headlessly / in CI for automationfullproof ↗
“Custom containers can be pulled from any compatible registry such as Docker Hub, GHCR, or Amazon ECR”
Run my own Docker image or custom machine template with my exact environmentfullproof ↗
“Secure Cloud runs on vetted infrastructure meeting SOC 2, ISO 27001, and PCI DSS compliance standards”
Verify the provider's security and compliance posture (SOC 2, data handling, datacenter tiers) before putting proprietary models on itpartialproof ↗
“CLI command lets you create a Pod directly specifying GPU type and image”
“CLI command lets you create a Pod directly specifying GPU type and image”
Provision an on-demand GPU instance from the console or API and be running code on it within minutesfullproof ↗
“CLI can diagnose issues and view account information in addition to managing resources”
“REST API supports managing Pods, endpoints, templates, volumes, and registries, authenticated via API key”
Drive the product through a documented public APIfullproof ↗
“Pods can be created, started, stopped, and terminated via console or CLI”
Start, stop, restart, and terminate instances programmatically and keep paying only for what is runningfullproof ↗
Unverified (12)
“Public Endpoints give instant API access to pre-deployed image/video/audio/text AI models with no infrastructure setup”
Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instancesfullproof ↗
“Instant Clusters offer fully managed multi-node compute with high-performance networking for distributed workloads”
Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cyclefullproof ↗
“S3-compatible API lets you manage files on network volumes without launching a Pod”
Move data in and out efficiently — S3-compatible endpoints, cloud-storage sync, or documented transfer toolingfullproof ↗
“Committing to a 3- or 6-month term unlocks significant discounts on compute costs”
Lock in reserved or committed-use discounts for sustained GPU capacitypartialproof ↗
“Deployed Pods can be accessed via SSH, web proxy, JupyterLab, or VS Code/Cursor for different workflows”
Expose ports to serve applications from my instance and connect instances over private networkingfullproof ↗
“Network volumes provide persistent storage that survives Pod termination or scale-to-zero”
Attach persistent network storage that survives instance teardown, so datasets and checkpoints outlive any single GPU rentalfullproof ↗
“Serverless is billed pay-per-second with no upfront cost, from worker start until it fully stops”
I am billed at per-second or per-minute granularity and only while my instance is actually runningfullproof ↗
“Serverless is billed pay-per-second with no upfront cost, from worker start until it fully stops”
Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instancesfullproof ↗
“Flex workers scale to zero when idle and use a standard per-second rate for variable workloads”
Deploy code to autoscaling serverless GPU workers that scale to zero, instead of managing always-on instancesfullproof ↗
“Network volumes can be used to share data across multiple machines and Runpod products”
Attach persistent network storage that survives instance teardown, so datasets and checkpoints outlive any single GPU rentalfullproof ↗
“Supports multi-node training to handle models too large for one GPU or to accelerate training across nodes”
Provision a multi-node GPU cluster with fast interconnect for distributed training without a sales cyclefullproof ↗
“Pods are billed by the second for compute and storage with no data ingress/egress fees”
I am billed at per-second or per-minute granularity and only while my instance is actually runningfullproof ↗
Contradicted (1)
“Runpod's CLI tool is open source”
Undersold (12)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Choose from current-generation datacenter GPUs (H100/H200/B200 class) as well as cheaper previous-generation optionspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Query the GPU catalog with live pricing and availability from a public or documented endpoint before committing any spendpartialproof ↗
See the published per-GPU-hour price for every GPU type on a public pricing page without talking to salespartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
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 consolefullproof ↗
Claims outside our story set (5)
Real capability claims found in Runpod’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.
“Coding agents can auto-migrate to REST API v1 by running a migrate skill command after installing the skills plugin”
source ↗“Auto-pay automatically reloads account balance below a threshold to avoid service interruptions”
source ↗“FlashBoot or model caching can minimize serverless worker cold-start times”
source ↗“Community Cloud connects individual compute providers to users via a vetted peer-to-peer system with competitive pricing”
source ↗“Offers thousands of GPUs available across 30+ regions”
source ↗
Pricing signals
- $3.49per GPU-hourpay-as-you-goPods: H100 SXM, Secure Cloud, per hour ratesource ↗as of 2026-09-07
- $1.59per GPU-hourpay-as-you-goPods: A100 SXM/PCIe per hour ratesource ↗as of 2026-09-07
- $0.27per GPU-hourpay-as-you-goPods: cheapest listed GPU, RTX A5000, per hoursource ↗as of 2026-09-07
- $4.79per GPU-hourpay-as-you-goServerless: H100 inference GPU per hoursource ↗as of 2026-09-07
Extracted verbatim from the vendor’s own pricing page — hover a figure for the exact quote.
Business model
Prepaid credits burn down against per-second billing for Pods and Serverless GPU workers, with published per-GPU-hour rates, savings plans, and custom enterprise capacity.
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)
