Merge branch 'main' into custom-template-2

Author: muhsinking

docs.json

@@ -145,13 +145,10 @@
             "pages": ["storage/network-volumes", "storage/s3-api"]
           },
           {
-            "group": "Hub",
+            "group": "Public Endpoints",
             "pages": [
-              "hub/overview",
               "hub/public-endpoints",
-              "hub/public-endpoint-reference",
-              "hub/publishing-guide",
-              "hub/revenue-sharing"
+              "hub/public-endpoint-reference"
             ]
           },
           {
@@ -173,6 +170,14 @@
             "group": "Fine-tuning",
             "pages": ["fine-tune"]
           },
+          {
+            "group": "Hub",
+            "pages": [
+              "hub/overview",
+              "hub/publishing-guide",
+              "hub/revenue-sharing"
+            ]
+          },
           {
             "group": "Reference",
             "pages": [
@@ -335,31 +340,24 @@
         "tab": "CLI",
         "groups": [
           {
-            "group": "Get started",
-            "pages": ["runpodctl/overview", "runpodctl/install-runpodctl"]
+            "group": "Runpod CLI",
+            "pages": ["runpodctl/overview"]
           },
           {
             "group": "Reference",
             "pages": [
-              "runpodctl/reference/runpodctl",
               "runpodctl/reference/runpodctl-config",
-              "runpodctl/reference/runpodctl-create",
               "runpodctl/reference/runpodctl-create-pod",
               "runpodctl/reference/runpodctl-create-pods",
-              "runpodctl/reference/runpodctl-get",
               "runpodctl/reference/runpodctl-get-cloud",
               "runpodctl/reference/runpodctl-get-pod",
               "runpodctl/reference/runpodctl-receive",
-              "runpodctl/reference/runpodctl-remove",
               "runpodctl/reference/runpodctl-remove-pod",
               "runpodctl/reference/runpodctl-remove-pods",
               "runpodctl/reference/runpodctl-send",
-              "runpodctl/reference/runpodctl-ssh",
               "runpodctl/reference/runpodctl-ssh-add-key",
               "runpodctl/reference/runpodctl-ssh-list-keys",
-              "runpodctl/reference/runpodctl-start",
               "runpodctl/reference/runpodctl-start-pod",
-              "runpodctl/reference/runpodctl-stop",
               "runpodctl/reference/runpodctl-stop-pod",
               "runpodctl/reference/runpodctl-update",
               "runpodctl/reference/runpodctl-version"
@@ -474,6 +472,10 @@
   },
 
   "redirects": [        
+    {
+      "source": "/runpodctl/install-runpodctl",
+      "destination": "/runpodctl/overview"
+    },
     {
       "source": "/references/faq",
       "destination": "/references/troubleshooting/zero-gpus"
@@ -643,6 +645,34 @@
     {
       "source": "/references/faq/manage-cards",
       "destination": "/references/troubleshooting/manage-payment-cards"
+    },
+    {
+      "source": "/runpodctl/reference/create",
+      "destination": "/runpodctl/overview"
+    },
+    {
+      "source": "/runpodctl/reference/get",
+      "destination": "/runpodctl/overview"
+    },
+    {
+      "source": "/runpodctl/reference/remove",
+      "destination": "/runpodctl/overview"
+    },
+    {
+      "source": "/runpodctl/reference/start",
+      "destination": "/runpodctl/overview"
+    },
+    {
+      "source": "/runpodctl/reference/stop",
+      "destination": "/runpodctl/overview"
+    },
+    {
+      "source": "/runpodctl/reference/ssh",
+      "destination": "/runpodctl/overview"
+    },
+    {
+      "source": "/runpodctl/reference/runpodctl",
+      "destination": "/runpodctl/overview"
     }
   ]
 }

get-started/manage-accounts.mdx

@@ -63,6 +63,7 @@ Runpod provides four distinct roles to control access within team accounts. Each
 | Send requests to Serverless endpoints | ✅ | ❌ | ✅ | ✅ |
 | Connect to existing Instant Clusters | ✅ | ❌ | ✅ | ✅ |
 | Create/delete/start/stop Instant Clusters | ❌ | ❌ | ❌ | ✅ |
+| Create/update/delete network volumes | ❌ | ❌ | ✅ | ✅ |
 | View billing information | ❌ | ✅ | ❌ | ✅ |
 | Manage payment methods | ❌ | ✅ | ❌ | ✅ |
 | Invite team members | ❌ | ❌ | ❌ | ✅ |
@@ -94,6 +95,10 @@ The admin role provides complete control over all account features and settings.
 
 Administrators have unrestricted access to manage team members, configure account settings, handle billing, and control all team computing resources. This role should be reserved for team leaders and trusted members who need full account access.
 
+## Account spend limits
+
+By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it.
+
 ## Monitor account activity
 
 Runpod provides comprehensive audit logs to track all actions performed within your account. This feature helps maintain security and accountability across team operations.

hub/public-endpoint-reference.mdx

@@ -1,7 +1,7 @@
 ---
-title: "Public Endpoint model reference"
-sidebarTitle: "Public Endpoint models"
-description: "Explore model-specific parameters for all of Runpod's Public Endpoints."
+title: "Model reference"
+sidebarTitle: "Model reference"
+description: "Explore model-specific parameters for Runpod's Public Endpoints."
 tag: "NEW"
 ---
 
@@ -220,14 +220,10 @@ response = client.chat.completions.create(
     model=model_name,
     messages=messages,
     max_tokens=525,
-    stream_options={"include_usage": True},
     stream=True
 )
 ```
 
-<Tip>
-`stream_options={"include_usage": True}` is required for streaming to work with vLLM Public Endpoints.
-</Tip>
 </Accordion>
 
 <Accordion title="Response format">

hub/public-endpoints.mdx

@@ -1,6 +1,6 @@
 ---
-title: "Public Endpoints"
-sidebarTitle: "Public Endpoints"
+title: "Overview"
+sidebarTitle: "Overview"
 description: "Test and deploy production-ready AI models using Public Endpoints."
 ---
 
@@ -54,7 +54,7 @@ Under **Result**, you can use the dropdown menu to show either a preview of the
 
 After inputting parameters using the playground, you can automatically generate an API request to use in your application.
 
-1. Select the **API** tab in the UI (above the **Input** field).
+1. Click **API Playground** (above the **Prompt** field).
 2. Using the dropdown menu, select the programming language (Python, JavaScript, cURL, etc.) and POST command you want to use (`/run` or `/runsync`).
 3. Click the **Copy** icon to copy the code to your clipboard.
 

pods/manage-pods.mdx

@@ -5,7 +5,7 @@ description: "Create, start, stop, and terminate Pods using the Runpod console o
 
 ## Before you begin
 
-If you want to manage Pods using the Runpod CLI, you'll need to [install Runpod CLI](/runpodctl/install-runpodctl), and set your [API key](/get-started/api-keys) in the configuration.
+If you want to manage Pods using the Runpod CLI, you'll need to [install Runpod CLI](/runpodctl/overview), and set your [API key](/get-started/api-keys) in the configuration.
 
 Run the following command, replacing `RUNPOD_API_KEY` with your API key:
 

pods/pricing.mdx

@@ -152,6 +152,10 @@ Runpod is not designed as a long-term cloud storage system. Storage is provided
 
 When you [stop a Pod](/pods/manage-pods#stop-a-pod), you will no longer be charged for the Pod's hourly GPU cost, but will continue to be charged for the Pod's volume disk at a rate of \$0.20 per GB per month.
 
+## Account spend limits
+
+By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it.
+
 ## Tracking costs and savings plans
 
 You can monitor your active savings plans, including their associated Pods, commitment periods, and expiration dates, by visiting the dedicated [Savings plans](https://www.console.runpod.io/savings-plans) section in your Runpod console. General Pod usage and billing can be tracked through the [Billing section](https://www.console.runpod.io/user/billing).

pods/storage/transfer-files.mdx

@@ -15,16 +15,19 @@ Runpod supports four different file transfer methods, each optimized for specifi
 | **Cloud sync** | Backup, multi-environment sharing | Cloud provider setup | Provider dependent |
 
 ### runpodctl
+
 The simplest option for occasional transfers. Uses secure one-time codes and requires no setup since it's pre-installed on all Pods. Perfect for quick file exchanges.
 
-To install `runpodctl` on your local machine, see the [installation guide](/runpodctl/install-runpodctl).
+To install `runpodctl` on your local machine, see the [installation guide](/runpodctl/overview).
 
 ### SCP
+
 A reliable, standard method that works over SSH. Ideal for users comfortable with command-line tools who need to transfer both individual files and directories.
 
 To configure your Pod for SSH access, see the ([SSH setup guide](/pods/configuration/use-ssh)).
 
 ### rsync
+
 The most powerful option, featuring incremental transfers, compression, and detailed progress reporting. Essential for large datasets, regular synchronization, and preserving file attributes.
 
 To set up `rsync`:
@@ -33,6 +36,7 @@ To set up `rsync`:
 - Ensure your local machine is running a Linux or WSL environment.
 
 ### Cloud sync
+
 Direct synchronization with cloud storage providers like AWS S3, Google Cloud Storage, or Dropbox. Best for creating backups or sharing files across multiple environments.
 
 To learn more, see the [cloud sync configuration guide](/pods/storage/cloud-sync).