Recued
Menu
← Back to packs

Registry Credentials and Billing - RunPod

by recued-core v1 app_pack 8 views

RunPod container-registry credential references plus Pod, Serverless endpoint, and network-volume billing history. Generated from the immutable official RunPod OpenAPI at docs commit 97887252ea4f07dd897c1c17f6ef12858e9a743b. This leaf carries 7 of the suite total 42 admitted operations. Pick the RunPod management connection whose Authorization header contains the complete bearer API-key value for rest.runpod.io. JSON request documents are sent verbatim, bounded query integers retain their safe numeric constraints, and unsafe JSON response integers remain exact strings. Reads are uncached and not approval-gated, and every private mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

What this pack installs

  • runpod-registry-billing Ingredient

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Destructive Web APIs runpod-registry-billing external change
Read: container_registry_auths.list_container_registry_auths · No approvalAdmin: container_registry_auths.create_container_registry_auth · Always asksRead: container_registry_auths.get_container_registry_auth · No approvalDestructive: container_registry_auths.delete_container_registry_auth · Always asksRead: billing.pod_billing · No approvalRead: billing.endpoint_billing · No approvalRead: billing.network_volume_billing · No approval

Data it touches

SurfacesWeb APIs

About

Tags

pack:runpodrunpodgpu-cloudregistry-authbillingcostsusageapicomposition