RunPod integration

Quick start

Call RunPod from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to RunPod's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "RUNPOD_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own RunPod API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

13 actions exposed via the RunPod integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• RUNPOD_CREATE_CLUSTER
• RUNPOD_CREATE_SECRET
• RUNPOD_DELETE_REGISTRY_AUTH
• RUNPOD_DELETE_TEMPLATE
• RUNPOD_GET_GPU_TYPES
• RUNPOD_GET_MYSELF
• RUNPOD_GET_POD
• RUNPOD_LIST_CPU_TYPES
• RUNPOD_SAVE_ENDPOINT
• RUNPOD_SAVE_REGISTRY_AUTH
• RUNPOD_SAVE_TEMPLATE
• RUNPOD_UPDATE_REGISTRY_AUTH