Skip to content
PlutusPlutusDocumentation

RunPod

What Plutus imports

Section titled “What Plutus imports”
  • Pod, Serverless endpoint, and network-volume spend
  • Spend and GPU-hours by GPU type

Connecting

Section titled “Connecting”

Method: API Key

  1. In the RunPod console, go to console.runpod.io → Settings → API Keys.
  2. Click Create API Key. A read-only key is enough — Plutus only calls RunPod’s billing endpoints and never creates or terminates any resource.
  3. Copy the key. RunPod only shows it once.
  4. In Plutus, paste the key into the API Key field and save.

Plutus pulls daily billed amounts from RunPod’s three billing endpoints — Pods, Serverless endpoints, and network volumes.

Notes

Section titled “Notes”

Costs come from RunPod’s own billing API, so these are billed amounts rather than an estimate. Pods and Serverless endpoints are broken down by their RunPod ID, which is what the billing API reports — RunPod does not return resource names on a billing record, and Pods are usually terminated once a job finishes.