RunPod
GPU job lifecycle from RunPod.
PreviewServiceenv var
Source implementation only. Registry, marketplace, hosted installer, and publisher provenance remain unverified until the release checklist records a clean-machine receipt. Review and pin `server webhook normalizers`, minimize telemetry, and keep provider secrets outside Chirp payloads.
Setup
- 1Review and pin the source in
server webhook normalizers. - 2Inject a reviewed, narrowly scoped Chirp credential through the runtime's secret manager.
- 3Send only bounded status/usage metadata; never send the provider credential, prompts, source, or unredacted inputs.
- 4Verify provider acceptance and the phone's delivery acknowledgement separately. Never call an accepted event delivered.
shell
# Dashboard → Provider webhooks
# 1. Choose RunPod, label the destination, and set an expiry.
# 2. Create the credential and copy its one-time setup value.
#
# Provider console: paste the one-time provider-console URL.
# Programmable sender (preferred): POST to the clean endpoint with
# X-Chirp-Webhook-Token: <one-time chirp_wh_... token>
#
# Bound endpoint:
CHIRP_WEBHOOK_ENDPOINT="https://api.chirpapp.dev/v1/webhooks/runpod"
#
# Never substitute CHIRP_API_KEY; broad account keys are rejected here.