agentrunpod-cli

Wrap RunPod API calls to submit, inspect, and cancel serverless jobs.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/SebastianBoehler/agent-cli-utils --skill agentrunpod-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentrunpod-cli
Source: https://github.com/SebastianBoehler/agent-cli-utils/tree/main/skills/agentrunpod-cli
Command: npx skills add https://github.com/SebastianBoehler/agent-cli-utils --skill agentrunpod-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This wrapper provides a deterministic, env-configurable interface around RunPod to submit, inspect, and cancel serverless jobs, delivering structured output for downstream agents.

Core Features & Use Cases

  • Deterministic command wrapper for RunPod operations (submit, status, cancel).
  • Env-driven configuration for RUNPOD_API_KEY, RUNPOD_ENDPOINT_ID, and RUNPOD_BASE_URL.
  • Structured JSON/YAML output suitable for automation and integration with other tools.

Quick Start

Install the RunPod CLI, configure RUNPOD_API_KEY and RUNPOD_ENDPOINT_ID in your environment, and submit a test payload to observe the structured output.

Frequently Asked Questions about agentrunpod-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage RunPod serverless jobs from the command line?

You can submit, inspect, and cancel RunPod serverless jobs using a deterministic CLI wrapper that requires RUNPOD_API_KEY and RUNPOD_ENDPOINT_ID environment variables. It outputs structured JSON or YAML suitable for downstream automation and agent integration.

What environment variables do I need to configure for RunPod API automation?

RunPod API automation requires RUNPOD_API_KEY and RUNPOD_ENDPOINT_ID environment variables, with an optional RUNPOD_BASE_URL override. These variables enable deterministic configuration of endpoints and API keys for serverless job management.

Can I get structured JSON output from RunPod operations for downstream agents?

Yes, the RunPod wrapper CLI delivers structured JSON output by default for submit, status, and cancel operations. This structured format ensures seamless integration with downstream automation tools and agents.

How do I submit a test payload to a RunPod serverless endpoint?

Install the RunPod CLI, configure your RUNPOD_API_KEY and RUNPOD_ENDPOINT_ID environment variables, then submit a test payload via the deterministic command wrapper using the installed binary or go run.

What is the best way to integrate RunPod serverless execution with an agentic workflow?

Using a deterministic CLI wrapper provides a structured, env-configurable interface around RunPod to manage serverless jobs. It guarantees consistent JSON outputs that downstream agents can reliably parse and act upon.

Does the RunPod CLI wrapper require any specific runtime or dependencies?

The RunPod CLI wrapper operates with no listed dependencies and can run using the installed binary or go run. It requires a valid RUNPOD_API_KEY and RUNPOD_ENDPOINT_ID to interact with the serverless API.