Alias
You can usesls as a shorthand for serverless:
Subcommands
List endpoints
List all your Serverless endpoints:List flags
Include the endpoint’s container configuration in the output: image, start command or Docker arguments, disk size, environment variables, and ports. Environment variable values may contain secrets.
Get endpoint details
Get detailed information about a specific endpoint:--include-template.
Get flags
Include the endpoint’s container configuration in the output: image, start command or Docker arguments, disk size, environment variables, and ports. Environment variable values may contain secrets.
Create an endpoint
Create a new Serverless endpoint from a template or from a Hub repo:--hub-id, GPU IDs and container disk size are automatically pulled from the Hub release config. You can override the GPU type with --gpu-id. Environment variables from the Hub release are included automatically, and you can override or add to them with --env.
Serverless templates vs Pod templates: Serverless endpoints require a Serverless-specific template. Pod templates (like
runpod-torch-v21) cannot be used because they include configuration, which Serverless does not support. When creating a template with runpodctl template create, use the --serverless flag to create a Serverless template.Each Serverless template can only be bound to one endpoint at a time. To create multiple endpoints with the same configuration, create separate templates for each.Create flags
Name for the endpoint. Must be at least 3 characters. If omitted, a name is auto-generated in the format
endpoint-XXXXXXXX.Template ID to use (required if
--hub-id is not specified). Use runpodctl template search to find templates.Hub listing ID to deploy from (alternative to
--template-id). Use runpodctl hub search to find repos.GPU type for workers. Accepts either a GPU type ID (e.g.,
NVIDIA A40, NVIDIA GeForce RTX 4090) or a GPU pool ID (e.g., ADA_24, AMPERE_48). Use runpodctl gpu list to see available GPUs.Compute type (
GPU or CPU). For CPU endpoints, use --instance-id to specify the CPU instance type.CPU instance ID when using
--compute-type CPU. If omitted, defaults to cpu3g-4-16. Only valid with --compute-type CPU.Comma-separated list of preferred datacenter IDs. Use
runpodctl datacenter list to see available datacenters.Network volume ID to attach for single-region deployments. Use
runpodctl network-volume list to see available network volumes. Mutually exclusive with --network-volume-ids.Comma-separated list of network volume IDs for multi-region deployments. Mutually exclusive with
--network-volume-id.Minimum CUDA version required for workers (e.g.,
12.4). Workers will only be scheduled on machines that meet this CUDA version requirement.Autoscaling strategy:
delay (scales based on queue wait time in seconds) or requests (scales based on pending request count).Trigger point for the autoscaler. For
delay, this is the target queue wait time in seconds. For requests, this is the pending request count that triggers scaling.Idle timeout in seconds. Workers shut down after being idle for this duration. Valid range: 1-3600 seconds.
Enable or disable flash boot for faster worker startup. When enabled, workers start from cached container images.
Execution timeout in seconds. Jobs that exceed this duration are terminated. The CLI accepts seconds but converts to milliseconds internally.
Environment variable in
KEY=VALUE format. Use multiple --env flags to set multiple variables. These values only apply when deploying from --hub-id, where they override the Hub release defaults. With --template-id, environment variables come from the template, so --env is ignored and the CLI prints a note to that effect.Model reference URL to attach to the endpoint. Use multiple
--model-reference flags to attach multiple models. Works with both --template-id and --hub-id, and requires GPU compute type.Block until the endpoint’s health reports a worker that is ready or running. A ready worker may be restored from FlashBoot, so the first request can still take longer. Setting
--workers-min 1 is the fastest way to get a worker.Maximum time to wait with
--wait, such as 90s, 10m, or 1h (default 10m). On timeout, the endpoint is kept and the error includes its ID.Update an endpoint
Update endpoint configuration:Update flags
New template ID to swap to. Use this to change the template attached to an existing endpoint without recreating it.
Autoscaling strategy:
delay (scales based on queue wait time in seconds) or requests (scales based on pending request count). Setting only --scale-by keeps the current threshold.Trigger point for the autoscaler. For
delay, this is the queue wait time in seconds. For requests, this is the pending request count. Switching from a fractional delay to requests requires an integer threshold.Model reference to cache on the endpoint. Use multiple
--model-reference flags to attach multiple models. The references you pass replace the endpoint’s existing model references.--idle-timeout doesn’t apply to queue-based endpoints that scale by request count.
Delete an endpoint
Delete an endpoint:Send a request
Send a JSON payload to an endpoint and wait for the job to finish:{"input": YOUR_PAYLOAD}, so wrapping it in input yourself nests it twice.
The command submits the job with /run and polls /status until the job reaches a final state. If the wait runs out, the job keeps running on the endpoint: the CLI prints the last job payload, reports a timeout error that names the serverless status command to use, and exits with code 1. Check the job with serverless status instead of sending the request again, which would start a second job.
The command exits with code 0 when the job is COMPLETED, or when --no-wait submitted it successfully. It exits with code 1 when the request fails, the wait runs out, or the job ends as FAILED, CANCELLED, or TIMED_OUT. The job payload is printed in every case.
Run flags
Submit the job and print its ID without waiting. Same as
--wait 0, and can’t be combined with an explicit --wait.Check a job
Get the status of a job you submitted earlier, for example withserverless run --no-wait:
COMPLETED or still queued or running. It exits with code 1 when the job ended as FAILED, CANCELLED, or TIMED_OUT, or when --wait ran out.
Status flags
Check endpoint health
Get worker counts by state and job counts by outcome:Read worker logs
Read the logs of the workers behind an endpoint:source, line, ts, and workerId fields, so you can pipe it to jq. Logs belong to workers, so without --worker the command reads every worker on the endpoint and tags each line with its worker ID. With --follow, it reconnects if the connection drops and picks up workers that start while it runs.
Repeated system lines about starting the container with no container output usually mean the container exits before your handler runs.
Logs flags
Keep streaming new lines until you interrupt the command. Without it, the command replays recent lines and exits once they stop arriving.
Number of historical lines to replay before live output, from 0 to 5000 (default
100). Use 0 for live output only.Only show logs after this point: a duration such as
30m, 2h, or 7d, or an RFC 3339 timestamp. Overrides --tail.Which log source to read:
container (your workload’s own output), system (platform events such as image pull, container create, and start), or both (default).How long to wait for output before exiting when not following (default
5s). The command exits earlier once the replayed lines stop arriving.Show environment variable overrides
Show the environment variables set directly on an endpoint. These override the template’s defaults and are what the running container receives:runpodctl template get shows.
Check model status
Show an endpoint’s model references and, for each worker, the resolved model version, assignment status, and expected mount path:FAILED status includes a failurePhase (download_failed, mount_failed, startup_failed, or cuda_failed) and a failureReason. For the full detail, run runpodctl serverless logs <endpoint-id> --source system.