# RunPod AI integration on Definable

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

## What this connects

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

Vendor: https://www.runpod.io/

## Tools available

**13** tools available. First 12:

- `RUNPOD_CREATE_CLUSTER` — Create RunPod Cluster — Tool 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 HPC workloads.
- `RUNPOD_CREATE_SECRET` — Create Secret — Tool 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 via environment variables (RUNPOD_SECRET_<name>).
- `RUNPOD_DELETE_REGISTRY_AUTH` — Delete Container Registry Authentication — Tool to delete container registry authentication from RunPod. Use when you need to remove stored registry credentials.
- `RUNPOD_DELETE_TEMPLATE` — Delete Template — Tool 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 endpoints, otherwise the operation will fail.
- `RUNPOD_GET_GPU_TYPES` — Get GPU Types — Tool to retrieve available GPU types and their specifications, pricing, and availability from RunPod. Use when you need to find GPU options for deployment.
- `RUNPOD_GET_MYSELF` — Get authenticated user info — Retrieve basic information about the authenticated user including ID, email, and security settings. Use this to get the current user's ID, email address, terms of service status, and MFA settings. Note: Access to financial fields (balance, spending, etc.) requires elevated API key permissions.
- `RUNPOD_GET_POD` — Get Pod Details — Retrieve 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 of an existing pod.
- `RUNPOD_LIST_CPU_TYPES` — List CPU Types — Tool 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.
- `RUNPOD_SAVE_ENDPOINT` — Save Serverless Endpoint — Tool 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 parameters. Include 'id' parameter to update an existing endpoint, omit it to create a new one.
- `RUNPOD_SAVE_REGISTRY_AUTH` — Save Container Registry Authentication — Tool 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.
- `RUNPOD_SAVE_TEMPLATE` — Save Template — Tool 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 variables, and resource allocations. For serverless templates, always set volumeInGb to 0.
- `RUNPOD_UPDATE_REGISTRY_AUTH` — Update Registry Auth — Tool to update existing container registry authentication credentials in RunPod. Use when you need to modify the username or password for an existing registry authentication.

## Auth

Auth schemes: `API_KEY`.

## How agents use RunPod

Inside a Definable workflow, RunPod is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → RunPod** — the Researcher (GPT-5.5) pulls context from RunPod (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → RunPod** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into RunPod (create record, post message, draft email).
- **Designer / Engineer → Distributor → RunPod** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via RunPod (attach file, open PR comment, post status).

The Verifier checks every RunPod call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/
- ai models — https://definable.ai/apps/category/ai-models/

## Related

- HTML page: https://definable.ai/apps/runpod/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt