RunPod
for LuumenAI
Check GPU pricing and pod state, then change RunPod config as an approved step
Connect RunPod and Luumen can read your GPU and CPU type catalog, current pricing and availability, and the details of any running pod. When something needs to change — a serverless endpoint, a template, registry credentials — the agent shows the plan first and waits for your approval before it writes. Authentication is by API key.
The RunPod toolbox
13 tools: 4 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet GPU TypesRetrieve available GPU types and their specifications, pricing, and availability from RunPod.
- ReadGet authenticated user infoRetrieve basic information about the authenticated user including ID, email, and security settings.
- ReadGet Pod DetailsRetrieve details of a specific RunPod pod by its unique pod ID.
- ReadList CPU TypesRetrieve available CPU types and their specifications from RunPod.
- WriteCreate RunPod ClusterCreate a new GPU cluster for multi-node distributed computing workloads on RunPod. Approval by default
- WriteCreate SecretCreate a new secure secret in RunPod for credential management. Approval by default
- WriteDelete Container Registry AuthenticationDelete container registry authentication from RunPod. Approval by default
- WriteDelete TemplateRemove a RunPod template via GraphQL mutation. Approval by default
- WriteSave Serverless EndpointCreate or update a RunPod serverless endpoint with GPU configuration and scaling settings. Approval by default
- WriteSave Container Registry AuthenticationSave container registry authentication credentials for accessing private Docker images in RunPod. Approval by default
- WriteSave TemplateCreate a new RunPod template or update an existing one with container configuration. Approval by default
- WriteUpdate Registry AuthUpdate existing container registry authentication credentials in RunPod. Approval by default
- WriteUpdate User SettingsUpdate current user settings (e.g., SSH public key) in RunPod. Approval by default
One prompt, start to finish
What a governed RunPod run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create runpod cluster, create secret, delete container registry authentication, delete template, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to RunPod — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put RunPod to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.