RunPod for AI agents

Agents read RunPod at once. Changes and sends are held for a person's approval by default.

About RunPod

The Cloud Built for AI - GPU cloud computing platform for AI and machine learning workloads

What an agent can do in RunPod

Every RunPod action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in RunPod without asking first. 3 actions.

  • Get GPU TypesTool to retrieve available GPU types and their specifications, pricing, and availability from RunPod. Use when you need to find GPU options for deployment.
  • Get Pod DetailsRetrieve details of a specific RunPod pod by its unique pod ID. Returns pod configuration including GPU count, memory, cost, and status. Use when you need to check the current state or configuration o
  • List CPU TypesTool to retrieve available CPU types and their specifications from RunPod. Use when you need to view CPU options for provisioning pods or selecting hardware configurations.

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 9 actions.

  • Create RunPod ClusterTool to create a new GPU cluster for multi-node distributed computing workloads on RunPod. Use when you need to deploy multiple pods with shared configuration for parallel processing, ML training, or
  • Create SecretTool to create a new secure secret in RunPod for credential management. Use when you need to store sensitive values like API keys, passwords, or tokens that will be accessible in pods and endpoints vi
  • Delete Container Registry AuthenticationTool to delete container registry authentication from RunPod. Use when you need to remove stored registry credentials.
  • Delete TemplateTool to remove a RunPod template via GraphQL mutation. Use when you need to delete a template that is no longer needed. The template must not be in use by any pods or assigned to any serverless endpoi
  • Save Serverless EndpointTool to create or update a RunPod serverless endpoint with GPU configuration and scaling settings. Use when configuring new GPU-accelerated serverless endpoints or modifying existing endpoint paramete
  • Save Container Registry AuthenticationTool to save container registry authentication credentials for accessing private Docker images in RunPod. Use when you need to store credentials for a private container registry.
  • Save TemplateTool to create a new RunPod template or update an existing one with container configuration. Use when you need to define reusable pod/serverless configurations with specific images, environment variab
  • Update Registry AuthTool to update existing container registry authentication credentials in RunPod. Use when you need to modify the username or password for an existing registry authentication.
  • Update User SettingsTool to update current user settings (e.g., SSH public key) in RunPod. Use when you need to configure SSH access to pods by setting the user's SSH public key.

Changes wait in Needs you

Changes and sends in RunPod are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

RunPod questions

Can an agent change data in RunPod on its own?

Not by default. Changes and sends in RunPod are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in RunPod?

This connector lists 3 read actions. Reads run at once, without waiting for approval.

How does RunPod connect?

It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring RunPod to your agents.